HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
lucidrains
parti-pytorch
Python2022–2022
lucidrains / parti-pytorch

parti-pytorch

Implementation of Parti, Google's pure attention-based text-to-image neural network, in Pytorch

2Distinct people
2Mentions
0Explicit recommenders
536GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Implementation of Parti, Google's pure attention-based text-to-image neural network, in Pytorch

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 6-hour interval2 dated mentions

Observed mentions: 2022-06-23 03:54:48 UTC to 2022-06-27 20:18:44 UTC.

012022-06-23 00:00:00 UTC to 2022-06-23 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 23, 00:002022-06-23 06:00:00 UTC to 2022-06-23 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-23 12:00:00 UTC to 2022-06-23 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-23 18:00:00 UTC to 2022-06-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-24 00:00:00 UTC to 2022-06-24 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-24 06:00:00 UTC to 2022-06-24 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-24 12:00:00 UTC to 2022-06-24 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-24 18:00:00 UTC to 2022-06-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-25 00:00:00 UTC to 2022-06-25 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-25 06:00:00 UTC to 2022-06-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 25, 06:002022-06-25 12:00:00 UTC to 2022-06-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-25 18:00:00 UTC to 2022-06-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-26 00:00:00 UTC to 2022-06-26 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-26 06:00:00 UTC to 2022-06-26 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-26 12:00:00 UTC to 2022-06-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-26 18:00:00 UTC to 2022-06-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-27 00:00:00 UTC to 2022-06-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-27 06:00:00 UTC to 2022-06-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-27 12:00:00 UTC to 2022-06-27 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-27 18:00:00 UTC to 2022-06-28 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 27, 18:00

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
Jun 23, 00:002022-06-23 00:00:00 UTC2022-06-23 06:00:00 UTC101
Jun 23, 06:002022-06-23 06:00:00 UTC2022-06-23 12:00:00 UTC000
Jun 23, 12:002022-06-23 12:00:00 UTC2022-06-23 18:00:00 UTC000
Jun 23, 18:002022-06-23 18:00:00 UTC2022-06-24 00:00:00 UTC000
Jun 24, 00:002022-06-24 00:00:00 UTC2022-06-24 06:00:00 UTC000
Jun 24, 06:002022-06-24 06:00:00 UTC2022-06-24 12:00:00 UTC000
Jun 24, 12:002022-06-24 12:00:00 UTC2022-06-24 18:00:00 UTC000
Jun 24, 18:002022-06-24 18:00:00 UTC2022-06-25 00:00:00 UTC000
Jun 25, 00:002022-06-25 00:00:00 UTC2022-06-25 06:00:00 UTC000
Jun 25, 06:002022-06-25 06:00:00 UTC2022-06-25 12:00:00 UTC000
Jun 25, 12:002022-06-25 12:00:00 UTC2022-06-25 18:00:00 UTC000
Jun 25, 18:002022-06-25 18:00:00 UTC2022-06-26 00:00:00 UTC000
Jun 26, 00:002022-06-26 00:00:00 UTC2022-06-26 06:00:00 UTC000
Jun 26, 06:002022-06-26 06:00:00 UTC2022-06-26 12:00:00 UTC000
Jun 26, 12:002022-06-26 12:00:00 UTC2022-06-26 18:00:00 UTC000
Jun 26, 18:002022-06-26 18:00:00 UTC2022-06-27 00:00:00 UTC000
Jun 27, 00:002022-06-27 00:00:00 UTC2022-06-27 06:00:00 UTC000
Jun 27, 06:002022-06-27 06:00:00 UTC2022-06-27 12:00:00 UTC000
Jun 27, 12:002022-06-27 12:00:00 UTC2022-06-27 18:00:00 UTC000
Jun 27, 18:002022-06-27 18:00:00 UTC2022-06-28 00:00:00 UTC110

What Hacker News says

2 sources
Give it a few days and lucidrains will have the code up[0]. But in honesty, it is probably how people react. We saw this with Pulse, GPT, and many others. The authors are clear about the limitations but people talk it up too much and others shit on it. There's also a reproducibility crisis in ML (many famous networks, like Swin[1][2][3], can't be reproduced (even worse when reviewers concentrate on benchmarks)). It isn't like many can train a model like this anyways. It gives them benefit of the doubt and maintains good publicity rather than controversial. Of course, this is extremely bad from an academic perspective and personally I believe you should have your paper revoked if it isn't reproducible. You'd be surprised how many don't track the random seed or measure variance. We have GitHub. You should be able to write training options t
Read the rest
In Parti: Pathways Autoregressive Text-to-Image Model

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.