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

280 andrey depth limitations hps #392

Closed
wants to merge 4 commits into from

Conversation

kimandrik
Copy link
Collaborator

Changed floating point arithmetics to fixed point arithmetics in both: ScaleAndRound function used in multiplication and ScaleAndRound function used in decryption.

Questions:

  1. Do we need to add tests for HPS and other variants? If so the test could be slow, as they require lot's of levels for BFV.
  2. I keep temporary bfv-mult-bug.cpp example from https://github.com/openfheorg/openfhe-development/tree/Erabelli_280-bfv-mult-bug. Do we need some variant of it?
  3. In case of decryption should we use previous method with floating point arithmetics, or move to new with fixed point arithmetics?
  4. Should we rename functions in dcrtPoly, as they could be confusing? Make renamings as a part of another issue?

@dsuponitskiy dsuponitskiy added this to the Release 1.0.4 milestone May 8, 2023
@dsuponitskiy dsuponitskiy added the bug Something isn't working label May 8, 2023
@yspolyakov
Copy link
Contributor

  1. Do we need to add tests for HPS and other variants? If so the test could be slow, as they require lot's of levels for BFV.

I would add some tests using a small ring dimension, e.g., 16.

I keep temporary bfv-mult-bug.cpp example from https://github.com/openfheorg/openfhe-development/tree/Erabelli_280-bfv-mult-bug. Do we need some variant of it?

I think we want to create a unit test based on it

In case of decryption should we use previous method with floating point arithmetics, or move to new with fixed point arithmetics?

Let us set up a conference call and discuss this in more detail.

Should we rename functions in dcrtPoly, as they could be confusing? Make renamings as a part of another issue?

Better do it as part of another issue

@yspolyakov
Copy link
Contributor

We had a meeting on this. Some code/approaches from this PR will be used to address #280 and #421

@yspolyakov yspolyakov closed this May 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Multiplicative depth limitation for HPS, HPSPOVERQ and HPSOVERQLEVELED modes of BFV
3 participants