-
Notifications
You must be signed in to change notification settings - Fork 180
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
gdasstage_ic and gdasfcst_seg0 disagree on staged filenames for ocean restarts #2865
Comments
Will work on this, thanks for reporting @jswhit ! |
Alrighty, so the
...but later on it gets set to the cycle that's running because the experiment is cold-starting, which means IAU is off and the model start date would not be 3hrs earlier:
That happens in Based on the above, either:
Pretty sure option 2 is what is needed. Thoughts? |
I believe 2 was how things worked before |
FWIW, this fixes my particular case (cold start for atmosphere, warm starts for ocean/ice)
|
Good to know, thanks @jswhit ! Didn't get a chance to look deep into this yesterday, will aim to today. |
@jswhit I see now that the staging needed adjusting. When I tested it it worked but I see now that you had symlinks from the I just ran the |
- Create specific variables for atmos, ice, mediator, ocean, and wave cycle dates and update scripts/staging yamls to use them. - Also resolve issue with incorrect IC filenames caused by not turning IAU off for cold-start. Refs NOAA-EMC#2865 Refs NOAA-EMC#2890
sorry for the late reply @KateFriedman-NOAA. When I copy your parm/stage directory, the staging job seems to run fine but I'm getting this error in gdasfcst_seg0.log. I think it's probably unrelated to this issue, but I don't seem to have a sorc/upp.fd/parm/gfs directory (which parm/post/gfs is symlinked to).
|
@jswhit There was an update to the system related to UPP and its parm txt files so you'll either want to make a fresh clone or do a submodule update command (and then link script) in your clone to remedy the issue. |
Okay, got the submodules updated correctly. Now I get this error
in gdasfcst_seg0 (see /scratch2/BMC/gsienkf/whitaker/GWTESTS/COMROOT/C96coupled3dvar_test/logs/2021032400) The file that was staged is |
@jswhit Ok so I traced the real issue back to the IAU not being turned off for the first half cycle so 3hrs is taken from the filename when it shouldn't. The PR I have open adds
Then rerun the staging and fcst jobs again. Let me know how it goes. |
that fixed it - thanks @KateFriedman-NOAA |
however, the first gdasocnanalprep step fails to find |
A similar problem with the snow analysis (gdassnowanl), |
@jswhit In both instances, 3hrs (half the assimilation window) is being taken off of the date in those filenames when it shouldn't. I looked at the latest logs for those two jobs and don't see |
@KateFriedman-NOAA |
- Move DOIAU="NO" to config.stage_ic - Add similar condition check to forecast_predet.sh Refs NOAA-EMC#2865
Fixes issue with incorrectly setting model_start time for initial condition filenames when cold starting. Refs NOAA-EMC#2865 Refs NOAA-EMC#2890
What is wrong?
for a coupled 3dVar cycling experiment with cold starts for 2021032400
gdasstage_ic
stages oceans restarts with m_prefix = 20210323.180000, butgdasfcst_seg0
then looks for restarts with m_prefix = 20210324.0000. Here's the error fromgdasfcst_sego
:and the relevant output from
gdasstage_ic
:What should have happened?
gdasstage_ic stages ocean restarts with the same filenames expected by gdasfcst_seg0 for cold starts.
What machines are impacted?
Hera
Steps to reproduce
run a cycled 3DVar coupled atm/ocean experiment. I ran
from /scratch2/BMC/gsienkf/whitaker/global-workflow-jswhit, with the patch from issue #2864 applied so that
gdasstage_ic
does not fail.Additional information
N/A
Do you have a proposed solution?
no
The text was updated successfully, but these errors were encountered: