Location of container .bashrc file on Cluster

[fgvangessel-umd]

For the airfoil problem, upon launching the container the machaero-specific .bashrc file must be sourced to add the appropriate python libraries and executables to the path. On Zaratan the location of that .bashrc file differs from the currently hard-coded path, Specifically,

# Existing path which throws error
"source ~/.bashrc_mdolab && cd /home/mdolabuser/mount/engibench && mpirun -np "

# Zaratan singularity path that is valid                
"source /home/mdolabuser/.bashrc_mdolab && cd /home/mdolabuser/mount/engibench && mpirun -np "

I'm looking for suggested solutions which are minimally invasive but would allow compatibility across clusters (i.e. Euler and Zaratan)

[ffelten]

I guess doing source /home/mdolabuser/.bashrc_mdolab will work in both cases, as I expect ~ to point to /home/mdolabuser

[fgvangessel-umd]

Hmm it looks like the environmental settings outside the container persist upon entry so ~ points to /home/fvangess/scratch rather than /home/mdolabuser so that solution wouldn't work.

[ffelten]

I meant what if we hardcode /home/mdolabuser instead of using ~. I guess it will be fine for Docker. I just tested that locally and it seems to work. Will do a PR so we can see the changes I'm mentioning.

[ffelten]

See #135