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

Crash with 'FATAL from PE 0: MOM_obsolete_params' #77

Closed
zhaobin74 opened this issue Aug 14, 2024 · 2 comments · Fixed by #79
Closed

Crash with 'FATAL from PE 0: MOM_obsolete_params' #77

zhaobin74 opened this issue Aug 14, 2024 · 2 comments · Fixed by #79

Comments

@zhaobin74
Copy link
Contributor

zhaobin74 commented Aug 14, 2024

Coupled run with MOM6 at 1440x1080 resolution crashed in MOM6 initializer:

WARNING from PE     0: MOM_obsolete_params: ETA_TOLERANCE_AUX is an obsolete run-time flag.


WARNING from PE     0: MOM_obsolete_params: ETA_TOLERANCE_AUX is an obsolete run-time flag.


WARNING from PE     0: MOM_file_parser : DEFAULT_2018_ANSWERS over-ridden.  Line: 'DEFAULT_2018_ANSWERS = False' in file MOM_override.


WARNING from PE     0: MOM_file_parser : DEFAULT_2018_ANSWERS over-ridden.  Line: 'DEFAULT_2018_ANSWERS = False' in file MOM_override.


FATAL from PE     0: MOM_obsolete_params: DEFAULT_2018_ANSWERS is an obsolete run-time flag, and should not be used. Instead use DEFAULT_ANSWER_DATE.


FATAL from PE     0: MOM_obsolete_params: DEFAULT_2018_ANSWERS is an obsolete run-time flag, and should not be used. Instead use DEFAULT_ANSWER_DATE.

--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on

DEFAULT_2018_ANSWERS is not being accepted, but present in both MOM_input and MOM_override.
It should be commented out or removed from both config files.

GEOS version: 11.6.0

@mathomp4
Copy link
Member

@zhaobin74 Can you look at #78. I just sort of went in and removed any line like that.

NOTE: #79 is aimed to GEOSgcm v12, so you'll want to try #78 which is for GEOSgcm v11

@sanAkel
Copy link
Collaborator

sanAkel commented Aug 16, 2024

@mathomp4, @zhaobin74 the fix is simple! Just set a date for DEFAULT_ANSWER_DATE. See this example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants