What version of the code are you using?
CESM 2.2.0
Have you made any changes to files in the source tree?
Some changes in nudging module
Describe every step you took leading up to the problem:
I am trying to run a hybrid case.
First I run the startup case, which it is December 2023 for daily runs and the outputs contain 3 hourly data.
Once the run is completed, I prepare a hybrid case for January 2024 where during the setting a I copy the initial (atmosphere) and restart (all other components) data in the /glade/derecho/scratch/$LOGNAME/viirs_2024/run/.
All this files have the ending format like:
*yyyy-mm-dd-00000.nc
The run is not completed and in the cess.log file the error shoe is this:
ERROR: GETFIL: FAILED to get viirs_2023.cam.i.20240101-00000.nc
Describe your problem or question:
How can I make that the model instead of looking for viirs_2023.cam.i.20240101-00000.nc look for viirs_2023.cam.i.2024-01-01-00000.nc
CESM 2.2.0
Have you made any changes to files in the source tree?
Some changes in nudging module
Describe every step you took leading up to the problem:
I am trying to run a hybrid case.
First I run the startup case, which it is December 2023 for daily runs and the outputs contain 3 hourly data.
Once the run is completed, I prepare a hybrid case for January 2024 where during the setting a I copy the initial (atmosphere) and restart (all other components) data in the /glade/derecho/scratch/$LOGNAME/viirs_2024/run/.
All this files have the ending format like:
*yyyy-mm-dd-00000.nc
The run is not completed and in the cess.log file the error shoe is this:
ERROR: GETFIL: FAILED to get viirs_2023.cam.i.20240101-00000.nc
Describe your problem or question:
How can I make that the model instead of looking for viirs_2023.cam.i.20240101-00000.nc look for viirs_2023.cam.i.2024-01-01-00000.nc