Issues in running mHM #111
Replies: 3 comments 17 replies
-
I believe that all layers need to be multiples of each other and have the same extensions. L0, for example, doesn't follow this rule |
Beta Was this translation helpful? Give feedback.
-
Dear all Could you please help diagnose the cause of this segmentation fault? Are there specific checks or debugging steps you recommend to resolve this issue? Thank you for your time and support. Please let me know if you need additional details or files. |
Beta Was this translation helpful? Give feedback.
-
Great to see you got more meaningful runtime error message using the debug executable. As per the message, you have at least one occurrence of -9998 in one or more of your input soil maps. Finding the -9998/s and replacing it/them by -9999 (standard noData value) should help. Meanwhile, also please share the soil classification file (or screenshot of) you are using for your setup for a quick check. Cheers |
Beta Was this translation helpful? Give feedback.
-
Dear mHM expert
Recently, I have set up and prepared all the input of mHM. I am running mHM across the whole Nile River Basin (3,176,541 km2). I got this attached error, and I think it is in regard to my Latlon file.
L0 = 0.00902777785
L1 = 0.25
L11 = 0.5
I have attached the error and the information of latlon.nc for your reference.
I am looking for your suggestion and recommendation to solve this issues
mhm.zip
header_1.txt
header_2.txt
header_3.txt
Beta Was this translation helpful? Give feedback.
All reactions