NaN in input field error #3054
-
Another issue I have run into with my runs is the following:
I have traced this error to the sfc initial condition files I am using, which do indeed included NaNs as the missing value. I have a set of working sfc ic files from the regression tests that do not include any NaNs which don't produce this issue. I'm assuming it is the missing field NaNs that are causing the crash - is there a flag that can be set to cause the code to ignore those NaNs, do we need to use a different missing value, or is it potentially a different problem entirely? I've attached the full log file here. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Some digging around uncovered the answer - there is a check purely for the presence of NaNs that the sfc_data files were failing, because missing values were being set to NaN. Simply replacing the NaNs in the file with -1e30 allowed the model to run without blowing up, so clearly those values were not actually being used in any of the calculations. |
Beta Was this translation helpful? Give feedback.
Some digging around uncovered the answer - there is a check purely for the presence of NaNs that the sfc_data files were failing, because missing values were being set to NaN. Simply replacing the NaNs in the file with -1e30 allowed the model to run without blowing up, so clearly those values were not actually being used in any of the calculations.