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

Use thresholding instead of public keys #58

Open
mccalluc opened this issue Oct 9, 2024 · 0 comments
Open

Use thresholding instead of public keys #58

mccalluc opened this issue Oct 9, 2024 · 0 comments
Labels
nice-to-have No discussion required, but not top priority

Comments

@mccalluc
Copy link
Contributor

mccalluc commented Oct 9, 2024

We should avoid setting keys as public info. Ultimately they could be set on the dataset page, but IMO we should release these privately by making use of the thresholding in the library, as well as the cutoff plot functionality you have.

Originally posted by @Shoeboxam in #48 (comment)

@mccalluc mccalluc added the nice-to-have No discussion required, but not top priority label Oct 21, 2024
@cmbz cmbz added this to DP Wizard Oct 23, 2024
@cmbz cmbz moved this to Pending in DP Wizard Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nice-to-have No discussion required, but not top priority
Projects
Status: Pending
Development

No branches or pull requests

1 participant