Continue BKZ even if we suspect SVP solution#9
Open
verdiverdiverdi wants to merge 4 commits intoWvanWoerden:debug_Breceivefrom
Open
Continue BKZ even if we suspect SVP solution#9verdiverdiverdi wants to merge 4 commits intoWvanWoerden:debug_Breceivefrom
verdiverdiverdi wants to merge 4 commits intoWvanWoerden:debug_Breceivefrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Simulates the next couple of tours of BKZ, even when we expect to be able to attain an SVP dimension that solves the instance. This captures the cases where the decrease in required SVP dimension saves more time than the subsequent BKZ tours.
The next three BKZ tours are simulated using fpylll's built in simulator for ease, and the time required for these tours are calculated as a function of the time taken for most recent completed tour. It is then checked where a solution is likely to appear, and whether this saves enough time to justify these further tours.
A new factor passed via --lwe/favour-memory-factor determines how much weight we place on reducing the maximum SVP dim at the cost of further BKZ tours. Greater than 1 should reduce memory consumption at the cost of time.