HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
google-research
circuit_training
Python2022–2025
google-research / circuit_training

circuit_training

Discover this repository through its Hacker News conversations.

10Distinct people
10Mentions
0Explicit recommenders
1.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

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 year10 dated mentions

Observed mentions: 2022-01-19 02:21:20 UTC to 2025-02-20 00:28:44 UTC.

012342022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

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
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC321
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

10 sources
> "scientific publication" These air quotes suggests the commenter above doesn't think the paper qualifies a scientific publication. Such a characterization is unfair. When I read the Nature article titled "Addendum: A graph placement methodology for fast chip design" [1], I see writing that more than meets the bar for a scientific publication. For example: > Since publication, we have open-sourced a software repository [21] to fully reproduce the methods described in our paper. External researchers can use this repository to pre-train on a variety of chip blocks and then apply the pre-trained model to new blocks, as was done in our original paper. As part of this addendum, we are also releasing a model checkpoint pre-trained on 20 TPU blocks [22]. For best results, however, we continue to recommend that developers pre-train on their own
Read the rest
in-distribution blocks [18], and provide a tutorial on how to perform pre-training with our open-source repository [23]. [1]: https://www.nature.com/articles/s41586-024-08032-5 [18]: Yue, S. et al. Scalability and generalization of circuit training for chip floorplanning. In Proc. 2022 International Symposium on Physical Design 65–70 (2022). [21]: Guadarrama, S. et al. Circuit Training: an open-source framework for generating chip floor plans with distributed deep reinforcement learning. GitHub https://github.com/google-research/circuit_training (2021). [23]: Guadarrama, S. et al. Pre-training. GitHub https://github.com/google-research/circuit_training/blob/mai... (2021).
In Jeff Dean responds to EDA industry about AlphaChip
In the tweet Jeff Dean says that Cheng at al. failed to follow the steps required to replicate the work of the Google researchers. Specifically: > In particular the authors did no pre-training (despite pre-training being mentioned 37 times in our Nature article), robbing our learning-based method of its ability to learn from other chip designs But in the Circuit Training Google repo[1] they specifically say: > Our results training from scratch are comparable or better than the reported results in the paper (on page 22) which used fine-tuning from a pre-trained model. I may be misunderstanding something here, but which one is it? Did they mess up when they did not pre-train or they followed the "steps" described in the original repo and tried to get a fair reproduction? Also, the UCSD group had to reverse-engineer several steps to reproduc
Read the rest
e the results so it seems like the paper's results weren't reproducible by themselves. [1]: https://github.com/google-research/circuit_training/blob/mai...
In Jeff Dean responds to EDA industry about AlphaChip
As someone who has no skin in the game and is only loosely following this, there is a tool: https://github.com/google-research/circuit_training, the detractors claim to not be able to reproduce Google's results (what Dean is commenting on) with it, Google and 1-2 other companies claim to be using it internally to success (e.g. see the end of this article: https://deepmind.google/discover/blog/how-alphachip-transfor...).
In Jeff Dean Responds to EDA Industry about AlphaChip
One is basically an evidence-free ad hominem attack. > [2] https://twitter.com/JacobSteinhardt/status/15215993404137881... The other two sources make a concrete claim that in mid-2002 there was an independent, open-source, replication of the Nature paper: > [1] https://twitter.com/ZoubinGhahrama1/status/15122035096467415... >> Google stands by this work published in Nature on ML for Chip Design, which has been independently replicated, open-sourced, and used in production at Google. > [3] https://twitter.com/sguada/status/1521587406385807361 >> The results in the Nature paper were independently replicated and validated by my team, the results were used in actual chips and Sat and his collaborators know it. >> Furthermore, the code was open-sourced. >> It is sad that you are providing a platform for someone's resentments. The claims about
Read the rest
independent replication refer to Google's circuit_training repository[1]. The UCSD team has conclusively shown this claim was materially false (see section 3 of their paper[2]). BTW, Prof. Andrew Khang, who headed the UCSD effort, initially wrote an exteremely favorable editorial about the Nature paper[3]. [1] https://github.com/google-research/circuit_training [2] https://arxiv.org/pdf/2302.11014.pdf [3] https://www.nature.com/articles/d41586-021-01515-9
In The False Dawn: Reevaluating Google's RL for Chip Macro Placement
Igor Markov, along with Sat Chatterjee, seem to be pursuing a bizarre vendetta (after Sat failed to take over their project) against the lead authors of the chip placement work, not some sort of intellectually honest critique. This was covered previously in the press and on social media, with statements from a variety of prominent researchers (e.g. [1][2][3]). The code is even available for the Nature paper's method, along with an FAQ: https://github.com/google-research/circuit_training#FAQ [1] https://twitter.com/ZoubinGhahrama1/status/15122035096467415... [2] https://twitter.com/JacobSteinhardt/status/15215993404137881... [3] https://twitter.com/sguada/status/1521587406385807361
In The False Dawn: Reevaluating Google's RL for Chip Macro Placement
The TF-Agents team replicated the RL training (with the corresponding teams' very deep collaboration) and open-sourced it here: https://github.com/google-research/circuit_training It pretty much gets the same results as found in the Nature paper. The original codebase was heavily research-focused, used TF1, was impossible to run distributed training outside of Google's infra, and made it hard to try algorithms other than PPO. So it was reimplemented on top of TF2 and using some distributed training and collection technologies developed by the TF-Agents team at Google Brain and infra teams at DeepMind. Everyone is welcome to poke at the training code and the model, and convince themselves that it does what it says on the box :)
In Google fires another AI researcher who reportedly challenged findings

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.