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

adding quantiles method to AutoGuideList #2837

Closed
wants to merge 5 commits into from
Closed

adding quantiles method to AutoGuideList #2837

wants to merge 5 commits into from

Conversation

vitkl
Copy link
Contributor

@vitkl vitkl commented May 7, 2021

This pull request adds quantiles method to AutoGuideList. I did not find where a test for this can be added. Please let me know what you think.

@fehiepsi fehiepsi added the WIP label May 8, 2021
@fehiepsi
Copy link
Member

fehiepsi commented May 8, 2021

@vitkl You can add a test here. :)

@fritzo
Copy link
Member

fritzo commented May 17, 2021

This is great. Can you resolve lint errors and add a test case?

/pyro/infer/autoguide/guides.py:270:1: W293 blank line contains whitespace

@vitkl
Copy link
Contributor Author

vitkl commented May 17, 2021

For AutoLaplaceApproximation guides, AutoGuideList also needs a method guide.laplace_approximation() - but otherwise, I added tests.

@fritzo
Copy link
Member

fritzo commented May 17, 2021

@vitkl you can make lint to test linting locally.

@fritzo
Copy link
Member

fritzo commented May 17, 2021

@vitkl I believe you need to switch the docstring from numpy-style to sphinx rst style:

"""
Returns the posterior quantile values of each latent variable.

:param list quantiles: A list of requested quantiles between 0 and 1.
:returns: A dict mapping sample site name to quantiles tensor.
:rtype: dict
"""

Copy link
Member

@fritzo fritzo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @vitkl I think you'll just need to merge with the dev branch, since we switched CI systems. Looking forward to merging this!

@fritzo
Copy link
Member

fritzo commented Jun 28, 2021

Hi @vitkl, this is a great new feature to have, and I'd like to include it in the next release. Do you want any help getting this merged?

@fritzo fritzo added this to the 1.7 release milestone Jun 28, 2021
@vitkl
Copy link
Contributor Author

vitkl commented Jun 28, 2021 via email

@fritzo
Copy link
Member

fritzo commented Jun 28, 2021

When do you plan next release?

Oh, how about next Wednesday 7/7? There's no fixed deadline, but I'd like to get out fixes for PyTorch 1.9 by the end of next week.

@fritzo fritzo removed this from the 1.7 release milestone Jul 6, 2021
@fritzo
Copy link
Member

fritzo commented Jul 6, 2021

Hi @vitkl no pressure, but do you plan to update this branch today? If not I'll release without, since there is a pressing PyTorch bug workaround. Also I'm happy to take over this PR and get your feature in if you're busy.

@vitkl
Copy link
Contributor Author

vitkl commented Jul 6, 2021 via email

@vitkl
Copy link
Contributor Author

vitkl commented Jul 6, 2021

Hm, actually, as I look at it now - I think I have addressed the comments from you @fritzo and @fehiepsi . What remains is fixing the conflict on this branch (which I don't immediately understand) and merging it to the correct branch. Would be great if you can do that.

@fritzo fritzo mentioned this pull request Jul 6, 2021
1 task
@fritzo
Copy link
Member

fritzo commented Jul 6, 2021

Closing after moving to #2896

@fritzo fritzo closed this Jul 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants