Closed aidanheerdegen closed 1 month ago
Note that this doesn't stop payu
running, but it is confusing for users if payu
reports an error that should be ignored.
I think it's being checked in the general payu model driver during setup where it creates the restart manifest and sets up symlinks to the work directory:
Should the error print statement not run for just the yatm
model? It looks like the yatm
model creates an empty directory during the archive step.
It looks like the
yatm
model creates an empty directory during the archive step.
You're right
https://github.com/payu-org/payu/blame/master/payu/models/yatm.py#L41
I can only assume that is because get_prior_restart_files
expected there to be one.
I think this solution is to remove that from the yatm
driver and add a no-op get_prior_restart_files
method to the yatm driver class that just returns an empty array.
Yeah I think that'll work :)
Do you know if the yatm
model never uses prior restart files? Just double checking whether it is safe to over-ride the method and return []
, or to have mostly the same method apart from the error log message?
yam
reads from data files, so should never require prior restarts. So fine to assume so. In some ways overriding is better because it is explicit that there are no restarts.
When trying to use some older restarts from a COSIMA model (
/g/data/ik11/outputs/access-om2-025/025deg_jra55_ryf9091_gadi/restart250
)payu
threw an error complaining about the absence of anatmosphere
subdirectory in the restart directory.It seems ACCESS-OM2 is now producing an empty
atmosphere
restart directory and then insisting on that existing in older restart directories.payu version info:
I used this released 0.25 configuration
https://github.com/ACCESS-NRI/access-om2-configs/tree/release-025deg_jra55_ryf-2.0