Closed freecodegaku closed 1 year ago
Hi @freecodegaku thanks for reporting this; it's interesting! We will look into this as soon as we can.
Just noting that I was able to replicate this issue.
I can try to look into this some this week, but we should probably pin to Python <3.11 for the time being.
I run the example script in the reference guide (https://wrf-python.readthedocs.io/en/latest/plot.html) using the same netcdf file used there. I got this unphysical result:
I used: python 3.10.9 netcdf4 1.6.3 matplotlib 3.7.1 cartopy 0.21.1
I tried both on windows 10 and linux, obtaining the same result.
Probably it's something related to the bug observed by @freecodegaku, even if I got this with a version of python<3.11.
I run the example script in the reference guide (https://wrf-python.readthedocs.io/en/latest/plot.html) using the same netcdf file used there. I got this unphysical result:
I used: python 3.10.9 netcdf4 1.6.3 matplotlib 3.7.1 cartopy 0.21.1
I tried both on windows 10 and linux, obtaining the same result.
Probably it's something related to the bug observed by @freecodegaku, even if I got this with a version of python<3.11.
Had the same issue, Installed python3.9 and for now everything seems fine
I run the example script in the reference guide (https://wrf-python.readthedocs.io/en/latest/plot.html) using the same netcdf file used there. I got this unphysical result:
I used: python 3.10.9 netcdf4 1.6.3 matplotlib 3.7.1 cartopy 0.21.1
I tried both on windows 10 and linux, obtaining the same result.
Probably it's something related to the bug observed by @freecodegaku, even if I got this with a version of python<3.11.
I also met this problem with python3.9, wrf-python1.4.1, netcdf1.6.2, and I guess the main reason is the "slp" in getvar function. Then I create a environment with python3.7, the problem solved.
the reason looks like to be numpy/numpy#23651 is your numpy version 1.24.3?
Thanks for pointing that out.
I haven't time to dig into this much, but that aligns with my current suspicions as well.
the reason looks like to be numpy/numpy#23651 is your numpy version 1.24.3?
Looks like that's the case. Pinning numpy fixes this issue and the additional/related test failures I see. Numpy just released 1.24.3 less than two months ago and dropped support for Python 3.7 so older environments and Python versions likely wouldn't be impacted.
I'll throw in a PR to pin numpy.
@freecodegaku, @Cat7102, @sinan0310 if you're still having issues with a numpy version other than 1.24.3, please let us know. Thanks for the bug report!
Running wrf-python with python=>3.11 produces different results to those from ncl e.g for example when using Python 3.11.3 on [https://www.dropbox.com/s/szxm475isnlnufh/wrfout_d01_1989-04-28_01?dl=0](https://www.dropbox.com/s/szxm475isnlnufh/wrfout_d01_1989-04-28_01?dl=0](https://www.dropbox.com/s/szxm475isnlnufh/wrfout_d01_1989-04-28_01?dl=0](https://www.dropbox.com/s/szxm475isnlnufh/wrfout_d01_1989-04-28_01?dl=0)
gives a min of 121.18885 and max of 495.5703. While using ncl
produces a min of 185.3759 and max 316.4777.
Running the python code with python version <=3.10.10 produces the same results as ncl i.e. 185.3759 and max 316.4777.