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

[python #IQN-702077]: inconsistency in metpy constants

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 #IQN-702077]: inconsistency in metpy constants
  • Date: Mon, 07 Nov 2022 13:21:31 -0700
Greetings!

Good catch! The documentation is incorrect--the value given in code has the 
correct value that goes along with the attached units of KJ/(K Kg).

This was fixed in this Pull Request:

  https://github.com/Unidata/MetPy/pull/2656

And will be included in the next release, which will coerce the value to J/(Kg 
K). If you're using the unit-handling properly, there should be no change.

Cheers!

Ryan

> Hi
> The documentation gives the water_specific_heat in units of J (K Kg)-1. 
> However, on accessing it gives kilojoules /kelvin /kilogram. Could you please 
> clarify.
> 
> Best wishes


Ticket Details
===================
Ticket ID: IQN-702077
Department: Support Python
Priority: Low
Status: Closed
===================
NOTE: All email exchanges with 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.