Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

STY: Use mbar and Pa for units of pressure #356

Open
wants to merge 5 commits into
base: dev/emc
Choose a base branch
from

Conversation

DWesl
Copy link

@DWesl DWesl commented Aug 9, 2024

Description

Fixes #350 by using Pa instead of pa and mbar instead of mb as units of pressure.
This should make the units of pressure generated by this repository machine-readable.
NOAA-EMC/fv3atm#859 makes other units machine-readable

Replaces #355

How Has This Been Tested?

I made similar changes to a version of this repository in global-workflow, which I then compiled and ran. This produced netCDF history files with machine-readable units (specifically the python pint program, though I also checked with UDUnits).

Checklist:

Please check all whether they apply or not

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules

DWesl and others added 3 commits June 28, 2024 14:59
It should keep my unit software from thinking I measure pressure in picoannum
My unit software thinks the latter is millibarn, a unit of area for atomic scattering.
This may help with CF compliance.
My unit software reads "pa" as "picoannum", a unit of time on the order of microseconds, rather than as "pascals", the unit of pressure.
@laurenchilutti
Copy link
Contributor

Can you please resolve the conflicts in the file driver/fvGFS/fv_nggps_diag.F90? I think all you will need to do is merge the dev/emc branch into your sty-units-fixes branch and resolve the conflicts from there.

@bensonr bensonr closed this Sep 6, 2024
@bensonr bensonr reopened this Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants