You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compared to Unitful.jl, the pros for using UDUnits.jl are
In place conversion via Converter function.
Support expressions like W m^2 (although, it doesn't support W * m^2, but this can easily be fixed by parsing the expression beforehand and I don't think any of the diagnostics write units like this)
Should be compatible with NetCDF files outside of CliMA since "the values of the units attributes [of NetCDF files] are character strings that are recognized by UNIDATA’s UDUNITS package..." in section 3.1 of the CF Conventions. Note that the UNIDATA’s UDUNITS package is a C library and UDUnits.jl is a Julia port of it.
Support units that we care about like degree_east and is generally more flexible with what units it can parse. For example, s, sec, secs, second, and seconds are all recognizable by UDUnits.jl and only s is recognizable by Unitful.jl. For another example, m**2 (Python syntax) is parseable by UDUnits.jl, but is not by Unitful.jl.
A possible replacement for Unitful.jl is UDUnits.jl.
Compared to Unitful.jl, the pros for using UDUnits.jl are
Converter
function.W m^2
(although, it doesn't supportW * m^2
, but this can easily be fixed by parsing the expression beforehand and I don't think any of the diagnostics write units like this)degree_east
and is generally more flexible with what units it can parse. For example,s
,sec
,secs
,second
, andseconds
are all recognizable by UDUnits.jl and onlys
is recognizable by Unitful.jl. For another example,m**2
(Python syntax) is parseable by UDUnits.jl, but is not by Unitful.jl.The cons for using UDUnits.jl are
The text was updated successfully, but these errors were encountered: