Issue in running mhm model

[wk1984]

I prepared input files and *.nml file for running my test case. When I run the model, it seems to stop at a step (see attached figure).

I also attached all files here for further discussion and checking.

moselle_domain.zip

[BryanSouzaM]

Hey! I think that you just don't have these geological units in the corresponding .asc file of your geological .txt file.

[wk1984]

Hey @BryanSouzaM, thank you for replying. But I think it may not solve the issue because I already set all pixels to geological unit = 1. For double checking, I now remove the units (2-10) in geological.txt and mhm_parameters.nml. The issue is still the same. Confusing for me.

[BryanSouzaM]

I think that the Geological message is just an Warning.

Maybe you need to check the 169 outlets of the model?

Also, the gauge is not coincident with the facc.

Additionally, your gauges folder is empty.

But anyway, the error may not stem from any of my comments.

But at the moment when your model froze, the mHM is operating the mRM (opening dem, fdir and facc, maybe?):

My model on the left for comparison:

[BryanSouzaM]

@wk1984

Checking your data, I noticed that the flow direction (fdir) is incorrectly oriented. "1" should be towards the right, and yours is towards the southeast.

[wk1984]

Yeah, it works when I fix the fdir issue. Many thanks for your help.

[cuneyd]

Hello,

I have a similar issue in my setup for Cyprus island. Your comments would be very much appreciated.

Error message in mhm:
Something went wrong during L11_link_location, movedownonecell got stuck in infinite loop at cell ( 1328 155

facc fdir and idgauges files in a zip folder:
fdir_facc_cyprus.zip

Thanks in advance,
Cüneyd

[BryanSouzaM]

Hey Cüneyd!

I think you should open a new discussion for posterior consulting.

Try this fdir.asc (It's just a test, it might not solve the problem. But it replaces the zero values with -9999.)

fdir.zip

But looking at your file, it seems that this problematic area is not important for the simulation, am I wrong? Maybe using a mask to remove it would work...

And again, maybe you should start a new discussion since this one has been closed.

Vinicius Bryan