Add static scale_factor/add_offset/_FillValue to awips_tiled GLM config #1537
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.
This is purely a configuration change to the configuration file used by the
awips_tiled
writer. This change is specific to the GLM "Full Disk" file scheme used by AWIPS and only effects the "Flash_extent_density" variable. The reason for this change is an apparent bug in AWIPS where for only the FED variable, the scale_factor/add_offset/_FillValue are ignored. In the best case we would use a scale_factor of 1.0 and add_offset of 0.0, but AWIPS, for some reason, does not allow "identity" scalings so 1.0 is not allowed. The change in this PR makes the scale_factor as close to 1.0 as possible for a 32-bit float so that the values in the file should nearly represent the original values.The AWIPS bug is still being investigated, but in the mean time this workaround should be backwards compatible and allow us to continue our work.