Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ocean EC(wISC)30to60 performance tests fail #5609

Closed
mark-petersen opened this issue Apr 19, 2023 · 2 comments · Fixed by #5610
Closed

Ocean EC(wISC)30to60 performance tests fail #5609

mark-petersen opened this issue Apr 19, 2023 · 2 comments · Fixed by #5610
Assignees

Comments

@mark-petersen
Copy link
Contributor

In MPAS-Ocean stand-alone testing, the compass tests:

ocean_global_ocean_EC30to60_PHC_performance_test
ocean_global_ocean_ECwISC30to60_PHC_performance_test

fail, or sometimes just hang, when using the gnu optimized compiler on chicoma and chrysalis (and probably others). They pass with gnu debug, intel debug, and intel optimized.

The runs die just before the timestepping begins with the error

$ tail log.ocean.0001.*
----------------------------------------------------------------------
Beginning MPAS-ocean Error Log File for task       1 of     128
    Opened at 2023/04/19 09:15:37
----------------------------------------------------------------------

ERROR: MPAS IO Error: Bad return value from PIO
CRITICAL ERROR: Core init failed for core ocean
Logging complete.  Closing file at 2023/04/19 09:15:37
@xylar
Copy link
Contributor

xylar commented Apr 19, 2023

@mark-petersen, you're seeing this on Chrysalis, too? I hadn't seen that, only on Chicoma and Perlmutter. I ask because Chrysalis is always easier to deal with in terms of queue times so that could be helpful if so.

@mark-petersen
Copy link
Contributor Author

mark-petersen commented Apr 20, 2023

Correct. Master failed on chrysalis as well, and in the same way as chicoma, and #5610 fixes it.

jonbob added a commit that referenced this issue Apr 27, 2023
…#5610)

Remove unused variables in ocean

The variables tidalPotentialZMid and nTidalPotentialConstituents are
defined in the Registry but not used for any computations. This tricks
the gnu compiler in optimized mode, which removes them internally. The
simulation then dies when the i/o references these variables on
initialization.

Fixes #5609
[BFB]
@jonbob jonbob closed this as completed in de075c7 Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants