HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Kyubyong
sudoku
Python2016–2017
Kyubyong / sudoku

sudoku

Can Neural Networks Crack Sudoku?

3Distinct people
3Mentions
0Explicit recommenders
868GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Can Neural Networks Crack Sudoku?

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2016-12-29 15:11:07 UTC to 2017-06-12 12:47:18 UTC. Weeks start Monday, UTC.

0122016-12-26 00:00:00 UTC to 2017-01-02 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 262017-01-02 00:00:00 UTC to 2017-01-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-09 00:00:00 UTC to 2017-01-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-16 00:00:00 UTC to 2017-01-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-23 00:00:00 UTC to 2017-01-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-30 00:00:00 UTC to 2017-02-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-06 00:00:00 UTC to 2017-02-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-13 00:00:00 UTC to 2017-02-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-20 00:00:00 UTC to 2017-02-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-02-27 00:00:00 UTC to 2017-03-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-06 00:00:00 UTC to 2017-03-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-13 00:00:00 UTC to 2017-03-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-03-20 00:00:00 UTC to 2017-03-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 202017-03-27 00:00:00 UTC to 2017-04-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-04-03 00:00:00 UTC to 2017-04-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-04-10 00:00:00 UTC to 2017-04-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-04-17 00:00:00 UTC to 2017-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-04-24 00:00:00 UTC to 2017-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-05-01 00:00:00 UTC to 2017-05-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-05-08 00:00:00 UTC to 2017-05-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-05-15 00:00:00 UTC to 2017-05-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-05-22 00:00:00 UTC to 2017-05-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-05-29 00:00:00 UTC to 2017-06-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-06-05 00:00:00 UTC to 2017-06-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-06-12 00:00:00 UTC to 2017-06-19 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsJun 12

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 262016-12-26 00:00:00 UTC2017-01-02 00:00:00 UTC110
Jan 22017-01-02 00:00:00 UTC2017-01-09 00:00:00 UTC000
Jan 92017-01-09 00:00:00 UTC2017-01-16 00:00:00 UTC000
Jan 162017-01-16 00:00:00 UTC2017-01-23 00:00:00 UTC000
Jan 232017-01-23 00:00:00 UTC2017-01-30 00:00:00 UTC000
Jan 302017-01-30 00:00:00 UTC2017-02-06 00:00:00 UTC000
Feb 62017-02-06 00:00:00 UTC2017-02-13 00:00:00 UTC000
Feb 132017-02-13 00:00:00 UTC2017-02-20 00:00:00 UTC000
Feb 202017-02-20 00:00:00 UTC2017-02-27 00:00:00 UTC000
Feb 272017-02-27 00:00:00 UTC2017-03-06 00:00:00 UTC000
Mar 62017-03-06 00:00:00 UTC2017-03-13 00:00:00 UTC000
Mar 132017-03-13 00:00:00 UTC2017-03-20 00:00:00 UTC000
Mar 202017-03-20 00:00:00 UTC2017-03-27 00:00:00 UTC000
Mar 272017-03-27 00:00:00 UTC2017-04-03 00:00:00 UTC000
Apr 32017-04-03 00:00:00 UTC2017-04-10 00:00:00 UTC000
Apr 102017-04-10 00:00:00 UTC2017-04-17 00:00:00 UTC000
Apr 172017-04-17 00:00:00 UTC2017-04-24 00:00:00 UTC000
Apr 242017-04-24 00:00:00 UTC2017-05-01 00:00:00 UTC000
May 12017-05-01 00:00:00 UTC2017-05-08 00:00:00 UTC000
May 82017-05-08 00:00:00 UTC2017-05-15 00:00:00 UTC000
May 152017-05-15 00:00:00 UTC2017-05-22 00:00:00 UTC000
May 222017-05-22 00:00:00 UTC2017-05-29 00:00:00 UTC000
May 292017-05-29 00:00:00 UTC2017-06-05 00:00:00 UTC000
Jun 52017-06-05 00:00:00 UTC2017-06-12 00:00:00 UTC000
Jun 122017-06-12 00:00:00 UTC2017-06-19 00:00:00 UTC211

What Hacker News says

3 sources
I find it interesting that when the NN fails to complete the whole puzzle, it seems to fail spectacularly (github.com/Kyubyong/sudoku#results) -- that is, there aren't a lot of good-partial attempts (90% or above). Does anyone know why this might be the case? Does the first wrong placement of a number in a gap essentially ruin the rest of the guesses?
In Can Neural Networks Crack Sudoku?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.