Initial prototype for wandb sweep

[jcohenadad]

Checklist

GitHub

• I've given this PR a concise, self-descriptive, and meaningful title
• I've linked relevant issues in the PR body
• I've applied the relevant labels to this PR
• I've assigned a reviewer

PR contents

• I've consulted ivadomed's internal developer documentation to ensure my contribution is in line with any relevant design decisions
• I've added relevant tests for my contribution
• I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description

Initial prototype for using Wandb sweep with ivadomed. Feedback welcome!

Linked issues

Resolves #1124

[jcohenadad]

need to add input params there

[coveralls]

Pull Request Test Coverage Report for Build 3761546981

• 0 of 9 (0.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.1%) to 74.443%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
ivadomed/scripts/train_wandb_sweep_hyperparam.py	0	9	0.0%

Totals
Change from base Build 3744318191:	-0.1%
Covered Lines:	4614
Relevant Lines:	6198

---

💛 - Coveralls

[naga-karthik]

Because of the time constraint, I thought a quick solution for running sweeps is to directly run from the wandb dashboard. On the project page, there is an option called "Sweeps" on the left-most column and wandb automatically suggests a list of hyperparameters to try (based on the previous runs) and lets us initialize and run the sweep. I tried on the spine-generic tutorial and it does not work because ivadomed is constrained to get parameter from the config file so even by specifying the hyperparameters separately does not start the sweep.

Next thing to-do:

• Refer to ivadomed_automate_training.py to see how ivadomed can be called from the file itself (without requiring the command line)