Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

Interesting Error Running 1 km Regional Mesh

MattW

Member
Hi MPAS folks,

I managed to make a 1 km regional mesh by first using MPAS-BR/grids/utilities/jigsaw/spherical_grid.py at master · pedrospeixoto/MPAS-BR to create a 150 km global mesh with a 1 km regional refinement, and then cutting out the 1 km refinement as a regional mesh using MPAS-Limited-Area. I was able to generate a static file, an init file, and lbc files using this mesh and HRRR data. However, when I tried running atmosphere using the resulting init and lbc files, I encountered an error I hadn't seen before, and that I haven't seen mentioned on the MPAS forum yet:

----------------------------------------------------------------------
Beginning MPAS-atmosphere Error Log File for task 336 of 512
Opened at 2025/07/16 09:08:03
----------------------------------------------------------------------

ERROR: MaxEdges2 < nOuterRow in CellsOnCellsOnCell
ERROR: MaxEdges2 = 16
ERROR: nOuterRow = 17
CRITICAL ERROR: Critical Error
Logging complete. Closing file at 2025/07/16 09:08:03

Is this due to the 1 km mesh being configured incorrectly? I was wondering if the 150 to 1 km refinement was too extreme--I'm trying a 60 to 1 km one to see if it fixes the issue. Could it also be a product of the limited area mesh generation? I'm running this experiment on Derecho at /glade/derecho/scratch/mawilson/mpas_tests/TX_floods if taking a look there would be helpful.

Thanks!

Matt Wilson
 
Using your ICs and LBCs, the standard MPAS-A v8.3.1 release seems to be running without issue. Are you using something like the ufs-community fork of MPAS-Model? If so, perhaps the issue is specific to that code.
 
I tried using an older version of the GSL MPAS code and it ran successfully, so it sounds like the issue is specific to the current version.
 
Also let me know if you've got any idea what might be causing the error with the latest GSL MPAS version, since we want to update to that one at some point. I'll also reach out to the GSL folks to see if they've run into this before.
 
Top