Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

ndown fails due to time step not on the hour

mullenkamp

New member
Hi,

I'm trying to run ndown to run a model down to 1km. The source data is from a nested model run that goes down to 3km. Both namelist.input files are attached with the rsl.error.0000 file from ndown.
ndown fails due to "Found 2020-09-28_01:00:02 before I found 2020-09-28_01:00:00"; which means that the source 3km output file does not have a time step on the hour.
I am using adaptive time stepping, but I'm also using step_to_output_time = .true.

Is there anything else I can do to force the time steps to the hour or have ndown ignore the seconds offset?

Thanks
 

Attachments

  • namelist_3km.input
    2.7 KB · Views: 0
  • namelist_ndown.input
    2.5 KB · Views: 0
  • rsl.error.0000
    8.6 KB · Views: 0
I found one solution.

Set this parameter in time_control:
adjust_output_times = .true.

It forces all time stamps to be rounded to the nearest hour.

This should also be set in domains to ensure that the model output is already close to the hour:
step_to_output_time = .true.

Hopefully I don't need any sub-hourly results ;) .
 
Top