-
Notifications
You must be signed in to change notification settings - Fork 2
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
Sqlite solving #4
Draft
OverkillGuy
wants to merge
16
commits into
master
Choose a base branch
from
sqlite-solve
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains 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
Enable math functions[1] by using a dedicated fresh build of sqlite3 instead of native stdlib, which is compiled without it. Build is from pysqlite3 lib, specced as pre-built binary, I don't have all day to compile this myself. See pysqlite3 project docs[2] specifying their sqlite3 config flags. [1]: https://www.sqlite.org/lang_mathfunc.html [2]: https://github.com/coleifer/pysqlite3
Now the sqlite in Python supports math operators, we can fill in entropy via SQL operations, rather than compute in pure Python. This is because crucial math func log2 is now available in pysqlite3. Unfortunately I'm limited by my own personal knowledge of SQL now. Great project to learn though, I'm really enjoying this low-stakes deep dive into SQL with tangible benefits at the end, even if I'm just recreating the results of 3blue1brown at the end: Building this on top of literate_wordle is nice bonus.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Not sure I really want to make another "novel" of this, but investigate solving of Wordle, by brute-force statistics, inspired by 3Blue1Brown.
I've never felt like I mastered SQL, so this is a perfect opportunity to learn, by using sqlite3!
New
sqlite_solve.py
file, pre-computing all wordle guesses against all answers, storing result in new sqlite tables.Tables allow solving wordle in a basic way: pick a good guess, input in wordle, insert the score in DB in a query that lists answers that match that score for that guess.
But as 3Blue1Brown video (linked in docstring) explains, we can optimize guess selection via information theory. This is still WIP in SQL (limited by my own knowledge of SQL queries)