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

Change choice of q in qary-lattice generation #275

Merged
merged 4 commits into from
Jun 15, 2024
Merged

Conversation

ludopulles
Copy link
Contributor

Let random lattice generation use the methods changed in fplll/fplll#526.
Note: adds support for values of 'q' above 2^31 when calling IntegerMatrix.random with methods 'ntrulike', 'ntrulike2' and 'qary'.

Note: G6K does not need any modification.

Resolves: post by @malb in fplll/fplll#526 (comment)

Let random lattice generation use the methods changed in
fplll/fplll#526.
Note: adds support for values of 'q' above 2^31 when calling
IntegerMatrix.random with methods 'ntrulike', 'ntrulike2' and 'qary'.
@@ -11,9 +11,9 @@


if sys.maxsize >= 2**62:
dimensions = ((0, 0), (2, 2), (3, 3), (10, 10), (30, 30), (50, 50), (60, 60))
dimensions = ((1, 1), (2, 2), (3, 3), (10, 10), (30, 30), (50, 50), (60, 60))
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should check these, those can happen as corner cases of higher-level algorithms

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough, I have changed matrix generation in this test file to use bits=max(1, m) in that case, as bits=0 gave a Segmentation Fault.

- Setting bits >= 1 prevents a SignalError in IntegerMatrix.randomize.
- Add assertion for the check introduced in commit
  b0d4ca4 .
@malb malb merged commit d03bc38 into fplll:master Jun 15, 2024
37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants