Live data from Hacker News

Viewing profile — wholehog

wholehog

HN member
Joined
Fri, Nov 22, 2024, 8:45 PM UTC
HN karma
29
Public activity
33 items

About wholehog

No profile information was provided.

Recent public activity

  1. comment
    Comment #42350569

    If someone tries to run your method but messes it up, and then accuses you of fraud when the results don't match their expectations, I'm not sure they're entitled to a neutral tone…

  2. comment
    Comment #42350433

    I think the pre-trained checkpoint uses the same 20 TPU blocks as the original paper, but it probably isn't the exact-same checkpoint, as the paper itself is from 2020/2021.

  3. comment
    Comment #42350389

    As Andrew Kahng was one of the co-authors of Cheng et al., all of the issues with his reproduction still matter here. The Nature paper went through an investigation and second roun…

  4. comment
    Comment #42350302

    Three generations of TPU, Axion (ARM-based CPU), various other chips at AlphaBet, MediaTek's usage...

  5. comment
    Comment #42350288

    The UCSD paper didn't run the Nature method correctly, so I don't see how you can draw this conclusion. From Jeff's tweet: "In particular the authors did no pre-training (despite p…

  6. comment
    Comment #42324843

    "Prior to publication of Cheng et al., our last correspondence with any of its authors was in August of 2022 when we reached out to share our new contact information." You don't st…

  7. comment
    Comment #42302070

    "These major methodological differences unfortunately invalidate Cheng et al.’s comparisons with and conclusions about our method. If Cheng et al. had reached out to the correspond…

  8. comment
    Comment #42299100

    I mean, I think second is still "one of the first?" And, no offense to this project, but I don't know of it being used in a real industrial setting, whereas AlphaChip was used in T…

  9. comment
    Comment #42299016

    So much wasted time. He even ran a study internally (with Markov), but, as the AlphaChip authors describe: In 2022, it was reviewed by an independent committee at Google, which det…

  10. comment
    Comment #42298951

    > Does the EDA ecosystem support a similarly open culture of benchmarking for commercial tools? If only. The comparison in Cheng et al. is the only public comparison with CMP that …

  11. comment
    Comment #42298836

    > 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? The Circuit Training repo was just …

  12. comment
    Comment #42298661

    Bitter Lesson: https://www.cs.utexas.edu/~eunsol/courses/data/bitter_lesson...

  13. comment
    Comment #42298651

    Are you really suggesting that the TPU team does not stand behind the graphs in Google's own blog post? And that MediaTek does not stand behind their quoted statement?

  14. comment
    Comment #42298447

    His original complaint being dismissed matters because it suggests that he was fishing around for a complaint that was valid, and that perhaps his primary motivation was to get mon…

  15. comment
    Comment #42298354

    > it might have a harder time with a chip designed by a third party (further from its pre-training). Then they could pre-train on chips that are in-distribution for that task. See …

  16. comment
    Comment #42293693

    They also changed the ratio of RL experience collectors to GPU workers (~1/20th the RL experience collectors, 1/2 the GPUs). I don't know what impact that has --- maybe each GPU ep…

  17. comment
    Comment #42293676

    > published a crappy article in Nature because it would never have passed editorial muster at something like DAC or an IEEE journal and now have to browbeat other people who are ca…

  18. comment
    Comment #42293649

    Pre-training is just training on multiple chips. "If Cheng et al. had reached out to the corresponding authors of the Nature paper, we would have gladly helped them to correct thes…

  19. comment
    Comment #42293605

    That is definitely a cool project, but I don't see how it contradicts "one of the first RL methods deployed to solve a real-world engineering problem". "One of the first" does not …

  20. comment
    Comment #42293588

    It is open: https://github.com/google-research/circuit_training

  21. comment
    Comment #42293578

    > The whole publication process seems dishonest, starting from publishing in Nature (why not ISCCC or something similar?) Why would you publish in ISCCC when you can get into Natur…

  22. comment
    Comment #42293472

    You're linking to his amended complaint - his original complaint was thrown out because it alleged things like "Google's motto is don't be evil, but they were evil, thus defrauding…

  23. comment
    Comment #42293431

    What are you even talking about? Jeff had a hand in TPU, which is so successful that all other AI companies are trying to clone this project and spin up their own efforts to make c…

  24. comment
    Comment #42293421

    > Some would say he got taken for a ride by a young charismatic grifter and is now in too deep to back out. Was the TPU physical design team also taken in? And also MediaTek? And a…

  25. comment
    Comment #42293411

    See my comment above - the Nature authors already did this, and tried a huge hyperparameter sweep for SA, and RL still won. See appendix of the Nature article: rdcu.be/cmedX