News for hackers. Stuff that matters.

rvarma

Re:Batch Normalization for deep networks on Thursday February 22, 2018 @05:32PM (#16442153)
Ah yeah, my bad, I should've instead shown the activations after the first layer, since "activation 0" is just the distribution of the random data I started with
Re:Batch Normalization for deep networks on Thursday February 22, 2018 @05:31PM (#16442142)
I actually think the idea of using leaky ReLUs is interesting, because it'll still provide a small gradient when x < 0, which perhaps may slightly alleviate the vanishing gradients issue
Re:Batch Normalization for deep networks on Thursday February 22, 2018 @05:28PM (#16442108)
Thanks for your comment!

Regarding point 1, I stored both the activations before batchnorm and after since I needed them during the backwards pass. i.e. I stored h_out before and after these operations:

h_out = (h_out - np.mean(h_out, axis = 0)) / np.std(h_out, axis = 0) h_out = gamma * h_out + beta

Regarding point 2, I do realize now that fixing a bad init via Xavier/he initialization and using batch norm fix slightly different problems - if I were to rewrite this post I probably wouldn't talk about initialization at all, or at least mention the Xavier/He initialization.

Thanks for the link! It actually provides a really clear and intuitive explanation of the notion of similarity.