-
Notifications
You must be signed in to change notification settings - Fork 15
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
[Bug]: ilamb unable to submit due to dependency check failure attributable to inconsistent resolving of ts_num_years #599
Comments
Thanks @wlin7. This points to a larger problem of running any task on a time period consisting of many time periods for its dependent task. In https://github.com/E3SM-Project/zppy/blob/main/zppy/ilamb.py:
Similarly in https://github.com/E3SM-Project/zppy/blob/main/zppy/e3sm_diags.py:
We'd probably need to replace each block of that type with a for-loop of dependency addition incrementing the start_yr and end_year by ts_num_years each time. |
@wlin7 Did setting |
Resolved by #603 |
What happened?
On running ilamb for v3.LR.historical_0101, with the following ilamb section in the cfg file
zppy would prompt
ts
files forland_monthly
was set to be every 5 years, which were generated properly.ts_num_years = 5
was set accordingly for the ilamb section. The dependency is expected to be on every 5 years from 1985 to 2014. But the above apparently is checking on1985-2014-0005
, in which the number of years0005
does not match the length fromstart year (1985)
toend year (2014).
What machine were you running on?
chrysalis
Environment
zppy in e3sm_unified_1.10
What command did you run?
Copy your cfg file
What jobs are failing?
What stack trace are you encountering?
The text was updated successfully, but these errors were encountered: