Daniel Voigt Godoy - Deep Learning with PyTorch Step-by-Step A Beginner’s Guide-leanpub
Moreover, let’s use a ten times higher learning rate; after all, we’re in full control ofthe gradients now:Model Configuration1 torch.manual_seed(42)2 with torch.no_grad():3 model.apply(weights_init)45 optimizer = optim.SGD(model.parameters(), lr=0.1)Before training it, let’s use set_clip_grad_value() to make sure no gradients areever above 1.0:Model Training1 sbs_reg_clip = StepByStep(model, loss_fn, optimizer)2 sbs_reg_clip.set_loaders(train_loader)3 sbs_reg_clip.set_clip_grad_value(1.0)4 sbs_reg_clip.capture_gradients(['fc1'])5 sbs_reg_clip.train(10)6 sbs_reg_clip.remove_clip()7 sbs_reg_clip.remove_hooks()fig = sbs_reg_clip.plot_losses()No more exploding gradients, it seems. The loss is being minimized even afterchoosing a much higher learning rate to train the model.Vanishing and Exploding Gradients | 581
Figure E.7 - Losses—clipping by valueWhat about taking a look at the average gradients once again (there are 320updates now, so we’re looking at the extremes only):avg_grad = np.array(sbs_reg_clip._gradients['fc1']['weight']).mean(axis=(1, 2))avg_grad.min(), avg_grad.max()Output(-24.69288555463155, 14.385948762893676)"How come these (absolute) values are much larger than our clippingvalue?"These are the computed gradients; that is, before clipping. Left unchecked, thesegradients would have caused large updates, which, in turn, would have resulted ineven larger gradients, and so on and so forth. Explosion, basically. But these valueswere all clipped before being used in the parameter update, so all went well withthe model training.It is possible to take a more aggressive approach and clip the gradients at the originusing the backward hooks we discussed before.582 | Extra Chapter: Vanishing and Exploding Gradients
- Page 556 and 557: The constructor method defines the
- Page 558 and 559: Does it sound familiar? That’s wh
- Page 560 and 561: and w to represent these parameters
- Page 562 and 563: A mini-batch of size 64 is small en
- Page 564 and 565: normed1 = batch_normalizer(batch1[0
- Page 566 and 567: OutputOrderedDict([('running_mean',
- Page 568 and 569: OutputOrderedDict([('running_mean',
- Page 570 and 571: batch_normalizer = nn.BatchNorm2d(n
- Page 572 and 573: torch.manual_seed(23)dummy_points =
- Page 574 and 575: np.concatenate([dummy_points[:5].nu
- Page 576 and 577: Another advantage of these shortcut
- Page 578 and 579: It should be pretty clear, except f
- Page 580 and 581: Data Preparation1 # ImageNet statis
- Page 582 and 583: Data Preparation — Preprocessing1
- Page 584 and 585: • freezing the layers of the mode
- Page 586 and 587: Extra ChapterVanishing and Explodin
- Page 588 and 589: discussing it, let me illustrate it
- Page 590 and 591: Model Configuration (2)1 loss_fn =
- Page 592 and 593: weights. If done properly, the init
- Page 594 and 595: just did), or, if you are training
- Page 596 and 597: Figure E.3 - The effect of batch no
- Page 598 and 599: Model Configuration1 torch.manual_s
- Page 600 and 601: torch.manual_seed(42)parm = nn.Para
- Page 602 and 603: (and only if) the norm exceeds the
- Page 604 and 605: if callable(self.clipping): 1self.c
- Page 608 and 609: Clipping with HooksFirst, we reset
- Page 610 and 611: • visualizing the difference betw
- Page 612 and 613: Chapter 8SequencesSpoilersIn this c
- Page 614 and 615: Before shuffling, the pixels were o
- Page 616 and 617: And then let’s visualize the firs
- Page 618 and 619: sequence so far, and a data point f
- Page 620 and 621: Considering this, the not "unrolled
- Page 622 and 623: linear_input = nn.Linear(n_features
- Page 624 and 625: Outputtensor([[0.3924, 0.8146]], gr
- Page 626 and 627: Now we’re talking! The last hidde
- Page 628 and 629: Let’s take a look at the RNN’s
- Page 630 and 631: ◦ The initial hidden state, which
- Page 632 and 633: batch_first argument to True so we
- Page 634 and 635: OutputOrderedDict([('weight_ih_l0',
- Page 636 and 637: out, hidden = rnn_stacked(x)out, hi
- Page 638 and 639: _l0_reverse).Once again, let’s cr
- Page 640 and 641: For bidirectional RNNs, the last el
- Page 642 and 643: Model Configuration1 class SquareMo
- Page 644 and 645: StepByStep.loader_apply(test_loader
- Page 646 and 647: Figure 8.14 - Final hidden states f
- Page 648 and 649: Figure 8.16 - Transforming the hidd
- Page 650 and 651: Since the RNN cell has both of them
- Page 652 and 653: Every gate worthy of its name will
- Page 654 and 655: • For r=0 and z=0, the cell becom
Moreover, let’s use a ten times higher learning rate; after all, we’re in full control of
the gradients now:
Model Configuration
1 torch.manual_seed(42)
2 with torch.no_grad():
3 model.apply(weights_init)
4
5 optimizer = optim.SGD(model.parameters(), lr=0.1)
Before training it, let’s use set_clip_grad_value() to make sure no gradients are
ever above 1.0:
Model Training
1 sbs_reg_clip = StepByStep(model, loss_fn, optimizer)
2 sbs_reg_clip.set_loaders(train_loader)
3 sbs_reg_clip.set_clip_grad_value(1.0)
4 sbs_reg_clip.capture_gradients(['fc1'])
5 sbs_reg_clip.train(10)
6 sbs_reg_clip.remove_clip()
7 sbs_reg_clip.remove_hooks()
fig = sbs_reg_clip.plot_losses()
No more exploding gradients, it seems. The loss is being minimized even after
choosing a much higher learning rate to train the model.
Vanishing and Exploding Gradients | 581