jactorch.optim.weight_decay#
Classes
Implements AdamW algorithm. |
Class AdamW
- class AdamW[source]#
Bases:
OptimizerImplements AdamW algorithm.
- __init__(params, lr=1e-3, betas=(0.9, 0.999), eps=1e-8, weight_decay=0)[source]#
Initialize AdamW optimizer.
- Parameters:
params – iterable of parameters to optimize or dicts defining parameter groups
lr – learning rate
betas – coefficients used for computing running averages of gradient and its square
eps – term added to the denominator to improve numerical stability
weight_decay – weight decay (L2 penalty)
- __new__(**kwargs)#
- add_param_group(param_group)#
Add a param group to the
Optimizers param_groups.This can be useful when fine tuning a pre-trained network as frozen layers can be made trainable and added to the
Optimizeras training progresses.- Parameters:
param_group (dict) – Specifies what Tensors should be optimized along with group specific optimization options.
- Return type:
None
- load_state_dict(state_dict)#
Loads the optimizer state.
- Parameters:
state_dict (dict) – optimizer state. Should be an object returned from a call to
state_dict().- Return type:
None
- static profile_hook_step(func)#
- register_load_state_dict_post_hook(hook, prepend=False)#
Register a load_state_dict post-hook which will be called after
load_state_dict()is called. It should have the following signature:hook(optimizer) -> None
The
optimizerargument is the optimizer instance being used.The hook will be called with argument
selfafter callingload_state_dictonself. The registered hook can be used to perform post-processing afterload_state_dicthas loaded thestate_dict.- Parameters:
hook (Callable) – The user defined hook to be registered.
prepend (bool) – If True, the provided post
hookwill be fired before all the already registered post-hooks onload_state_dict. Otherwise, the providedhookwill be fired after all the already registered post-hooks. (default: False)
- Returns:
a handle that can be used to remove the added hook by calling
handle.remove()- Return type:
torch.utils.hooks.RemoveableHandle
- register_load_state_dict_pre_hook(hook, prepend=False)#
Register a load_state_dict pre-hook which will be called before
load_state_dict()is called. It should have the following signature:hook(optimizer, state_dict) -> state_dict or None
The
optimizerargument is the optimizer instance being used and thestate_dictargument is a shallow copy of thestate_dictthe user passed in toload_state_dict. The hook may modify the state_dict inplace or optionally return a new one. If a state_dict is returned, it will be used to be loaded into the optimizer.The hook will be called with argument
selfandstate_dictbefore callingload_state_dictonself. The registered hook can be used to perform pre-processing before theload_state_dictcall is made.- Parameters:
hook (Callable) – The user defined hook to be registered.
prepend (bool) – If True, the provided pre
hookwill be fired before all the already registered pre-hooks onload_state_dict. Otherwise, the providedhookwill be fired after all the already registered pre-hooks. (default: False)
- Returns:
a handle that can be used to remove the added hook by calling
handle.remove()- Return type:
torch.utils.hooks.RemoveableHandle
- register_state_dict_post_hook(hook, prepend=False)#
Register a state dict post-hook which will be called after
state_dict()is called. It should have the following signature:hook(optimizer, state_dict) -> state_dict or None
The hook will be called with arguments
selfandstate_dictafter generating astate_dictonself. The hook may modify the state_dict inplace or optionally return a new one. The registered hook can be used to perform post-processing on thestate_dictbefore it is returned.- Parameters:
hook (Callable) – The user defined hook to be registered.
prepend (bool) – If True, the provided post
hookwill be fired before all the already registered post-hooks onstate_dict. Otherwise, the providedhookwill be fired after all the already registered post-hooks. (default: False)
- Returns:
a handle that can be used to remove the added hook by calling
handle.remove()- Return type:
torch.utils.hooks.RemoveableHandle
- register_state_dict_pre_hook(hook, prepend=False)#
Register a state dict pre-hook which will be called before
state_dict()is called. It should have the following signature:hook(optimizer) -> None
The
optimizerargument is the optimizer instance being used. The hook will be called with argumentselfbefore callingstate_dictonself. The registered hook can be used to perform pre-processing before thestate_dictcall is made.- Parameters:
hook (Callable) – The user defined hook to be registered.
prepend (bool) – If True, the provided pre
hookwill be fired before all the already registered pre-hooks onstate_dict. Otherwise, the providedhookwill be fired after all the already registered pre-hooks. (default: False)
- Returns:
a handle that can be used to remove the added hook by calling
handle.remove()- Return type:
torch.utils.hooks.RemoveableHandle
- register_step_post_hook(hook)#
Register an optimizer step post hook which will be called after optimizer step. It should have the following signature:
hook(optimizer, args, kwargs) -> None
The
optimizerargument is the optimizer instance being used.- Parameters:
hook (Callable) – The user defined hook to be registered.
- Returns:
a handle that can be used to remove the added hook by calling
handle.remove()- Return type:
torch.utils.hooks.RemovableHandle
- register_step_pre_hook(hook)#
Register an optimizer step pre hook which will be called before optimizer step. It should have the following signature:
hook(optimizer, args, kwargs) -> None or modified args and kwargs
The
optimizerargument is the optimizer instance being used. If args and kwargs are modified by the pre-hook, then the transformed values are returned as a tuple containing the new_args and new_kwargs.- Parameters:
hook (Callable) – The user defined hook to be registered.
- Returns:
a handle that can be used to remove the added hook by calling
handle.remove()- Return type:
torch.utils.hooks.RemovableHandle
- state_dict()#
Returns the state of the optimizer as a
dict.It contains two entries:
state: a Dict holding current optimization state. Its contentdiffers between optimizer classes, but some common characteristics hold. For example, state is saved per parameter, and the parameter itself is NOT saved.
stateis a Dictionary mapping parameter ids to a Dict with state corresponding to each parameter.
param_groups: a List containing all parameter groups where eachparameter group is a Dict. Each parameter group contains metadata specific to the optimizer, such as learning rate and weight decay, as well as a List of parameter IDs of the parameters in the group.
NOTE: The parameter IDs may look like indices but they are just IDs associating state with param_group. When loading from a state_dict, the optimizer will zip the param_group
params(int IDs) and the optimizerparam_groups(actualnn.Parameters) in order to match state WITHOUT additional verification.A returned state dict might look something like:
{ 'state': { 0: {'momentum_buffer': tensor(...), ...}, 1: {'momentum_buffer': tensor(...), ...}, 2: {'momentum_buffer': tensor(...), ...}, 3: {'momentum_buffer': tensor(...), ...} }, 'param_groups': [ { 'lr': 0.01, 'weight_decay': 0, ... 'params': [0] }, { 'lr': 0.001, 'weight_decay': 0.5, ... 'params': [1, 2, 3] } ] }
- step(closure=None)[source]#
Performs a single optimization step.
- Parameters:
closure (callable, optional) – A closure that reevaluates the model and returns the loss.
- zero_grad(set_to_none=True)#
Resets the gradients of all optimized
torch.Tensors.- Parameters:
set_to_none (bool) – instead of setting to zero, set the grads to None. This will in general have lower memory footprint, and can modestly improve performance. However, it changes certain behaviors. For example: 1. When the user tries to access a gradient and perform manual ops on it, a None attribute or a Tensor full of 0s will behave differently. 2. If the user requests
zero_grad(set_to_none=True)followed by a backward pass,.grads are guaranteed to be None for params that did not receive a gradient. 3.torch.optimoptimizers have a different behavior if the gradient is 0 or None (in one case it does the step with a gradient of 0 and in the other it skips the step altogether).- Return type:
None