FaultyBagnose:

Maybe I’m misunderstanding what is meant by “loading in to a range”, but if it means an affine transform that maps the min to 0 and max to 1, performing this operation prior to the normalization should have no effect?


That’s correct and you could skip the [0, 1] normalization and use the mean and std stats for the raw input values in [0, 255]. However, since ToTensor() is often used in the transformations to transform a PIL.Image in [0, 255] to a tensor in [0, 1], I believe this workflow grew organically.