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

"Jumps" in estimates based on is_sparse #52

Open
bencrts opened this issue Oct 20, 2022 · 0 comments
Open

"Jumps" in estimates based on is_sparse #52

bencrts opened this issue Oct 20, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@bencrts
Copy link
Collaborator

bencrts commented Oct 20, 2022

We call different costing functions for very similar parameter sets which could lead to "jumps". For example, for the two parameter sets:

sage: params = LWE.Parameters(n=1024, q=2^20, Xs=ND.SparseTernary(512,128,128), Xe=ND.DiscreteGaussian(3.2))
sage: params_is_sparse = LWE.Parameters(n=1024, q=2^20, Xs=ND.SparseTernary(512,128,127), Xe=ND.DiscreteGaussian(3.2))

we would see a 5-bit difference:

sage: LWE.dual_hybrid(params)
rop: ≈2^172.9, mem: ≈2^167.8, m: 911, β: 502, d: 1890, ↻: 1, ζ: 45, tag: dual_hybrid
sage: LWE.dual_hybrid(params_is_sparse)
rop: ≈2^178.0, mem: ≈2^168.8, m: 909, β: 501, d: 1886, ↻: 41, ζ: 47, h1: 22, tag: dual_hybrid

since different costing functions are called based on the result of is_sparse.

@bencrts bencrts changed the title "Jumps" in estimates based "Jumps" in estimates based on is_sparse Oct 20, 2022
@bencrts bencrts added the bug Something isn't working label Oct 21, 2022
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

No branches or pull requests

1 participant