- Release 1.2.0
- Previous versions of wrf-python promoted the strings used in xarray (e.g.
name, attributes) to Unicode strings. This caused problems when porting
examples for PyNGL to use wrf-python in Python 3.x. All strings are now the
native string for the Python version being used. While this should be
transparent to most users, any users that worked with the xarray name or
attribute values on Python 2.7 may run in to string related errors, so we've
decided to bump the major version number.
Release 1.1.3
Fixed/Enhanced the cloud top temperature diagnostic.
Optical depth was not being calculated correctly when
cloud ice mixing ratio was not available.
Fixed an indexing bug that caused crashes on Windows, but should have been
crashing on all platforms.
Users can now specify if they want cloud free regions to use fill values,
rather than the default behavior of using the surface temperature.
Users can now specify the optical depth required to trigger the cloud
top temperature calculation. However, the default value of 1.0 should be
sufficient for most users.
Added 'th' alias for the theta product.
Fixed a crash issue related to updraft helicity when a dictionary is
used as the input.
Dictionary inputs now work correctly with xy_to_ll and ll_to_xy.
The cape_2d diagnostic can now work with a single column of data, just like
cape_3d.
Fixed indexing bug.
Fixed incorrect computation of optical depth when cloud ice is not available.
Users can use fill values for cloud free areas.
Users can now specify the optical depth threshold that triggers the calculation.
Fixes#45.
Release 1.1.1
- Added script for building on Cheyenne with maxed out Intel settings, which
also required a patch for numpy.distutils.
- Fixed a few unicode characters hiding in a docstring that were causing
problems on Cheyenne, and also building the docs with Sphinx on Python 2.x.
- Fix issue with np.amax not working with xarray on Cheyenne, causing an error
with the mdbz product.
- Fix cape_2d private variable bug when running with multiple CPUs.