Program received signal SIGABRT: Process abort signal

CMAQ
26

@azurebullet,

Thanks for uploading the data for your case. After some testing with @hogrefe.christian we were able to reproduce your error and think that the issue stems from your domain definition.

As @hogrefe.christian noted:

“CCTM can automatically horizontally window gridded files like CGRID or emissions (in your case, EQUATES input files with 299 rows and 459 columns) to a smaller domain (like your subdomain with 125 rows and 125 columns), as long as they share the same projection and the subdomain is fully contained in the larger domain.”

However, there is one additional caveat in the following statement: “the subdomain is fully contained in the larger domain”. This statement assumes that your smaller domain is a least some whole number multiple of the larger domain on all sides.
Figuratively, this is what that means:

image
image1315×746 134 KB

In the domain configuration you provide in your GRIDDESC:

GRID_NAME = ‘2019_08d1’
XORIG = 138000.000
YORIG = -1338000.000

Notice the larger domain grid configuration:
GRID_NAME = ‘12US1’
XORIG = -2556000.0
YORIG = -1728000.

This suggests that the GRID ‘2019_08d1’ is exactly 224.5 grid cells in the X direction and 32.5 in the Y direction, which is not a proper domain definition (off by 0.5*dx) to use if you want to window the EQUATES emissions inputs. Doing so, is causing memory allocation issues and hard to find non-trivial errors in the code.

In this case, you have a couple of options:

  1. Re-run WPS and WRF to re-define your domain to be half a grid cell more or less than what you provide in ‘2019_08d1’. You’ve expressed capability in doing so, so I suggest you pursue this route.

  2. If you are adamant about keeping your domain definition, than you must re-grid all the emissions inputs to match your domain definition. This option is much harder, but certainly can be done.

Please let us know if this fixed your issue, if so we appreciate your help in finding a case where the current implementation of CMAQ doesn’t safely catch this specific invalid setup and leads to hard to find errors. We will work to update our documentation and model code in future releases!

Thanks!

4 Likes