WARNING: tmax smaller than tmin at doy and Program received signal SIGSEGV: Segmentation fault - invalid memory reference. #136
Unanswered
ayeshaspace
asked this question in
Q&A
Replies: 1 comment
-
|
It's great that you are trying to set up mHM. It's hard to diagnose this issue from far away. Let's have a look at this newt week. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I am setting up the mHM model for my basin data. After ensuring the environment was configured correctly, I encountered an error while running the model from version 5.12, which I understand may be due to the calculation of PET using tmax and tmin with the Hargreaves approach. I found that this issue was already discussed and fixed in version 5.13 (https://git.ufz.de/mhm/mhm/-/issues/242).

Therefore, I upgraded from version 5.12 to 5.13 and tried running the model using ./mhm --quiet. However, I am now facing new errors.
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x7d6feb223960 in ???
#1 0x7d6feb222ac5 in ???
#2 0x7d6feae4251f in ???
#3 0x5d834fe1b094 in __mo_meteo_handler_MOD_get_corrected_pet
#4 0x5d834fe6cb4b in __mo_mhm_interface_run_MOD_mhm_interface_run_do_time_step
#5 0x5d834fe6984c in __mo_mhm_eval_MOD_mhm_eval
#6 0x5d834fd36bdd in mo_mhm_interface_MOD_mhm_interface_run
#7 0x5d834fd34f5d in MAIN
#8 0x5d834fd34fa3 in main
Segmentation fault (core dumped)
I have carefully checked the meteorological grids, including data types, etc, multiple times, but I still cannot identify the cause. What could be the possible reason for this?
Beta Was this translation helpful? Give feedback.
All reactions