360 day calendar in WBM #16
-
|
I am trying to run WBM with some climate drivers that employ a Is there another setting I should be changing? Currently some other inputs (e.g. crop and soil data) are still set to 365 bands, could this be the issue? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
The calendar keyword in the init file is case sensitive, and the statement "calendar => 360" in the "MT_Code_Name => {}" block will not work. It must be "Calendar => 360". Please, use a reference init file spreadsheet "WBM_Usage_and_Input_Reference.xlsx" for correct key words. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick response, Alex. I am using the correct case now but I see the following error |
Beta Was this translation helpful? Give feedback.
-
|
Which climate inputs have this issue? How many? Is it a particular ensemble? |
Beta Was this translation helpful? Give feedback.
-
|
The issues are with the KACE-1-0-G, UKESM1-0-LL, and HadGEM3-GC31-MM/LL models in the NEX-GDDP ensemble. So 4/35 models. Overall not a huge problem and I think pre-processing would be the simpler solution(?) |
Beta Was this translation helpful? Give feedback.
-
|
Meanwhile:
|
Beta Was this translation helpful? Give feedback.
-
|
example of how to deal with the input data: https://loca.ucsd.edu/loca-calendar/ |
Beta Was this translation helpful? Give feedback.
-
|
This is useful! Since we are almost always aggregating over time horizons longer than a day I don't think we need to worry about making false comparisons. But having fewer days over the growing season (for example) could make a difference in the statistics, though I'm not sure how important that would be vs. differences in models and interannual variability. Xarray has some functionality to convert calendars and insert NaNs to the new dates (https://docs.xarray.dev/en/stable/generated/xarray.Dataset.convert_calendar.html) so maybe this could be the starting point. |
Beta Was this translation helpful? Give feedback.
- 7511
The calendar keyword in the init file is case sensitive, and the statement "calendar => 360" in the "MT_Code_Name => {}" block will not work. It must be "Calendar => 360". Please, use a reference init file spreadsheet "WBM_Usage_and_Input_Reference.xlsx" for correct key words. Thanks.