Feature: Add input/output tensor component ranges to network files #138
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 PR facilitates storing the range of values encountered in the training data for purposes of
See the cloud-microphysics subdirectory for an example of mechanics and utility of training-data normalization to aid convergence.
BREAKING CHANGE: network files will now contain a tensor_range JSON objects for inputs followed by a tensor_range JSON object for outputs, each of which stores a string label ("inputs" for the first and "outputs" for the second) followed by "minima" arrays and "maxima" arrays.