-
Notifications
You must be signed in to change notification settings - Fork 10
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
Post-selection #82
Post-selection #82
Conversation
Thank you for your contribution! I think implementation itself looks good. On the other hand, we are bit worried that In addition, those |
Thanks!
I see. That makes sense.
Agree. Then I'll put the filter functions in |
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.
Sorry for a belated review.
I added a few minor comments but overall it looks good to me.
After merging this, we would like to consider unifying similar implementation in #154.
…__.py Co-authored-by: KAWAKUBO Toru <dev@kwkbtr.info>
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.
Thank you!
Added a very basic
post_selection()
and functions that generateSampler
performs post-selection behind the scenes.post_selection()
create_general_post_selection_sampler()
functions that create sampler with post-selection, specialized for JW and BK mappingscreate_jw_electron_number_post_selection_sampler()
create_bk_electron_number_post_selection_sampler()
create_jw_electron_number_post_selection_filter_fn()
create_bk_electron_number_post_selection_filter_fn
The implementation provides necessary functionalities but I'm not sure if it follows the quri-parts's development policy. I would love to discuss with organizers what the implementation should be 😉