-
Notifications
You must be signed in to change notification settings - Fork 104
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
Mismatch between datetime objects #730
Comments
@nishsilva thank you for opening this issue! I will update you on what I find. |
Hey @nishsilva, there were a few issues found. They have been fixed in the latest PR #732. If you could try this out, let me know if this solves what you are seeing! |
Thank you for the fix @jtmims the datetime issue has been resolved. However, I am encountering another error when I set preprocessing to true. Let me know if I need to open this as a new issue. Below is the error message I am receiving.
|
@nishsilva thanks for sending in these issues! I was able to get the preprocessor to work on this data and launch your POD using PR #733. Let me know if this works for you too! |
@jtmims preprocessor is now working fine at my end too. Thank you so much for your support! I am closing the issue. |
Bug Severity
Describe the bug
I am trying to read in a model data set from ECMWF-LR output in the MDTF. For this I use a data catalog. When I run the MDTF I get an error (attached) saying that there is a mismatch between the cftime datetime objects in the dataset because one using the Gregorian calendar and the other using the noleap calendar.
Steps To Reproduce
Created a data catalog for a HighResMIP Model data files (variable zos) - CMIP6.HighResMIP.ECMWF.ECMWF-IFS-HR.hist-1950.r1i1p1f1.Omon.zos.gn
Created a trial POD names sl_reginoal https://github.com/nishsilva/MDTF-diagnostics/tree/nish-pod/diagnostics/sl_regional
The runtime configuration file is https://github.com/nishsilva/MDTF-diagnostics/blob/nish-pod/diagnostics/sl_regional/runtime_config_NE_ECMWF_HR.yml
Environment
Describe the system environment:
Log information and/or terminal output
The text was updated successfully, but these errors were encountered: