Closed hamidrezaomidvar closed 4 years ago
As I recall, we did have implemented this to trigger WRF fatal error if things went crazy: https://github.com/Urban-Meteorology-Reading/SUEWS/blob/47c08e5edea805ee976a9258f566190938225f9a/SUEWS-SourceCode/suews_ctrl_error.f95#L337-L344
These lines need to be activated when compiling by passing cpp
flag for preprocessing.
I agree with you
在 2020年5月15日,23:36,Ting Sun notifications@github.com 写道:
As I recall, we did have implemented this to trigger WRF fatal error if things went crazy: https://github.com/Urban-Meteorology-Reading/SUEWS/blob/47c08e5edea805ee976a9258f566190938225f9a/SUEWS-SourceCode/suews_ctrl_error.f95#L337-L344
These lines need to be activated when compiling by passing cpp flag for preprocessing.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
I see. Then it was definitely JASMIN problem. it has been very unstable recently because of the situation.
It seems to me that when SUEWS fatal error happens, it does not communicate with WRF error module and although the run stops, in the cluster it shows the job still running. It might be the problem of Jasmin but good to double check! not an urgent problem to look into now