hooks¶
Classes
Hooks to be used with Checkpointing. |
|
Hooks to be used with LightningDataModule. |
|
Hooks to be used in LightningModule. |
Various hooks to be used in the Lightning code.
-
class
pytorch_lightning.core.hooks.
CheckpointHooks
[source]¶ Bases:
object
Hooks to be used with Checkpointing.
-
on_load_checkpoint
(checkpoint)[source]¶ Called by Lightning to restore your model. If you saved something with
on_save_checkpoint()
this is your chance to restore this.Example
def on_load_checkpoint(self, checkpoint): # 99% of the time you don't need to implement this method self.something_cool_i_want_to_save = checkpoint['something_cool_i_want_to_save']
Note
Lightning auto-restores global step, epoch, and train state including amp scaling. There is no need for you to restore anything regarding training.
- Return type
None
-
on_save_checkpoint
(checkpoint)[source]¶ Called by Lightning when saving a checkpoint to give you a chance to store anything else you might want to save.
Example
def on_save_checkpoint(self, checkpoint): # 99% of use cases you don't need to implement this method checkpoint['something_cool_i_want_to_save'] = my_cool_pickable_object
Note
Lightning saves all aspects of training (epoch, global step, etc…) including amp scaling. There is no need for you to store anything about training.
- Return type
None
-
-
class
pytorch_lightning.core.hooks.
DataHooks
[source]¶ Bases:
object
Hooks to be used with LightningDataModule.
-
prepare_data
()[source]¶ Use this to download and prepare data.
Warning
DO NOT set state to the model (use setup instead) since this is NOT called on every GPU in DDP/TPU
Example:
def prepare_data(self): # good download_data() tokenize() etc() # bad self.split = data_split self.some_state = some_other_state()
In DDP prepare_data can be called in two ways (using Trainer(prepare_data_per_node)):
Once per node. This is the default and is only called on LOCAL_RANK=0.
Once in total. Only called on GLOBAL_RANK=0.
Example:
# DEFAULT # called once per node on LOCAL_RANK=0 of that node Trainer(prepare_data_per_node=True) # call on GLOBAL_RANK=0 (great for shared file systems) Trainer(prepare_data_per_node=False)
This is called before requesting the dataloaders:
model.prepare_data() if ddp/tpu: init() model.setup(stage) model.train_dataloader() model.val_dataloader() model.test_dataloader()
- Return type
None
-
test_dataloader
()[source]¶ Implement one or multiple PyTorch DataLoaders for testing.
The dataloader you return will not be called every epoch unless you set
reload_dataloaders_every_epoch
toTrue
.For data processing use the following pattern:
download in
prepare_data()
process and split in
setup()
However, the above are only necessary for distributed processing.
Warning
do not assign state in prepare_data
fit()
…
setup()
Note
Lightning adds the correct sampler for distributed and arbitrary hardware. There is no need to set it yourself.
- Return type
- Returns
Single or multiple PyTorch DataLoaders.
Example
def test_dataloader(self): transform = transforms.Compose([transforms.ToTensor(), transforms.Normalize((0.5,), (1.0,))]) dataset = MNIST(root='/path/to/mnist/', train=False, transform=transform, download=True) loader = torch.utils.data.DataLoader( dataset=dataset, batch_size=self.batch_size, shuffle=False ) return loader # can also return multiple dataloaders def test_dataloader(self): return [loader_a, loader_b, ..., loader_n]
Note
If you don’t need a test dataset and a
test_step()
, you don’t need to implement this method.Note
In the case where you return multiple test dataloaders, the
test_step()
will have an argumentdataloader_idx
which matches the order here.
-
train_dataloader
()[source]¶ Implement a PyTorch DataLoader for training.
- Return type
- Returns
Single PyTorch
DataLoader
.
The dataloader you return will not be called every epoch unless you set
reload_dataloaders_every_epoch
toTrue
.For data processing use the following pattern:
download in
prepare_data()
process and split in
setup()
However, the above are only necessary for distributed processing.
Warning
do not assign state in prepare_data
fit()
…
setup()
Note
Lightning adds the correct sampler for distributed and arbitrary hardware. There is no need to set it yourself.
Example
def train_dataloader(self): transform = transforms.Compose([transforms.ToTensor(), transforms.Normalize((0.5,), (1.0,))]) dataset = MNIST(root='/path/to/mnist/', train=True, transform=transform, download=True) loader = torch.utils.data.DataLoader( dataset=dataset, batch_size=self.batch_size, shuffle=True ) return loader
-
transfer_batch_to_device
(batch, device=None)[source]¶ Override this hook if your
DataLoader
returns tensors wrapped in a custom data structure.The data types listed below (and any arbitrary nesting of them) are supported out of the box:
torch.Tensor
or anything that implements .to(…)torchtext.data.batch.Batch
For anything else, you need to define how the data is moved to the target device (CPU, GPU, TPU, …).
Example:
def transfer_batch_to_device(self, batch, device) if isinstance(batch, CustomBatch): # move all tensors in your custom data structure to the device batch.samples = batch.samples.to(device) batch.targets = batch.targets.to(device) else: batch = super().transfer_batch_to_device(data, device) return batch
- Parameters
- Return type
- Returns
A reference to the data on the new device.
Note
This hook should only transfer the data and not modify it, nor should it move the data to any other device than the one passed in as argument (unless you know what you are doing).
Note
This hook only runs on single GPU training and DDP. If you need multi-GPU support for your custom batch objects in
dp
orddp2
, you need to define your customDistributedDataParallel
orLightningDistributedDataParallel
and overrideconfigure_ddp()
.See also
move_data_to_device()
apply_to_collection()
-
val_dataloader
()[source]¶ Implement one or multiple PyTorch DataLoaders for validation.
The dataloader you return will not be called every epoch unless you set
reload_dataloaders_every_epoch
toTrue
.It’s recommended that all data downloads and preparation happen in
prepare_data()
.Note
Lightning adds the correct sampler for distributed and arbitrary hardware There is no need to set it yourself.
- Return type
- Returns
Single or multiple PyTorch DataLoaders.
Examples
def val_dataloader(self): transform = transforms.Compose([transforms.ToTensor(), transforms.Normalize((0.5,), (1.0,))]) dataset = MNIST(root='/path/to/mnist/', train=False, transform=transform, download=True) loader = torch.utils.data.DataLoader( dataset=dataset, batch_size=self.batch_size, shuffle=False ) return loader # can also return multiple dataloaders def val_dataloader(self): return [loader_a, loader_b, ..., loader_n]
Note
If you don’t need a validation dataset and a
validation_step()
, you don’t need to implement this method.Note
In the case where you return multiple validation dataloaders, the
validation_step()
will have an argumentdataloader_idx
which matches the order here.
-
-
class
pytorch_lightning.core.hooks.
ModelHooks
[source]¶ Bases:
object
Hooks to be used in LightningModule.
-
on_after_backward
()[source]¶ Called in the training loop after loss.backward() and before optimizers do anything. This is the ideal place to inspect or log gradient information.
Example:
def on_after_backward(self): # example to inspect gradient information in tensorboard if self.trainer.global_step % 25 == 0: # don't make the tf file huge params = self.state_dict() for k, v in params.items(): self.logger.experiment.add_histogram( tag=k, values=v.grad, global_step=self.trainer.global_step )
- Return type
None
-
on_before_zero_grad
(optimizer)[source]¶ Called after optimizer.step() and before optimizer.zero_grad().
Called in the training loop after taking an optimizer step and before zeroing grads. Good place to inspect weight information with weights updated.
This is where it is called:
for optimizer in optimizers: optimizer.step() model.on_before_zero_grad(optimizer) # < ---- called here optimizer.zero_grad()
- Parameters
optimizer¶ (
Optimizer
) – The optimizer for which grads should be zeroed.- Return type
None
-
on_epoch_start
()[source]¶ Called in the training loop at the very beginning of the epoch.
- Return type
None
-
on_fit_start
()[source]¶ Called at the very beginning of fit. If on DDP it is called on every process
-
on_pretrain_routine_end
()[source]¶ Called at the end of the pretrain routine (between fit and train start).
fit
pretrain_routine start
pretrain_routine end
training_start
- Return type
None
-
on_pretrain_routine_start
()[source]¶ Called at the beginning of the pretrain routine (between fit and train start).
fit
pretrain_routine start
pretrain_routine end
training_start
- Return type
None
-
on_test_batch_end
(outputs, batch, batch_idx, dataloader_idx)[source]¶ Called in the test loop after the batch.
-
on_test_batch_start
(batch, batch_idx, dataloader_idx)[source]¶ Called in the test loop before anything happens for that batch.
-
on_test_epoch_start
()[source]¶ Called in the test loop at the very beginning of the epoch.
- Return type
None
-
on_train_batch_end
(outputs, batch, batch_idx, dataloader_idx)[source]¶ Called in the training loop after the batch.
-
on_train_batch_start
(batch, batch_idx, dataloader_idx)[source]¶ Called in the training loop before anything happens for that batch.
If you return -1 here, you will skip training for the rest of the current epoch.
-
on_train_end
()[source]¶ Called at the end of training before logger experiment is closed.
- Return type
None
-
on_train_epoch_end
(outputs)[source]¶ Called in the training loop at the very end of the epoch.
- Return type
None
-
on_train_epoch_start
()[source]¶ Called in the training loop at the very beginning of the epoch.
- Return type
None
-
on_validation_batch_end
(outputs, batch, batch_idx, dataloader_idx)[source]¶ Called in the validation loop after the batch.
-
on_validation_batch_start
(batch, batch_idx, dataloader_idx)[source]¶ Called in the validation loop before anything happens for that batch.
-
on_validation_epoch_end
()[source]¶ Called in the validation loop at the very end of the epoch.
- Return type
None
-
on_validation_epoch_start
()[source]¶ Called in the validation loop at the very beginning of the epoch.
- Return type
None
-
setup
(stage)[source]¶ Called at the beginning of fit and test. This is a good hook when you need to build models dynamically or adjust something about them. This hook is called on every process when using DDP.
Example:
class LitModel(...): def __init__(self): self.l1 = None def prepare_data(self): download_data() tokenize() # don't do this self.something = else def setup(stage): data = Load_data(...) self.l1 = nn.Linear(28, data.num_classes)
-