-
Notifications
You must be signed in to change notification settings - Fork 6
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
Issues related to stop_option = nsteps in nuopc.runconfig #157
Comments
Thanks minghang for the explanation :) That behaviour seems correct? We could add a note to the wiki We can do 1-timestep in 1-deg configs because the ocean timestep ( As you said, in 0.25 degree, the smallest stop_n that gives a whole number of |
For the existing 025 deg config,
I dont follow.. the smallest |
Are you suggesting that since the ocn_cpl_dt is 3600, achieving a whole number with 12 nsteps (12*3600/1350) would indicate correctness? We might be discussing different things here. From wiki, it suggests that |
Good catch @minghangli-uni. So it looks like we are wrong about the Note I did write a caveat in the wiki 😉:
|
@ezhilsabareesh8, I presume you didn't try to run either of these PRs with |
@dougiesquire , I just tried running the IAF config for 5 steps with
|
@ezhilsabareesh8 Can you please post the directory for this iaf run? |
It does look like the cpl_dt are important for setting at least the mediator timestep: Its suprising it just work without it! |
It's in my home directory, let me copy it to a different location. I am just running the MOM6-CICE6 IAF configuration with the nuopc settings mentioned above. |
@anton-seaice, this is what I wrote about this in the wiki, but clearly deeper investigation is needed:
|
Hi @ezhilsabareesh8, it appeears that you haven't modified CLOCK_attributes::
atm_cpl_dt = 99999 #not used
calendar = GREGORIAN
end_restart = .false.
glc_avg_period = yearly
glc_cpl_dt = 86400
history_ymd = -999
ice_cpl_dt = 99999 #not used
... Hence the updated total runlength was calculated as 86400*5/1350=320, resulting in a whole number and allowing the run to proceed without any issues.
Despite the total runlength updating, the timestep for each component remains unchanged at 1350s. Hence, you can determine your |
When I set
|
I did the same run but didn't meet the error you described. However, the error message I received was similar to what I initially reported.
Have you previously reported this issue elsewhere? |
The only caveat is when using case (optNSteps,trim(optNSteps)//'s')
call ESMF_ClockGet(clock, TimeStep=AlarmInterval, rc=rc)
if (ChkErr(rc,__LINE__,u_FILE_u)) return
AlarmInterval = AlarmInterval * opt_n For the other options, such as case (optNMinutes,trim(optNMinutes)//'s')
call ESMF_TimeIntervalSet(AlarmInterval, s=60, rc=rc)
AlarmInterval = AlarmInterval * opt_n The |
Thanks @minghangli-uni. So I think the safest/clearest way forward is to set (at least) |
This issue has been mentioned on ACCESS Hive Community Forum. There might be relevant details there: https://forum.access-hive.org.au/t/cosima-twg-meeting-minutes-2024/1734/11 |
To avoid confusion I think we should add a comment to
|
Thanks @aekiss. We can use the automatic |
* Add comments after ocn_cpl_dt in nuopc.runconfig - COSIMA/access-om3#157 (#95) * Update nuopc.runconfig Co-authored-by: Andrew Kiss <31054815+aekiss@users.noreply.github.com> --------- Co-authored-by: Andrew Kiss <31054815+aekiss@users.noreply.github.com>
* Add comments after ocn_cpl_dt in nuopc.runconfig - COSIMA/access-om3#157 (#95) * Update nuopc.runconfig Co-authored-by: Andrew Kiss <31054815+aekiss@users.noreply.github.com> Fix bug in nuopc.runconfig by removing the equal sign ('=') from comments (after '#') (#98) (#99)
* Add comments after ocn_cpl_dt in nuopc.runconfig - COSIMA/access-om3#157 (#95) * Update nuopc.runconfig Co-authored-by: Andrew Kiss <31054815+aekiss@users.noreply.github.com> Fix bug in nuopc.runconfig by removing the equal sign ('=') from comments (after '#') (#98) (#99)
* Add comments after ocn_cpl_dt in nuopc.runconfig - COSIMA/access-om3#157 (#95) * Update nuopc.runconfig Co-authored-by: Andrew Kiss <31054815+aekiss@users.noreply.github.com> ---------
* Add comments after ocn_cpl_dt in nuopc.runconfig - COSIMA/access-om3#157 (#95) * Update nuopc.runconfig Co-authored-by: Andrew Kiss <31054815+aekiss@users.noreply.github.com> Fix bug in nuopc.runconfig by removing the equal sign ('=') from comments (after '#') (#98) (#99) Co-authored-by: minghang.li <minghangl1101@gmail.com>
* Add comments after ocn_cpl_dt in nuopc.runconfig - COSIMA/access-om3#157 (#95) * Update nuopc.runconfig Co-authored-by: Andrew Kiss <31054815+aekiss@users.noreply.github.com> Fix bug in nuopc.runconfig by removing the equal sign ('=') from comments (after '#') (#98) (#99) Co-authored-by: minghang.li <minghangl1101@gmail.com>
* Add comments after ocn_cpl_dt in nuopc.runconfig - COSIMA/access-om3#157 (#95) * Update nuopc.runconfig Co-authored-by: Andrew Kiss <31054815+aekiss@users.noreply.github.com> ---------
It appears that there are issues related to
stop_option = nsteps
, contrary to what was proposed in the wiki.The default
CLOCK
setup innuopc.runconfig
for the current 0.25deg configuration is listed as follows, but changingrestart_n=10
,stop_n=10
andrestart_option = nsteps
:An error occurs with the above setup:
ERROR PET239 src/addon/NUOPC/src/NUOPC_Base.F90:956 Invalid argument - setClock timeStep=1350s is not a divisor of runDuration=36000s
This error suggests that these timesteps are still in use (i.e.,
3600*10/1350
). A more consolidated evidence can be found by checking the ESMF profiling results. When changingstop_n
to 12, the code can be run successfully. This is because 3600*12 can divide 1350 and equals 32, as evidenced by the count for[OCN] RunPhase1
, which is 32 instead of 12.NB:
days
andyears
are functioning properly, so this issue should not impact production runs. However, it's worth noting for anyone interested in conducting short tests.The text was updated successfully, but these errors were encountered: