floating point exception issue #211
Answered
by
cenlinhe
SmithSimmon
asked this question in
Q&A
-
Beta Was this translation helpful? Give feedback.
Answered by
cenlinhe
Sep 11, 2024
Replies: 1 comment 1 reply
-
What model time step are you using? If you are using an hourly timestep (NOAH_TIMESTEP = 3600), then please reduce it to half-hourly (NOAH_TIMESTEP = 1800). The issue might be caused by the inaccurate numerical solution under a large timestep. |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
SmithSimmon
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What model time step are you using? If you are using an hourly timestep (NOAH_TIMESTEP = 3600), then please reduce it to half-hourly (NOAH_TIMESTEP = 1800). The issue might be caused by the inaccurate numerical solution under a large timestep.
If you want to know the exact grid, you could add printout code in the NoahmpDriverMain module for the I, J point.