You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I'm training a MLP model with mini-batched input, the result is more better than the pytorch's version. I checked my input, I found my input samples are time continuous data and I forgot make a global shuffle. So the model can see future information in a mini-batch. I think the main reason is the low-level implementation of AffineTransform function with mini-batch. One solution is to make a global shuffle before making mini-batch, another solution maybe is to optimize the implementation of mini-batched AffineTransform. Thanks for paying attention to this issue.
The text was updated successfully, but these errors were encountered:
initial-d
changed the title
When using mini-batch, there is a potential risks of future information leakage
When using mini-batch, there is a potential risk of future information leakage
Sep 10, 2021
When I'm training a MLP model with mini-batched input, the result is more better than the pytorch's version. I checked my input, I found my input samples are time continuous data and I forgot make a global shuffle. So the model can see future information in a mini-batch. I think the main reason is the low-level implementation of AffineTransform function with mini-batch. One solution is to make a global shuffle before making mini-batch, another solution maybe is to optimize the implementation of mini-batched AffineTransform. Thanks for paying attention to this issue.
The text was updated successfully, but these errors were encountered: