The Configuration file
The ELBO configuration is specified in YAML in a configuration file. Let's look at its contents.
The configuration file, typically named
elbo.yamlhas the following properties:
The name of your ML training task
"Hello, ELBO 💪"
The class of GPU you want to request. This can be one of the following:
A setup script that will be run prior to calling the training code
The main training code. The task execution will call this file directly.
The directory where this task is present. Usually the current directory. This directory will be zipped and uploaded for running the task.
Please make sure all the files and scripts needed to run the training code are present in this directory.
The directory where your code will place model checkpoints, plots, generated files etc. The ELBO service will package this directory and save it for you to download after the task is complete.
Setting this to
Tip: If you are submitting the task for the first time, you may want to run the training task on an
Economyclass machine and then move to higher classes when you see the model converging after a few epochs.
Here is a sample configuration with comments on what each property means:
# ELBO Sample Config File for MNIST Classifier Task
# All paths are relative to where the `elbo.yaml` file is placed
name: "Train MNIST Classifier"
# The GPU class to use - Economy, MidRange, HighEnd, All
# The script to run for setting up the environment. For example - installing packages
# on Ubuntu
# The PIP requirements file. ELBO will install the requirements specified in this
# file before launching the task.
# The main entry point in the task. Once the script exits or terminates, the task
# is considered complete.
# The task directory, relative to this file. This directory will be tar-balled and sent to ELBO task executor for
# Artifacts directory. This is the directory that will be copied over as output. All model related files -
# checkpoints, generated samples, evaluation results etc. should be placed in this directory.