MOM6 regional crashing with layout error

HI all,

I’ve been banging my head against the wall for a couple of days an have convinced myself I’m making a relatively simple error.

I’m attempting to run a custom regional MOM6 configuration, developed using @ashjbarnes tools.

When I run the model on Setonix, I get the following error: At least one pe in pelist is not used by any tile in the mosaic

I’m run the test configuration with 128 cores, and I’ve check that the MOM_LAYOUT matches the requests resources. I’ve regenerated the solo mosaic and quick mosaics (as I’m in the middle of the Pccific ocean, no tiles are masked as there is not enough land).

Does anyone out there have any advice? Thanks all!

1 Like

I haven’t seen that before, but given that it’s happening in the atmosphere initialisation, I wonder if you should include an explicit layout for the null components in your input.nml. Either 0,0 or 10,10, I’m not sure if it can be explicitly empty, or if it should match your processor count:

    layout = 0, 0
    layout = 0,0
1 Like

Thanks @angus-g I gave it a try but, unfortunately, no luck.

I’m wondering if this is either a Setonix thing, or a problem when trying to run the model without a processor land mask?

Can you push your config to GitHub? Would that help for others to assist diagnosing the problem?

Hi Chris,

Just a thought but could it possibly be associated with a MOM6 executable difference? As far as I understand, @ashjbarnes has mom6-regional setup to be using a more recent ocean-only executable? I was hoping to get him to help us compile this on Setonix some time soon.

1 Like

Hi all,

Thanks for the suggestion @john_reilly . This may indeed be an issue. Maybe @angus-g or @ashjbarnes could comment.

The configuration was created using the current version of @ashjbarnes tool (cloned directly from github). I’m not sure what, if any, difference using the ocean only (versus the MOM6-SIS executable) would make.

I’ve been in a workshop all day, but push my config tomorrow to GitHub.

1 Like

Well, with help from @ashjbarnes and @john_reilly we were able to find that the source of the problem was my own incompetence: no mask and moasic files were being produced and included in the INPUT directories, which tripped up the MOM6 at atmospheric initialization.

Potential trap for if you are running a domain in the open ocean with few continents/large islands to be aware of.

1 Like