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

Rationale behind the parameter values in TenSEAL #471

Open
ParthN9i4 opened this issue Feb 12, 2024 · 2 comments
Open

Rationale behind the parameter values in TenSEAL #471

ParthN9i4 opened this issue Feb 12, 2024 · 2 comments
Labels
Type: Question ❔ Question about implementation or some technical aspect

Comments

@ParthN9i4
Copy link

Question

Can you please explain the thought behind keeping the parameter values for poly_mod_degree as 4096 or 8192 and coeff_mod_bit_sizes as [40,20,40] or [40,21,21,...,42].

Further Information

I am doing my final year project that uses ML and FHE. It would be great to have some insights behind the usage of specific parameter values. I went through the ICLR paper for TenSEAL as well.

@ParthN9i4 ParthN9i4 added the Type: Question ❔ Question about implementation or some technical aspect label Feb 12, 2024
@manulen
Copy link

manulen commented Apr 3, 2024

I can recommend this blog post which helped me a lot in understanding the ckks algo and its parameters:

https://medium.com/intuit-engineering/data-science-without-seeing-data-how-to-set-microsoft-open-source-seal-parameters-72929b184058

@ParthN9i4
Copy link
Author

Thank you for sharing this blog manulen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Question ❔ Question about implementation or some technical aspect
Projects
None yet
Development

No branches or pull requests

2 participants