-
Notifications
You must be signed in to change notification settings - Fork 3
Bugfix/investigate stein thinning #1000
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
Conversation
…teinThinning in blobs benchmark
# Conflicts: # benchmark/blobs_benchmark.py
|
List of all changes:
|
rg936672
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just a few minor suggestions. Remember to link the issues that this PR closes, either under "Development" at the top right, or by using "Closes #xyz" in the issue description.
Co-authored-by: rg936672 <162452529+rg936672@users.noreply.github.com>
rg936672
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy my suggestions have all been addressed, though hold off on merging until both (a) @pc532627 approves as well and (b) you've created a ticket for any suggestions that you've deemed out of scope for this PR. (Could be as simple as a "Clean up benchmarking code" with a link to the review comments in question.)
pc532627
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor typo
|
TODO failure is a bug in the latest Ruff - see astral-sh/ruff#16874 |
These have been fixed by the changes in #1000.
PR Type
Description
Improving the performance of Stein Thinning in benchmarks, primarily by using regularisation and better probability density estimation.
How Has This Been Tested?
Existing tests pass as expected.
Does this PR introduce a breaking change?
Checklist before requesting a review