You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following test fails because it only writes rpointer files for the components in the short timestep and doesn't write for the components on a longer timestep.
ERS_Ln144.ne30pg3_t232.BLT1850.derecho_intel.allactive-defaultio
There are two problems here:
The test is malformed in that it should select a restart time that is possible for all components, as currently formed it writes a restart at 2days 12.5 hours (02-45000) which is not a time that all of the components can restart.
Even if it were to specify a time that works for all components, the restart alarm for each component is triggered based on the number of steps for that component and not that of the shortest timestep component as it should be. CESM version you are using: cesm3.0-beta02
Machine you are using: derecho
Have you modified the code? (If so, please point us to you changes.): No
Details of bug
See description above
Steps to reproduce the problem. Include externals description file(s) and link to public repository
run the test indicated
Screen output or log file showing the error message and context
The text was updated successfully, but these errors were encountered:
Brief summary of bug
Test fails due to incorrect restart alarms
General bug information
The following test fails because it only writes rpointer files for the components in the short timestep and doesn't write for the components on a longer timestep.
ERS_Ln144.ne30pg3_t232.BLT1850.derecho_intel.allactive-defaultio
There are two problems here:
The test is malformed in that it should select a restart time that is possible for all components, as currently formed it writes a restart at 2days 12.5 hours (02-45000) which is not a time that all of the components can restart.
Even if it were to specify a time that works for all components, the restart alarm for each component is triggered based on the number of steps for that component and not that of the shortest timestep component as it should be.
CESM version you are using: cesm3.0-beta02
Machine you are using: derecho
Have you modified the code? (If so, please point us to you changes.): No
Details of bug
See description above
Steps to reproduce the problem. Include externals description file(s) and link to public repository
run the test indicated
Screen output or log file showing the error message and context
The text was updated successfully, but these errors were encountered: