unyt 2.1.0

Code of Conduct

The unyt package is part of The yt Project. Participating in unyt development therefore happens under the auspices of the yt community code of conduct. If for any reason you feel that the code of conduct has been violated, please send an e-mail to confidential@yt-project.org with details describing the incident. All emails sent to this address will be treated with the strictest confidence by an individual who does not normally participate in yt development.

License

The unyt package is licensed under the BSD 3-clause license.

Citation

If you make use of unyt in work that leads to a publication we would appreciate a mention in the text of the paper or in the acknowledgements along with a citation to our paper in the Journal of Open Source Software. You can use the following BibTeX:

@article{Goldbaum2018,
  doi = {10.21105/joss.00809},
  url = {https://doi.org/10.21105/joss.00809},
  year  = {2018},
  month = {aug},
  publisher = {The Open Journal},
  volume = {3},
  number = {28},
  pages = {809},
  author = {Nathan J. Goldbaum and John A. ZuHone and Matthew J. Turk and Kacper Kowalik and Anna L. Rosen},
  title = {unyt: Handle,  manipulate,  and convert data with units in Python},
  journal = {Journal of Open Source Software}
}

Or the following citation format:

Goldbaum et al., (2018). unyt: Handle, manipulate, and convert data with units in Python . Journal of Open Source Software, 3(28), 809, https://doi.org/10.21105/joss.00809

2.1.0 (2019-03-26)

This release includes a few minor new features and bugfixes for the 2.0.0 release.

• Added support for the matmul @ operator. See PR #80.

• Allow defining unit systems using Unit instances instead of string unit names. See PR #71.

• Fix incorrect behavior when uhstack is called with the axis argument. See PR #73.

• Add "rsun", "lsun", and "au" as alternate spellings for the "Rsun", "Lsun", and "AU" units. See PR #77.

• Improvements for working with code unit systems. See PR #78.

• Reduce impact of floating point round-off noise on unit comparisons. See PR #79.

2.0.0 (2019-03-08)

unyt 2.0.0 includes a number of exciting new features as well as some bugfixes. There are some small backwards incompatible changes in this release related to automatic unit simplification and handling of dtypes. Please see the release notes below for more details. If you are upgrading from unyt 1.x we suggest testing to make sure these changes do not siginificantly impact you. If you run into issues please let us know by opening an issue on GitHub.

• Dropped support for Python 2.7 and Python 3.4. Added support for Python 3.7.

• Added Unit.simplify(), which cancels pairs of terms in a unit expression that have inverse dimensions and made it so the results of unyt_array multiplication and division will automatically simplify units. This means operations that combine distinct dimensionally equivalent units will cancel in many situations. For example

  >>> from unyt import kg, g
  >>> print((12*kg)/(4*g))
  3000.0 dimensionless

  older versions of unyt would have returned 4.0 kg/g. See PR #58 for more details. This change may cause the units of operations to have different, equivalent simplified units than they did with older versions of unyt.

• Added the ability to resolve non-canonical unit names to the equivalent canonical unit names. This means it is now possible to refer to a unit name using an alternative non-canonical unit name when importing the unit from the unyt namespace as well as when a unit name is passed as a string to unyt. For example:

  >>> from unyt import meter, second
  >>> data = 1000.*meter/second
  >>> data.to('kilometer/second')
  unyt_quantity(1., 'km/s')
  >>> data.to('metre/s')
  unyt_quantity(1000., 'm/s')

  The documentation now has a table of units recognized by unyt along with known alternative spellings for each unit.

• Added support for unicode unit names, including μm for micrometer and Ω for ohm. See PR #59.

• Substantially improved support for data that does not have a float64 dtype. Rather than coercing all data to float64 unyt will now preserve the dtype of data. Data that is not already a numpy array will be coerced to a dtype by calling np.array internally. Converting integer data to a new unit will convert the data to floats, if this causes a loss of precision then a warning message will be printed. See PR #55 for details. This change may cause data to be loaded into unyt with a different dtype. On Windows the default integer dtype is int32, so data may begin to be recognized as int32 or converted to float32 where before it was interpreted as float64 by default.

• Unit registries are now associated with a unit system. This means that it’s possible to create a unit registry that is associated with a non-MKS unit system so that conversions to “base” units will end up in that non-MKS system. For example:

  >>> from unyt import UnitRegistry, unyt_quantity
  >>> ureg = UnitRegistry(unit_system='cgs')
  >>> data = unyt_quantity(12, 'N', registry=ureg)
  >>> data.in_base()
  unyt_quantity(1200000., 'dyn')

  See PR #62 for details.

• Added two new utility functions, unyt.unit_systems.add_constants and unyt.unit_systems.add_symbols that can populate a namespace with a set of unit symbols in the same way that the top-level unyt namespace is populated. For example, the author of a library making use of unyt could create an object that users can use to access unit data like this:

  >>> from unyt.unit_systems import add_symbols
  >>> from unyt.unit_registry import UnitRegistry
  >>> class UnitContainer(object):
  ...    def __init__(self):
  ...        add_symbols(vars(self), registry=UnitRegistry())
  >>> units = UnitContainer()
  >>> units.kilometer
  km
  >>> units.microsecond
  µs

  See PR #68.

• The unyt codebase is now automatically formatted by black. See PR #57.

• Add missing “microsecond” name from top-level unyt namespace. See PR #48.

• Add support for numpy.argsort by defining unyt_array.argsort. See PR #52.

• Add Farad unit and fix issues with conversions between MKS and CGS electromagnetic units. See PR #54.

• Fixed incorrect conversions between inverse velocities and statohm. See PR #61.

• Fixed issues with installing unyt from source with newer versions of pip. See PR #63.

• Fixed bug when using define_unit that caused crashes when using a custom unit registry. Thank you to Bili Dong (@qobilidob on GitHub) for the pull request. See PR #64.

We would also like to thank Daniel Gomez (@dangom), Britton Smith (@brittonsmith), Lee Johnston (@l-johnston), Meagan Lang (@langmm), Eric Chen (@ericchen), Justin Gilmer (@justinGilmer), and Andy Perez (@sharkweek) for reporting issues.

1.0.7 (2018-08-13)

Trigger zenodo archiving.

1.0.6 (2018-08-13)

Minor paper updates to finalize JOSS submission.

1.0.5 (2018-08-03)

unyt 1.0.5 includes changes that reflect the peew review process for the JOSS method paper. The peer reviewers were Stuart Mumfork (@cadair), Trevor Bekolay (@tbekolay), and Yan Grange (@ygrange). The editor was Kyle Niemeyer (@kyleniemeyer). The` unyt` development team thank our reviewers and editor for their help getting the unyt paper out the door as well as for the numerous comments and suggestions that improved the paper and package as a whole.

In addition we’d like to thank Mike Zingale, Meagan Lang, Maksin Ratkin, DougAJ4, Ma Jianjun, Paul Ivanov, and Stephan Hoyer for reporting issues.

• Added docstrings for the custom exception classes defined by unyt. See PR #44.

• Added improved documentation to the contributor guide on how to run the tests and what the PR review guidelines are. See PR #43.

• Updates to the text of the method paper in response to reviewer suggestions. See PR #42.

• It is now possible to run the tests on an installed copy of unyt by executing unyt.test(). See PR #41.

• Minor edit to LICENSE file so GitHub recognizes it. See PR #40. Thank you to Kyle Sunden (@ksunden) for the contribution.

• Add spatial frequency as a dimension and added support in the spectral equivalence for the spatial frequency dimension. See PR #38 Thank you to Kyle Sunden (@ksunden) for the contribution.

• Add support for Python 3.7. See PR #37.

• Importing unyt will now fail if numpy and sympy are not installed. See PR #35

• Testing whether a unit name is contained in a unit registry using the Python in keyword will now work correctly for all unit names. See PR #31.

• The aliases for megagram in the top-level unyt namespace were incorrectly set to reference kilogram and now have the correct value. See PR #29.

• Make it possible to take scalars to dimensionless array powers with a properly broadcasted result without raising an error about units. See PR #23.

• Whether or not a unit is allowed to be SI-prefixable (for example, meter is SI-prefixable to form centimeter, kilometer, and many other units) is now stored as metadata in the unit registry rather than as global state inside unyt. See PR #21.

• Made adjustments to the rules for converting between CGS and MKS E&M units so that errors are only raised when going between unit systems and not merely when doing a complicated unit conversion invoving E&M units. See PR #20.

• round(q) where q is a unyt_quantity instance will no longer raise an error and will now return the nearest rounded float. See PR #19.

• Fixed a typo in the readme. Thank you to Paul Ivanov (@ivanov) for the fix.

• Added smoot as a unit. See PR #14.

1.0.4 (2018-06-08)

• Expand installation instructions

• Mention paper and arxiv submission in the readme.

1.0.3 (2018-06-06)

• Fix readme rendering on pypi

1.0.2 (2018-06-06)

• Added a paper to be submitted to the Journal of Open Source Software.

• Tweaks for the readme

1.0.1 (2018-05-24)

• Don’t use setup_requires in setup.py

1.0.0 (2018-05-24)

• First release on PyPI.

• unyt began life as a submodule of yt named yt.units.

• It was separated from yt.units as its own package in 2018.