Network Drive Issues and Output Directories

[wishnewski]

Hi!

Question 1:

Executing the provided examples worked for out seamlessly, however only as long as I try to run the model on my home C: drive (mhm-venv is on :C aswell). As soon as I try to run the exact same model files from a network drive (tried several different) I run into the following issue:

Working directory: h:\mHM\workshop\mhm\test_domain
Using namelists:
     mhm.nml
     mhm_parameter.nml
     mhm_outputs.nml

File does not exist: mhm.nml
STOP 1

Working on C: is not a problem, I was just interested if that is a known problem or if its likely rather due to issues with my network drive configurations.

Question 2:

Does the output directory, which is specified in mhm.nml always need to exist before executing the model, or is it also possible to adapt the respective command in the file to create the specified output folder "on the run" if not existing?

Thanks for the help!

[StephanThober]

On Question 1: please try mhm -h, you can also specify the location of configuration files explicitly. Maybe that helps.

On Question 2: Yes, the folder needs to exist before mHM is run.

[wishnewski]

Thanks for the quick reply! Regarding Question 1: unfortunately this does not seem to fix the issue. Even when explicitly specifying the locations, the problem remains. The screenshot from the total commander also confirms that the files in the specified directory exist indeed.

[StephanThober]

@MuellerSeb : have you encountered such an issue before? It may be related to the OS.

[MuellerSeb]

This is hard to debug. There are many layers between mHM and the OS on Windows, since we use the msys2 based compilers from conda that convert file system interactions from the unix based GNU compilers to the windows file system.

My takeaway here is: don't use paths to a network drive with mHM on Windows.