HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Zeta36
chess-alpha-zero
Jupyter Notebook2018–2018
Zeta36 / chess-alpha-zero

chess-alpha-zero

Chess reinforcement learning by AlphaGo Zero methods.

2Distinct people
2Mentions
0Explicit recommenders
2.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Chess reinforcement learning by AlphaGo Zero methods.

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, 3:56:07 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 week2 dated mentions

Observed mentions: 2018-03-03 18:53:23 UTC to 2018-08-20 15:37:09 UTC. Weeks start Monday, UTC.

012018-02-26 00:00:00 UTC to 2018-03-05 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 262018-03-05 00:00:00 UTC to 2018-03-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-03-12 00:00:00 UTC to 2018-03-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-03-19 00:00:00 UTC to 2018-03-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-03-26 00:00:00 UTC to 2018-04-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-02 00:00:00 UTC to 2018-04-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-09 00:00:00 UTC to 2018-04-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-16 00:00:00 UTC to 2018-04-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-23 00:00:00 UTC to 2018-04-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-30 00:00:00 UTC to 2018-05-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-05-07 00:00:00 UTC to 2018-05-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-05-14 00:00:00 UTC to 2018-05-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-05-21 00:00:00 UTC to 2018-05-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 212018-05-28 00:00:00 UTC to 2018-06-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-04 00:00:00 UTC to 2018-06-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-11 00:00:00 UTC to 2018-06-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-18 00:00:00 UTC to 2018-06-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-25 00:00:00 UTC to 2018-07-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-07-02 00:00:00 UTC to 2018-07-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-07-09 00:00:00 UTC to 2018-07-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-07-16 00:00:00 UTC to 2018-07-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-07-23 00:00:00 UTC to 2018-07-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-07-30 00:00:00 UTC to 2018-08-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-08-06 00:00:00 UTC to 2018-08-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-08-13 00:00:00 UTC to 2018-08-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-08-20 00:00:00 UTC to 2018-08-27 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 20

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
Feb 262018-02-26 00:00:00 UTC2018-03-05 00:00:00 UTC110
Mar 52018-03-05 00:00:00 UTC2018-03-12 00:00:00 UTC000
Mar 122018-03-12 00:00:00 UTC2018-03-19 00:00:00 UTC000
Mar 192018-03-19 00:00:00 UTC2018-03-26 00:00:00 UTC000
Mar 262018-03-26 00:00:00 UTC2018-04-02 00:00:00 UTC000
Apr 22018-04-02 00:00:00 UTC2018-04-09 00:00:00 UTC000
Apr 92018-04-09 00:00:00 UTC2018-04-16 00:00:00 UTC000
Apr 162018-04-16 00:00:00 UTC2018-04-23 00:00:00 UTC000
Apr 232018-04-23 00:00:00 UTC2018-04-30 00:00:00 UTC000
Apr 302018-04-30 00:00:00 UTC2018-05-07 00:00:00 UTC000
May 72018-05-07 00:00:00 UTC2018-05-14 00:00:00 UTC000
May 142018-05-14 00:00:00 UTC2018-05-21 00:00:00 UTC000
May 212018-05-21 00:00:00 UTC2018-05-28 00:00:00 UTC000
May 282018-05-28 00:00:00 UTC2018-06-04 00:00:00 UTC000
Jun 42018-06-04 00:00:00 UTC2018-06-11 00:00:00 UTC000
Jun 112018-06-11 00:00:00 UTC2018-06-18 00:00:00 UTC000
Jun 182018-06-18 00:00:00 UTC2018-06-25 00:00:00 UTC000
Jun 252018-06-25 00:00:00 UTC2018-07-02 00:00:00 UTC000
Jul 22018-07-02 00:00:00 UTC2018-07-09 00:00:00 UTC000
Jul 92018-07-09 00:00:00 UTC2018-07-16 00:00:00 UTC000
Jul 162018-07-16 00:00:00 UTC2018-07-23 00:00:00 UTC000
Jul 232018-07-23 00:00:00 UTC2018-07-30 00:00:00 UTC000
Jul 302018-07-30 00:00:00 UTC2018-08-06 00:00:00 UTC000
Aug 62018-08-06 00:00:00 UTC2018-08-13 00:00:00 UTC000
Aug 132018-08-13 00:00:00 UTC2018-08-20 00:00:00 UTC000
Aug 202018-08-20 00:00:00 UTC2018-08-27 00:00:00 UTC101

What Hacker News says

2 sources
Machine learning seems especially prone to attracting "aggregators" - resources whose sole purpose is to enthusiastically collect, promote and/or promulgate other resources for learning about the subject (or one of its sub-disciplines). I think we're starting to get at least one of these a week. That observation aside, this isn't the first time this has been submitted by the author. That's not a problem in of itself, but I'd like to repeat part of my original critique [1] of this website when it was submitted a few months ago. The author is pretty transparent about the way in which these resources are collected - they're automatically scraped from GitHub. I don't think that's intrinsically bad, but it does mean that due diligence is somewhat lacking. For example, consider the "model" page for Chess Reinforcement Learning: https://modelzoo
Read the rest
.co/model/chess-reinforcement-learning. That lists the README for the corresponding GitHub repository [2] verbatim. But the README specifically states that work on the model has been discontinued in favor of a new, better model's repository [3]. Additionally, the authors mention that they had difficulty with some of the implementation related to Self-Play. Now I feel a philosophical point is in order. Ostensibly, an aggregator for resources should helpfully do all or most of the heavy lifting in 1) finding the resources, 2) vetting their completeness as advertised, and 3) maintaining up to date references for the resources it lists. There was no way to distinguish the limitations or obsolescence of the aforementioned model in first looking at it. Rather I had to open the page, click "Get Model" and read through the GitHub README on my own. I see substantially little difference between this activity and simply searching GitHub, considering that every single model I can find is listed on GitHub. This is not to say that this project is bad, I just don't think it's particularly useful in its current form. I understand that's harsh feedback. But in my opinion the author would need to perform far more due diligence on the included models, the implementation artifacts of included models, the people implementing the models themselves and the methodology for model inclusion. As it stands this is presently a collection of models which are in varying states of completeness, developed by people who may or may not be authors of the papers they're implementing (or even have much implementation experience at all), and with varying levels of "out of the box" utility. ___________________ 1. https://news.ycombinator.com/item?id=17311346 2. https://github.com/Zeta36/chess-alpha-zero 3. https://github.com/glinscott/leela-chess
In Reinforcement Learning Resources, Models and Code

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.