...
Once your environment file is ready, you can use Tikky to perform the installation for you. You must decide where to install it, but use of HPCPERM is strongly recommended. Use of HOME, PERM or SCRATCH for such installations is discouraged for performance reasons.
For your convenience, a variable $TYKKY_PATH is defined by default to use your $HPCPERM/tykky, that you can use to place your environments:
| No Format |
|---|
conda-containerize new --mamba --prefix <install_dir>$TYKKY_PATH/<env_name> env.yml |
| Tip | ||
|---|---|---|
| ||
If your environment is a complex one, and you are performing the installation from a standard interactive login session, you may hit some limitations in the cpus available, amount of memory or temporary storage. For example, a typical AI/ML environment may require more than 20 GB of memory and 30 GB of local TMPDIR space. On top of that, creating the image is also a cpu-intensive task that may take some time if run on the default 2 cpus 1 cpu of a login session. We recommend you to either submit the installation as a batch job specifying higher cpus, memory or storage requirements, or do it interactively with
|
...
You may activate your new environment with the convenience tykky activate function, very similar to how you would do it with conda. If you installed your environment under $TYKKY PATH, then it is as simple as:
| No Format |
|---|
tykky activate <env_name> |
Of if you installed it somewhere else:
| No Format |
|---|
tykky activate <install_dir> |
...