You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to introduce checks in the coupler that ensure that all fields passed from components are free of NaN values.
There is also value in having some other physical checks (like certain fields that should be non-negative), but feeling from a number of discussions is that those physical checks belong in components, not in the coupler.
The text was updated successfully, but these errors were encountered:
Check flds for nan
Checks incoming component fields for NaN in the coupler, fail on first NaN found, report
component name and instance, field name and 1d global index into field. Add a test in scripts_regression_tests.py that checks this feature is working.
Test suite: scripts_regression_tests.py , PFS.f19_g17.B1850.cheyenne_intel with and without to measure impact on performance (negligible)
Test baseline:
Test namelist changes:
Test status: bit for bit
Fixes#1757
User interface changes?:
Update gh-pages html (Y/N)?:
Code review:
We want to introduce checks in the coupler that ensure that all fields passed from components are free of NaN values.
There is also value in having some other physical checks (like certain fields that should be non-negative), but feeling from a number of discussions is that those physical checks belong in components, not in the coupler.
The text was updated successfully, but these errors were encountered: