-
Notifications
You must be signed in to change notification settings - Fork 7
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
pio configuration checks #158
Comments
For sequential runs, the above formula will break using the following setup, since the formula
|
Yes -it should be It looks like there is some logic which just changes these values if they are wrong:
I guess we could add
Or throw an error if the condition fails. Shall we do this in the CESM share, or payu, or both ? |
I think there is a bug here. See this payu-org/payu#496 (comment) |
Closed through payu-org/payu#496 |
We should add checks to the pio initialisation modules to confirm that these options are valid for each model component and the mediator:
I think the checks would go here:
https://github.com/ESCOMP/CMEPS/blob/ffb573791c7670ada8660dbac96c6c84886f62d3/cesm/nuopc_cap_share/driver_pio_mod.F90#L366
But it may be they fit at a higher level within the CMEPS code.
The most likely error we would make it to request io from a PE which doesn't exist. i.e. we need to check
This would avoid isses like #156
Another error to check is if pio_typename is compatible with the pio version built.
The text was updated successfully, but these errors were encountered: