Closed chris-clem closed 1 year ago
Hi @chris-clem, great idea! On it. Would you be willing to test the patch, once it is done?
Nice! Sure, I can test it
Related to this: I don't know if adding the env variables to .bashrc
is the best place to do it. Some users might use zsh and others might use nnUnet seperately.
I added a env_vars.sh
file in the MOOSE repo dir that I source.
@chris-clem I have pushed a patch, can you do a git pull and check if the update helps with the request you have made? I am working on my potato laptop, which doesn't have MOOSE installed, so I cannot test it on my own. Many thanks for your suggestions and help - much appreciated!
@chris-clem : regarding the env_vars.sh, I like this solution. How do we do this? do you wanna make a PR request? or you want me to do this? I am fine with either :D!
I am running MOOSE on a large dataset at the moment. Will do it when the run is finsihed. Probably on Monday or Tuesday.
I will have a look at the env_var PR. Should not be too complicated.
Passt! I will await your PR 🎉, any help with managing the environment variables is highly appreciated 🙌🏽
Hi @chris-clem, I tested the patch, it seems to work on my end. Also I have released a new version. Closing this for now :D, keep me posted in case if it doesn't work in your end!
Is your feature request related to a problem? Please describe. If the environment variables are not loaded, MOOSE fails silently like so:
Describe the solution you'd like It would be nice to let the user know that the problem is that the
nnUNet_raw_data_base
,nnUNet_preprocessed
, etc. env variables are not set.