Closed chris-clem closed 1 year ago
Hi @chris-clem, I am down with Covid and the other MOOSE members are on vacay. Many thanks for the detailed analysis.I will be able to look at it in detail next week. Sorry about the delay!
No problem, I hope you recover soon!
Did you get a chance to take a look?
@chris-clem I did, I like option 2...
Got it, thanks! I try to create a PR next week.
MOOSE v2.0 doesn't have any of these issues @chris-clem! Also a friend showed me your prezi from Fully-3D conference. Now you can actually integrate your models easily in MOOSEV2. Have a look at the readme!
Dear MOOSE team,
I mentioned the following issue in another issue and wanted to create a new one for it:
Originally posted by @chris-clem in https://github.com/QIMP-Team/MOOSE/issues/42#issuecomment-1286930959.
As a quick solution, I added a
env_vars.sh
file in the MOOSE repo dir that I source instead of.bashrc
. In the meantime, I have searched how people are handling the problem in general and found the following possibilities:.env
file in the repo dir and load it withpython-dotenv
as explained here..env
file in the repo dir and recommend users to use direnv, which then automatically loads the env variables when changing in the MOOSE dir.The downside of 1. is that it requires a new dependency, the downside of 2. that it requires a new program, and the downside of 3. is that it requires conda for managing the environment.
What do you think is the best option?