Running jobs
This section shows how to run jobs on Nimbo. Warning: It's really easy.

nimbo run

To run a script on an AWS instance, all you need to do is run:
nimbo run "your-script-command"
Nimbo will set everything up according to your nimbo-config.yml file. For example, if you're running a training job on MNIST you might run:
nimbo run "python --epochs=10 --lr=3e-4"
The quotes " " around the command are necessary to allow you to pass any arbitrary command to Nimbo. In fact, you don't have to run a python command; you can run any command you want, and Nimbo will run it on the remote machine.
If you choose to run a bash script, remember to activate the conda environment inside of it, since the environment activated by Nimbo will not propagate into your bash script (but you don't have to create the environment - Nimbo already takes care of that).
If you press Ctrl-C while the instance is running, Nimbo will automatically delete the instance so you do not have to do it manually. Make sure you press Ctrl-C only once for a graceful clean-up.
Nimbo will try to sync all the files that are tracked on git in the current folder (including changes that aren't committed). If no git is detected on the current folder, Nimbo will sync all the python files.

Sync results and check logs

Nimbo will have stored your results in S3, according to the fields in nimbo-config.yml . Results are sent from the instance to S3 every 5 seconds so even jobs that failed halfway through will have their results backed up. To download the results into your computer simply run:
nimbo pull results
Additionally, Nimbo stores logs with the full output of nimbo run in a nimbo-logs folder of your results path. If your job fails or stops for whatever reason, the easiest way to debug it is to sync the logs using the command:
nimbo pull logs

Running in the background and other options

If you want your job to run in the background (i.e. launch the job without needing an active terminal session), you can set run-in-background: yes.
If you don't want Nimbo to automatically delete the instance upon job completion or when there's an error (e.g. you might want to SSH into the instance for debugging), you can change the config parameter persist. If this value is yes , the instance will not be deleted.

More commands and options

You can find a list of common commands with example outputs in the Useful Commands section, and other commands in the All Commands section.
You can also find a list of all the supported Nimbo configuration fields in the Config Options section.
Last modified 7mo ago