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

Ensures MPAS AM write/compute startup steps are performed #1191

Conversation

pwolfram
Copy link
Contributor

This merge fixes a bug in the ACME for MPAS-O analysis members (AMs)
where startup computation and writing did not work for AMs because a call to ocn_analysis_compute_startup was previously missing.

Dycore results should be BFB. However, AM results may not necessarily
be BFB.

Addresses #1185. Assumes MPAS-O PR MPAS-Dev/MPAS#1179 has been fulfilled.

cc @jonbob

Copy link
Contributor

@jonbob jonbob left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pwolfram - we're going to include this PR in the upcoming MPAS push and I wanted to see if you'd like to add a comment line to this before I bring it in. No big deal...

@pwolfram
Copy link
Contributor Author

pwolfram commented Feb 1, 2017 via email

@jonbob
Copy link
Contributor

jonbob commented Feb 1, 2017

Oh, I just meant a comment in the Fortran code

This is to fix a bug in the ACME where startup computation and writing
did not work for AMs.  A call to `ocn_analysis_compute_startup` was
previously missing
@pwolfram pwolfram force-pushed the pwolfram/ocn/fix_AM_write_on_startup branch from c34ec71 to c00cde8 Compare February 1, 2017 22:37
@pwolfram
Copy link
Contributor Author

pwolfram commented Feb 1, 2017

@jonbob, thanks for catching that-- it is much better with a comment!

@jonbob
Copy link
Contributor

jonbob commented Feb 1, 2017

@pwolfram -- certainly not important, but maybe more clear. Thanks!

@jonbob
Copy link
Contributor

jonbob commented Feb 8, 2017

@pwolfram -- one more quick question. I've been testing an implementation of this in mpas-seaice, but in that case, the call to cice_analysis_compute_startup is done at the end of the init_mct routine instead of in the run_mct routine. It will only get called once that way, while in the ocn it will be called every timestep. Do you think it's necessary to call it for every step? In the standalone ocn driver, it only gets called once....

@jonbob
Copy link
Contributor

jonbob commented Feb 13, 2017

This issue was closed by #1257

@jonbob jonbob closed this Feb 13, 2017
@jonbob jonbob deleted the pwolfram/ocn/fix_AM_write_on_startup branch February 13, 2017 22:18
agsalin pushed a commit that referenced this pull request Apr 13, 2017
fix issue with compset not printing to timing file

Get_timing was using the old CCSM_COMPSET name instead of just COMPSET

Test suite: scripts_regression_tests.py
Test baseline:
Test namelist changes:
Test status: bit for bit

Fixes #1191

User interface changes?:

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

Successfully merging this pull request may close these issues.

2 participants