-
Notifications
You must be signed in to change notification settings - Fork 354
Add _FillValue to all active and debug tracer fields #571
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
Conversation
Nice work @wenshanw! Exactly what we discussed on Friday. |
Note: This PR is based off of #533 so it should be rebased onto ocean/develop after that PR is merged and develop is merged into ocean/develop. |
Change name of missing value attribute from missing_value to _FillValue This PR changes the name of the missing value attribute in netCDF output files from missing_value to _FillValue. The _FillValue attribute can be set by adding a missing_value to individual variables and var_arrays in the Registry file (See #571 for an example). This change is needed because some analysis software, notably NCO, does not support the missing_value attribute by default and expects _FillValue instead.
@wenshanw, this branch needs to be rebased onto If my branch looks good to you, you can just do a hard reset to mine. Go to the local directory where you have your
Then, do a force push to your remote. The exact syntax will depend on what you named your remote. I called it
|
TestingIn my rebased branch, I ran
There are
Looking at The remaining 5 tracer variables are a good start but we would need
@wenshanw, I think you mentioned on at least two different calls that you thought all the variables from In any case, after the rebase, I think there's a considerable amount of work to do before |
@wenshanw, could you change the name of the PR to something like "Add _FillValue to all active and debug tracer fields"? In the description of the PR at the top, could you edit to change "active tracers" to "active and debug tracers" in both items? |
@xylar I am sorry I somehow had the impression to use this version. I have another version that I added So we've done rebased here, right? (after I force-pushed your |
@xylar I remove the |
Yes, by resetting to my branch and force-pushing, these commits are now "based" off of the current
Yes, that's right.
That's something for us to look into. One possibility is that MPAS variables default to being filled with zeros unless a different default value is set. But setting the fill value is supposed to also set that as the new default. So there must be somewhere that tendency variables get set to zero explicitly. @mark-petersen, could you help us track down where that is? |
@mark-petersen, I think this is ready to review. I think it might make sense to add fill values to just these 5 variables as a starting point and have a follow-up PR for the remaining variables. Does that seem okay to you? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR does, indeed, add _FillValues
to the following five variables in timeSeriesStatsDaily
output:
timeDaily_avg_activeTracers_temperature:_FillValue = 9.96920996838687e+36 ;
timeDaily_avg_activeTracers_salinity:_FillValue = 9.96920996838687e+36 ;
timeDaily_avg_debugTracers_tracer1:_FillValue = 9.96920996838687e+36 ;
timeDaily_avg_debugTracers_tracer2:_FillValue = 9.96920996838687e+36 ;
timeDaily_avg_debugTracers_tracer3:_FillValue = 9.96920996838687e+36 ;
I want to do some additional testing (including checking the EC60to30
mesh and timeSeriesStatsMonthly
) once fill values are in all variables.
1, Added the
_FillValue
attribute to active and debug tracers in the output NetCDF files.2, Replaced
-1e34
with_FillValue
in active and debug tracers.