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

Test failure of enum-parallel gradients after PyTorch #5776 #912

Closed
neerajprad opened this issue Mar 21, 2018 · 5 comments
Closed

Test failure of enum-parallel gradients after PyTorch #5776 #912

neerajprad opened this issue Mar 21, 2018 · 5 comments

Comments

@neerajprad
Copy link
Member

neerajprad commented Mar 21, 2018

With the latest pytorch master, many parallel enum tests in test_enum are failing due to mismatch in the gradient computation.

To replicate, checkout the commit 5fa3aac610ee234338dbc11eb5b6d4a133cb483d in PyTorch master (pytorch/pytorch#5776), build PyTorch and run these tests

pytest -v --tb=short tests/infer/test_enum.py

Example of a failing test - test_elbo_iarange_iarange 2-2-None-None-parallel-None.

@fritzo, @eb8680 - I thought that there could be some unexpected interactions between the dice elbo change and upstream PyTorch. Turns out that is not exactly the case as 11 of our tests fail even before the dice elbo change, but there are more failures (79) with dice elbo. Could you guys take a look?

This could either be a Pyro bug or something in PyTorch upstream.

@neerajprad neerajprad added the bug label Mar 21, 2018
@fritzo fritzo self-assigned this Mar 21, 2018
@fritzo fritzo changed the title Elbo gradient mismatch with enum-parallel on latest pytorch master Test failure of enum-parallel gradients after PyTorch #5776 Mar 21, 2018
@fritzo fritzo removed their assignment Mar 21, 2018
@cpuhrsch
Copy link

Hey @neerajprad, thank you for your post, I'm looking into this now.

@cpuhrsch
Copy link

I found the bug, I'll send a patch soon.

@neerajprad
Copy link
Member Author

Thanks, @cpuhrsch! Curious to see where the bug was.

@cpuhrsch
Copy link

@neerajprad please see PR pytorch/pytorch#5926

@fritzo
Copy link
Member

fritzo commented Mar 24, 2018

Fixed upstream by pytorch/pytorch#5926 and in Pyro by #917.

@fritzo fritzo closed this as completed Mar 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants