You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to allow users to set an option in their experiment .yaml file so that in this case a new clean virtual environment is created and all dependencies are installed. E.g. something like install_venv_at_startup in the meta_job_args. At the beginning of the experiment the toolbox searches for a requirements.txt file in the root directory and creates either a clean venv or a conda environment before starting up the experiment. We also have to make sure that mle_toolbox is being installed but the user does not have to configure it since we only need the DeepLogger, get_configs_ready and set_random_seeds functionalities.
The text was updated successfully, but these errors were encountered:
Later on this should also be made compatible with docker/singularity containers. We only need to make sure that drive mounting and driver installations are somehow managed. Talk to @wllhf and Florian Blume about their slurm HPC setup.
RobertTLange
changed the title
Option to install environment at experiment startup
Option to install environment/container at experiment startup
Dec 11, 2021
I would like to allow users to set an option in their experiment
.yaml
file so that in this case a new clean virtual environment is created and all dependencies are installed. E.g. something likeinstall_venv_at_startup
in themeta_job_args
. At the beginning of the experiment the toolbox searches for arequirements.txt
file in the root directory and creates either a cleanvenv
or aconda
environment before starting up the experiment. We also have to make sure thatmle_toolbox
is being installed but the user does not have to configure it since we only need theDeepLogger
,get_configs_ready
andset_random_seeds
functionalities.The text was updated successfully, but these errors were encountered: