Remove `mamba` command and switch to Miniforge3

E3SM-Project / polaris

Testing and analysis for OMEGA, MPAS-Ocean, MALI and MPAS-Seaice

BSD 3-Clause "New" or "Revised" License

6 stars 13 forks source link

Remove `mamba` command and switch to Miniforge3 #161

Closed xylar closed 9 months ago

xylar commented 9 months ago

This is the equivalent of the Compass PR https://github.com/MPAS-Dev/compass/pull/751.

Checklist

[x] User's Guide has been updated
[x] Developer's Guide has been updated
[x] Documentation has been built locally and changes look as expected
[x] Testing comment in the PR documents testing used to verify the changes

xylar commented 9 months ago

Testing

I created a new development environment for polaris using a miniforge3 installation on my laptop.

mark-petersen commented 9 months ago

with this commit, should we now use

./configure_polaris_envs.py  --conda /usr/projects/climate/mpeterse/miconda3 # on LANL IC
./configure_polaris_envs.py  --conda ~/miconda3 # everywhere else

or create some other conda directory? Does it matter if polaris and compass use the same ~/miconda3 directory, if I am using them at the same time? Thanks.

xylar commented 9 months ago

You should do:

./configure_polaris_envs.py  --conda /usr/projects/climate/mpeterse/miniforge3

on LANL IC. (We don't recommend using Miniconda3 and it would be confusing to call a miniforge3 installation miniconda3 or miconda3.)

xylar commented 9 months ago

or create some other conda directory? Does it matter if polaris and compass use the same ~/miconda3 directory, if I am using them at the same time? Thanks.

They should use the same ~/miniforge3 directory, yes.

xylar commented 9 months ago

It should work to use an existing ~/miniconda3 or ~/mambaforge if you already have one. You don't need to create a new ~/miniforge3 directory if you already have conda installed somewhere.