-
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]: Failure to generate global time series plot if not starting from year 1 #546
Comments
No, that works. The cfg I use for testing starts at 1850 (https://github.com/E3SM-Project/zppy/blob/main/tests/integration/generated/test_complete_run_chrysalis.cfg). But I wasn't sure if that was the simulation start date. So, I ran a cfg starting at 1860 instead and it generated plots ok: https://web.lcrc.anl.gov/public/e3sm/diagnostic_output/ac.forsyth2/zppy_test_debug_www/546-change-start-yr/v2.LR.historical_0201/global_time_series/global_time_series_1860-1870_results/v2_historical_0201_glb.pdf cfg:
|
So something is happening in this block, specifically at zppy/zppy/templates/coupled_global.py Lines 585 to 590 in 4db3e24
But I'm not sure why that's failing.
It does look like only the There are two types of errors:
Corresponds to zppy/zppy/templates/global_time_series.bash Lines 88 to 95 in 4db3e24
Corresponds to zppy/zppy/templates/global_time_series.bash Lines 67 to 75 in 4db3e24
|
What happened?
The following error occur when trying to generate global time series plot that does not start from year 1 of a simulation (v3.LR.piControl-spinup). This happens after e3sm_diags and mpas-analysis for the covered period have been completed properly. Same errors also occur for other subperiods, such as global_time_series_0901-1100, global_time_series_1001-1400, regardless of the length of the time series. Does it mean the plotting codes are currently intended only for time series from the beginning of a simulation? Is it easy to make it work for any selected sub-period?
Examples can be found under /lcrc/group/e3sm2/ac.wlin/E3SMv3/20231209.v3.LR.piControl-spinup.chrysalis/post/scripts
What machine were you running on?
chrysalis
Environment
v2.3.1rc1
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: