2020-03-03 15:52:16 +00:00
|
|
|
Hyperparameters
|
|
|
|
---------------
|
|
|
|
Lightning has utilities to interact seamlessly with the command line ArgumentParser
|
|
|
|
and plays well with the hyperparameter optimization framework of your choice.
|
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
ArgumentParser
|
|
|
|
^^^^^^^^^^^^^^
|
|
|
|
Lightning is designed to augment a lot of the functionality of the built-in Python ArgumentParser
|
|
|
|
|
|
|
|
.. code-block:: python
|
|
|
|
|
|
|
|
from argparse import ArgumentParser
|
|
|
|
|
|
|
|
parser = ArgumentParser()
|
|
|
|
parser.add_argument('--layer_1_dim', type=int, default=128)
|
|
|
|
|
|
|
|
args = parser.parse_args()
|
|
|
|
|
|
|
|
This allows you to call your program like so:
|
|
|
|
|
|
|
|
.. code-block:: bash
|
|
|
|
|
|
|
|
python trainer.py --layer_1_dim 64
|
|
|
|
|
|
|
|
|
|
|
|
Argparser Best Practices
|
2020-03-03 15:52:16 +00:00
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^
|
2020-04-26 13:20:06 +00:00
|
|
|
It is best practice to layer your arguments in three sections.
|
2020-03-03 15:52:16 +00:00
|
|
|
|
2020-04-26 14:57:26 +00:00
|
|
|
1. Trainer args (gpus, num_nodes, etc...)
|
|
|
|
2. Model specific arguments (layer_dim, num_layers, learning_rate, etc...)
|
|
|
|
3. Program arguments (data_path, cluster_email, etc...)
|
2020-04-26 13:20:06 +00:00
|
|
|
|
|
|
|
We can do this as follows. First, in your LightningModule, define the arguments
|
|
|
|
specific to that module. Remember that data splits or data paths may also be specific to
|
|
|
|
a module (ie: if your project has a model that trains on Imagenet and another on CIFAR-10).
|
2020-03-03 15:52:16 +00:00
|
|
|
|
|
|
|
.. code-block:: python
|
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
class LitModel(LightningModule):
|
|
|
|
|
|
|
|
@staticmethod
|
|
|
|
def add_model_specific_args(parent_parser):
|
|
|
|
parser = ArgumentParser(parents=[parent_parser], add_help=False)
|
|
|
|
parser.add_argument('--encoder_layers', type=int, default=12)
|
|
|
|
parser.add_argument('--data_path', type=str, default='/some/path')
|
|
|
|
return parser
|
|
|
|
|
|
|
|
Now in your main trainer file, add the Trainer args, the program args, and add the model args
|
|
|
|
|
|
|
|
.. code-block:: python
|
|
|
|
|
|
|
|
# ----------------
|
|
|
|
# trainer_main.py
|
|
|
|
# ----------------
|
2020-03-03 15:52:16 +00:00
|
|
|
from argparse import ArgumentParser
|
|
|
|
|
|
|
|
parser = ArgumentParser()
|
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
# add PROGRAM level args
|
|
|
|
parser.add_argument('--conda_env', type=str, default='some_name')
|
|
|
|
parser.add_argument('--notification_email', type=str, default='will@email.com')
|
|
|
|
|
|
|
|
# add model specific args
|
|
|
|
parser = LitModel.add_model_specific_args(parser)
|
2020-03-06 19:43:17 +00:00
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
# add all the available trainer options to argparse
|
|
|
|
# ie: now --gpus --num_nodes ... --fast_dev_run all work in the cli
|
2020-03-06 19:43:17 +00:00
|
|
|
parser = pl.Trainer.add_argparse_args(parser)
|
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
hparams = parser.parse_args()
|
2020-03-03 15:52:16 +00:00
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
Now you can call run your program like so
|
|
|
|
|
|
|
|
.. code-block:: bash
|
|
|
|
|
|
|
|
python trainer_main.py --gpus 2 --num_nodes 2 --conda_env 'my_env' --encoder_layers 12
|
|
|
|
|
|
|
|
Finally, make sure to start the training like so:
|
|
|
|
|
|
|
|
.. code-block:: bash
|
|
|
|
|
|
|
|
hparams = parser.parse_args()
|
|
|
|
|
|
|
|
# YES
|
|
|
|
model = LitModel(hparams)
|
|
|
|
trainer = Trainer.from_argparse_args(hparams, early_stopping_callback=...)
|
|
|
|
|
|
|
|
# NO
|
2020-04-26 14:57:26 +00:00
|
|
|
# model = LitModel(learning_rate=hparams.learning_rate, ...)
|
|
|
|
#trainer = Trainer(gpus=hparams.gpus, ...)
|
2020-04-26 13:20:06 +00:00
|
|
|
|
|
|
|
|
|
|
|
LightiningModule hparams
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
Normally, we don't hard-code the values to a model. We usually use the command line to
|
|
|
|
modify the network and read those values in the LightningModule
|
2020-03-03 15:52:16 +00:00
|
|
|
|
|
|
|
.. code-block:: python
|
|
|
|
|
2020-03-06 11:25:24 +00:00
|
|
|
class LitMNIST(pl.LightningModule):
|
2020-03-03 15:52:16 +00:00
|
|
|
def __init__(self, hparams):
|
2020-03-27 12:36:50 +00:00
|
|
|
super().__init__()
|
2020-04-26 13:20:06 +00:00
|
|
|
|
|
|
|
# do this to save all arguments in any logger (tensorboard)
|
2020-03-03 15:52:16 +00:00
|
|
|
self.hparams = hparams
|
|
|
|
|
|
|
|
self.layer_1 = torch.nn.Linear(28 * 28, hparams.layer_1_dim)
|
|
|
|
self.layer_2 = torch.nn.Linear(hparams.layer_1_dim, hparams.layer_2_dim)
|
|
|
|
self.layer_3 = torch.nn.Linear(hparams.layer_2_dim, 10)
|
|
|
|
|
|
|
|
def forward(self, x):
|
|
|
|
...
|
|
|
|
|
|
|
|
def train_dataloader(self):
|
|
|
|
...
|
|
|
|
return DataLoader(mnist_train, batch_size=self.hparams.batch_size)
|
|
|
|
|
|
|
|
def configure_optimizers(self):
|
|
|
|
return Adam(self.parameters(), lr=self.hparams.learning_rate)
|
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
@staticmethod
|
|
|
|
def add_model_specific_args(parent_parser):
|
|
|
|
parser = ArgumentParser(parents=[parent_parser], add_help=False)
|
2020-03-03 15:52:16 +00:00
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
parser.add_argument('--layer_1_dim', type=int, default=128)
|
|
|
|
parser.add_argument('--layer_2_dim', type=int, default=256)
|
|
|
|
parser.add_argument('--batch_size', type=int, default=64)
|
|
|
|
parser.add_argument('--learning_rate', type=float, default=0.002)
|
|
|
|
return parser
|
2020-03-03 15:52:16 +00:00
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
Now pass in the params when you init your model
|
2020-03-06 19:53:27 +00:00
|
|
|
|
|
|
|
.. code-block:: python
|
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
hparams = parse_args()
|
|
|
|
model = LitMNIST(hparams)
|
2020-03-06 19:53:27 +00:00
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
The line `self.hparams = hparams` is very special. This line assigns your hparams to the LightningModule.
|
|
|
|
This does two things:
|
2020-03-06 19:53:27 +00:00
|
|
|
|
2020-04-26 14:57:26 +00:00
|
|
|
1. It adds them automatically to tensorboard logs under the hparams tab.
|
|
|
|
2. Lightning will save those hparams to the checkpoint and use them to restore the module correctly.
|
2020-03-06 19:53:27 +00:00
|
|
|
|
2020-03-03 15:52:16 +00:00
|
|
|
Trainer args
|
|
|
|
^^^^^^^^^^^^
|
2020-04-26 13:20:06 +00:00
|
|
|
To recap, add ALL possible trainer flags to the argparser and init the Trainer this way
|
2020-03-03 15:52:16 +00:00
|
|
|
|
|
|
|
.. code-block:: python
|
|
|
|
|
|
|
|
parser = ArgumentParser()
|
|
|
|
parser = Trainer.add_argparse_args(parser)
|
2020-04-26 13:20:06 +00:00
|
|
|
hparams = parser.parse_args()
|
2020-03-03 15:52:16 +00:00
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
trainer = Trainer.from_argparse_args(hparams)
|
2020-03-03 15:52:16 +00:00
|
|
|
|
2020-04-26 13:20:06 +00:00
|
|
|
# or if you need to pass in callbacks
|
|
|
|
trainer = Trainer.from_argparse_args(hparams, checkpoint_callback=..., callbacks=[...])
|
2020-03-03 15:52:16 +00:00
|
|
|
|
|
|
|
|
|
|
|
Multiple Lightning Modules
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
We often have multiple Lightning Modules where each one has different arguments. Instead of
|
|
|
|
polluting the main.py file, the LightningModule lets you define arguments for each one.
|
|
|
|
|
|
|
|
.. code-block:: python
|
|
|
|
|
2020-03-06 11:25:24 +00:00
|
|
|
class LitMNIST(pl.LightningModule):
|
2020-04-17 18:45:23 +00:00
|
|
|
def __init__(self, hparams):
|
|
|
|
super().__init__()
|
|
|
|
self.layer_1 = torch.nn.Linear(28 * 28, hparams.layer_1_dim)
|
2020-03-03 15:52:16 +00:00
|
|
|
|
|
|
|
@staticmethod
|
|
|
|
def add_model_specific_args(parent_parser):
|
|
|
|
parser = ArgumentParser(parents=[parent_parser])
|
|
|
|
parser.add_argument('--layer_1_dim', type=int, default=128)
|
|
|
|
return parser
|
|
|
|
|
|
|
|
class GoodGAN(pl.LightningModule):
|
2020-04-17 18:45:23 +00:00
|
|
|
def __init__(self, hparams):
|
|
|
|
super().__init__()
|
|
|
|
self.encoder = Encoder(layers=hparams.encoder_layers)
|
2020-03-03 15:52:16 +00:00
|
|
|
|
|
|
|
@staticmethod
|
|
|
|
def add_model_specific_args(parent_parser):
|
|
|
|
parser = ArgumentParser(parents=[parent_parser])
|
|
|
|
parser.add_argument('--encoder_layers', type=int, default=12)
|
|
|
|
return parser
|
|
|
|
|
|
|
|
Now we can allow each model to inject the arguments it needs in the main.py
|
|
|
|
|
|
|
|
.. code-block:: python
|
|
|
|
|
|
|
|
def main(args):
|
|
|
|
|
|
|
|
# pick model
|
|
|
|
if args.model_name == 'gan':
|
|
|
|
model = GoodGAN(hparams=args)
|
|
|
|
elif args.model_name == 'mnist':
|
2020-03-06 11:25:24 +00:00
|
|
|
model = LitMNIST(hparams=args)
|
2020-03-03 15:52:16 +00:00
|
|
|
|
2020-03-06 11:25:24 +00:00
|
|
|
model = LitMNIST(hparams=args)
|
2020-04-26 13:20:06 +00:00
|
|
|
trainer = Trainer.from_argparse_args(args)
|
2020-03-03 15:52:16 +00:00
|
|
|
trainer.fit(model)
|
|
|
|
|
|
|
|
if __name__ == '__main__':
|
|
|
|
parser = ArgumentParser()
|
|
|
|
parser = Trainer.add_argparse_args(parser)
|
|
|
|
|
|
|
|
# figure out which model to use
|
|
|
|
parser.add_argument('--model_name', type=str, default='gan', help='gan or mnist')
|
2020-04-26 13:20:06 +00:00
|
|
|
|
|
|
|
# THIS LINE IS KEY TO PULL THE MODEL NAME
|
2020-03-03 15:52:16 +00:00
|
|
|
temp_args = parser.parse_known_args()
|
|
|
|
|
|
|
|
# let the model add what it wants
|
|
|
|
if temp_args.model_name == 'gan':
|
|
|
|
parser = GoodGAN.add_model_specific_args(parser)
|
|
|
|
elif temp_args.model_name == 'mnist':
|
2020-03-06 11:25:24 +00:00
|
|
|
parser = LitMNIST.add_model_specific_args(parser)
|
2020-03-03 15:52:16 +00:00
|
|
|
|
|
|
|
args = parser.parse_args()
|
|
|
|
|
|
|
|
# train
|
|
|
|
main(args)
|
|
|
|
|
|
|
|
and now we can train MNIST or the gan using the command line interface!
|
|
|
|
|
|
|
|
.. code-block:: bash
|
|
|
|
|
|
|
|
$ python main.py --model_name gan --encoder_layers 24
|
|
|
|
$ python main.py --model_name mnist --layer_1_dim 128
|
|
|
|
|
|
|
|
Hyperparameter Optimization
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
Lightning is fully compatible with the hyperparameter optimization libraries!
|
|
|
|
Here are some useful ones:
|
|
|
|
|
|
|
|
- `Hydra <https://medium.com/pytorch/hydra-a-fresh-look-at-configuration-for-machine-learning-projects-50583186b710>`_
|
|
|
|
- `Optuna <https://github.com/optuna/optuna/blob/master/examples/pytorch_lightning_simple.py>`_
|