[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[python #SJG-520459]: WRF-Python issue

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [python #SJG-520459]: WRF-Python issue
  • Date: Wed, 28 Aug 2024 11:18:45 -0600
Greetings!

Unfortunately, we don't maintain the WRF-Python package and don't have any 
experience working with it. WRF-Python is developed and maintained by our 
colleagues over in NCAR's Computer and Information Systems Lab.

I would suggest opening an issue over on the issue tracker for WRF-Python and 
see if someone is able to help you there:

    https://github.com/NCAR/wrf-python/issues

Cheers,

Ryan

> Hello everyone,
> For a while I have been using successfully wrf-python version 1.3.2.6, but
> recently a colleague of mine tried extracting cape_2d with wrf-python and
> found strange patterns in the map, the same happened with slp variable
> (attached cape_wrong.jpeg and slp_wrong.jpeg files).
> 
> However terrain variable (also extracted with wrf-python) seems fine
> (attached ter_right.jpeg)
> 
> I have tried using his code to reproduce the results... but I couldn't! I
> got correct values for CAPE and SLP.
> The only difference is the environment. I used a linux machine in the cloud
> and my colleague used a local linux VM. We discarded it was a wrf-python
> version, but maybe there is something else different in the environment
> (other python dependencies for example).
> 
> In the following post they comment something similar:
> https://groups.google.com/a/ucar.edu/g/wrfpython-talk/c/CM0WnzByTwY


Ticket Details
===================
Ticket ID: SJG-520459
Department: Support Python
Priority: Low
Status: Closed
===================
NOTE: All email exchanges with NSF Unidata User Support are recorded in the 
Unidata inquiry tracking system and then made publicly available through the 
web.  If you do not want to have your interactions made available in this way, 
you must let us know in each email you send to us.