Feature: Ability to set desired NetCDF output precision from config#105
Merged
fmalatino merged 4 commits intoNOAA-GFDL:developfrom Mar 13, 2025
Merged
Feature: Ability to set desired NetCDF output precision from config#105fmalatino merged 4 commits intoNOAA-GFDL:developfrom
fmalatino merged 4 commits intoNOAA-GFDL:developfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces methods for setting the desired precision of output when using the
netcdfoutput format. Within a config file, the precision can be specified as follows:The
Floatoption will use whatever is the current value of thePACE_FLOAT_PRECISIONenvironment variable for output precision.The
float32option will set the output precision to benumpy.float32.The
float64option will set the output precision to benumpy.float64.The default option is
Float.The latter two options allow for instances when the desired run precision, as set by
PACE_FLOAT_PRECISION, will be different than the required output precision.If the combination of
float64is used withPACE_FLOAT_PRECISION = 32, a warning will be raised.How Has This Been Tested?
Tested using the current set of unit tests in the workflow CI
Checklist: