POD discussion: Surface Temperature Extremes diagnostic #120
Replies: 8 comments
-
@acatalano16 : I wanted to update you on some issues running the POD on CMIP6 data (so beyond your sample data; some of the errors may be due to framework code). I've added some debugging comments but haven't gotten very far yet -- if you have any insight please let me know.
temp_extremes_distshape.log
|
Beta Was this translation helpful? Give feedback.
-
@tsjackson-noaa On the first issue, I did get some empty slice warnings but the code ran smoothly despite these warnings so I didn't consider it an error. I believe they are related to the masking, so taking even a "nanmean" or "nanpercentile" across some masked latitudes of NaNs will result in that warning. On the second issue, I have never received that error and am thus unsure of the cause. If you try looking at the max/min of the exceedances array maybe that will be illuminating? Perhaps it's turning into all NaNs upstream or is outside the threshold range, though I can't imagine why from the code. On the third issue, I had considered 4D data in crafting the code and have a commented line somewhere. Is the 4D data already sliced to 500hPa and just has a "1" in the last dimension? |
Beta Was this translation helpful? Give feedback.
-
Thanks @acatalano16. Would you be able to also pass along the versions of the Python packages you used to develop the POD, specifically NumPy? |
Beta Was this translation helpful? Give feedback.
-
@jkrasting @tsjackson-noaa Upon further inspection, I was receiving that same error (I've been using the _MDTF_base environment), but because it popped up in the log before that section of code ran and it didn't affect the output html, I must have missed it. I apologize. It seems to be similar to the first "error" in that it is related to the NaN slices from masking the globe, and it doesn't stop the code (it's related to numpy as John figured out: Unidata/netcdf4-python#766). I think the easiest fix for the first two points raised is to suppress the warning messages, but it's not a command I'm used to using and was unable to apply successfully last year when I first tried. If that's not a route you want to take, I can also try bypassing numpy slices by including a few "if" lines at these problematic functions? |
Beta Was this translation helpful? Give feedback.
-
Progress update: Link to development branch and POD commit history. These links will stop working when the branch is deleted after integration work is finished. Links to files below will remain valid. Current bugs/errors:
Remaining necessary tasks:
|
Beta Was this translation helpful? Give feedback.
-
Referencing #40 as it relevant to this issue. |
Beta Was this translation helpful? Give feedback.
-
The branch containing existing development work on this POD has been renamed from pod/temp_extremes_distshape to feature/add_temp_extremes_distshape, as part of the reorganization proposed in issue #106. |
Beta Was this translation helpful? Give feedback.
-
Update: Sticking point encountered previously was that the POD uses |
Beta Was this translation helpful? Give feedback.
-
Thread for progress in adding the Surface Temperature Extremes Distributions POD by Arielle Catalano, Paul Loikith and J. David Neelin.
Beta Was this translation helpful? Give feedback.
All reactions