Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When using mini-batch, there is a potential risk of future information leakage #1642

Open
initial-d opened this issue Sep 10, 2021 · 0 comments

Comments

@initial-d
Copy link

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.

@initial-d 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant