Conversation
forsyth2
added
the
semver: new feature
| "bundles_walltime": "02:00:00", | ||
| "constraint": "", | ||
| # To run this test, replace conda environment with your e3sm_diags dev environment | ||
| # TODO: Get conda working on Andes |
There was a problem hiding this comment.
I tried following the conda directions for E3SM Diags at https://e3sm-project.github.io/e3sm_diags/_build/html/master/install.html#others-local, but I get:
$ which conda
/usr/bin/which: no conda in (/sw/andes/spack-envs/base/opt/linux-rhel8-x86_64/gcc-9.3.0/openmpi-4.0.4-skxqfeiocc5jtuw3y6dwtnxzzqjp5ffs/bin:/sw/andes/gcc/9.3.0/bin:/sw/sources/hpss/bin:/sw/andes/bin:/opt/ibm/spectrumcomputing/lsf/10.1/linux3.10-glibc2.17-x86_64/etc:/opt/ibm/spectrumcomputing/lsf/10.1/linux3.10-glibc2.17-x86_64/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sw/sources/cgroup_tool/bin:/opt/puppetlabs/bin:/usr/lpp/mmfs/bin:/opt/dell/srvadmin/bin)
I tried following the mamba directions for zppy at https://e3sm-project.github.io/zppy/_build/html/main/getting_started.html#others-local, but I get:
$ which mamba
/usr/bin/which: no mamba in (/sw/andes/spack-envs/base/opt/linux-rhel8-x86_64/gcc-9.3.0/openmpi-4.0.4-skxqfeiocc5jtuw3y6dwtnxzzqjp5ffs/bin:/sw/andes/gcc/9.3.0/bin:/sw/sources/hpss/bin:/sw/andes/bin:/opt/ibm/spectrumcomputing/lsf/10.1/linux3.10-glibc2.17-x86_64/etc:/opt/ibm/spectrumcomputing/lsf/10.1/linux3.10-glibc2.17-x86_64/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sw/sources/cgroup_tool/bin:/opt/puppetlabs/bin:/usr/lpp/mmfs/bin:/opt/dell/srvadmin/bin)
@xylar @tomvothecoder Would either of you know how to get some form of conda working on Andes?
There was a problem hiding this comment.
I think you just need to log in with a new terminal after you install. The instruction:
Do you wish the installer to initialize Miniconda3 by running conda init? [yes|no] yes
is adding something to your .bashrc and that doesn't take effect unless you either do source .bashrc or you log in to a fresh terminal.
There was a problem hiding this comment.
If that doesn't work, you should instead do:
source ~/mambaforge/etc/profile.d/conda.sh
source ~/mambaforge/etc/profile.d/mamba.sh
mamba activate
if you installed Miniconda3 instead of Mambaforge --
source ~/miniconda3/etc/profile.d/conda.sh
conda activate
There was a problem hiding this comment.
source ~/mambaforge/etc/profile.d/conda.sh source ~/mambaforge/etc/profile.d/mamba.sh mamba activate
Ah, that appears to work, thanks!
|
@forsyth2 I was recently struggling with this as well. I never for it fully working, but I can get the unified env with this: |
|
To do: need to figure out where to transfer the input files (for integration tests -- i.e., the output of the simulation). What workspace has a large enough space quota? (The directory of |
3 participants
Andes support. Resolves #450.