-
Notifications
You must be signed in to change notification settings - Fork 15
Implementation of NormalizedReluBounding for non-zero thresholds #100
base: develop
Are you sure you want to change the base?
Conversation
for more information, see https://pre-commit.ci
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #100 +/- ##
========================================
Coverage 99.85% 99.85%
========================================
Files 23 23
Lines 1374 1374
========================================
Hits 1372 1372
Misses 2 2 ☔ View full report in Codecov by Sentry. |
…nemoi-models into feature/normalized_relu_bounding
for more information, see https://pre-commit.ci
Hello! Very cool feature. Have you done any training on this? Are there any specific variables where you would prefer doing this over simply using a std normalization? But I think I can see your point for the freezing temperature of the ocean. With a std normalization, you would not have an absolute zero. |
Yes, this bounding has now been tested for a couple of months. All the results I have shown regarding the surface ocean in the last weeks are run with this feature. The surface temperature is the only obvious test case for now, but when we have a 3D ocean, we will want this for all the vertical layers. I am sure use cases will also pop up for other model components in the future. |
This new approach can be used when applying the Relu bounding to a threshold value other than the default 0. An obvious use case is the ocean temperature, which should not go below the freezing temperature of the ocean (approx. 271.15 K). The threshold imputed to the function is normalised according to the normalisation scheme specified in the config file.
Here is an example call to be added to the config:
In case of multiple variables