NodeValid

Published video-model weights, licences and hardware notes

Pyramid Flow publishes no parameter count

The card for this release names two checkpoints, the resolution each one produces and the seconds each one runs for. It does not say how large the model is, and it is the only release here whose size column is empty. As of 2026-09-22.

Pyramid Flow in the size column, as publishedThe card answers the questions about what comes out and skips the question about what goes on disk, which is the reverse of the usual omission in this register.Fixed by the published countLeft to the runThe countNo parameter count recorded—What it belongs toThe card states none—Licence on that releasestabilityai-ai-community—Memory for a run—No memory figure recordedOutput size—768p, with a 384p checkpointThe empty column is the finding
Fig. 1 Three questions a reader brings to a model card, and which of them this one answers.
What the repositories actually stateFilled where the repository states something, hollow where it does not. A blank is not an inference.What the repositories actually stateWhat the pages stateWhat the pagesstateSize, in the vendor's own wor…Size, in the vendor's own wordsSize, in the vendor's own words — What the pages state: No parameter count recordedThe detail published beside itThe detail published beside it — What the pages state: The card states noneLicence, from the same pagesLicence, from the same pages — What the pages state: stabilityai-ai-communityHardware, from the same pagesHardware, from the same pages — What the pages state: No memory figure recorded
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
Pyramid Flow in the size column, with the columns that qualify it. Read from huggingface.co/rain1011 on 2026-09-22.
ColumnWhat the pages state
Size, in the vendor's own wordsNo parameter count recorded
The detail published beside itThe card states none
Licence, from the same pagesstabilityai-ai-community
Hardware, from the same pagesNo memory figure recorded

Inclusion rule. The value this page is about, the detail the vendor attached to it, and the two columns that change how it should be read. A column the vendor left empty keeps its row and says so. Order. This column first, then its detail, then the two columns that qualify it.

1A missing count is unusual in this column

A parameter count is the cheapest thing a release can publish. It needs no measurement, no hardware and no caveat, which is why the size column is close to full across the register and why one empty cell stands out.

The absence is recorded as an absence. Reading a figure off a configuration file, or off somebody's summary of the architecture, would put a number in the register that nobody published.

2What the card publishes instead

It is generous in the columns that usually go empty. Two checkpoints are described by output rather than by size: ten seconds at 768p on one, five seconds at 384p on the other, both at 24 FPS.

That is a release documented for people who want to know what they will get rather than what they will download. It is a defensible choice and it leaves one question unanswered.

3Why the count would still have been worth having

Size is the only column here that lets two releases be compared directly, because it does not depend on a setting. Without it, this family cannot be placed beside the 2B and 13B releases in the register at all.

It also travels with the licence question. Where a family publishes several sizes the terms can differ between them, and a reader has nothing here to hang that check on.

4Sources

The count comes from huggingface.co/rain1011, read 2026-09-22, exactly as the vendor wrote it. Everything else this release publishes is on its family entry; why the count sits in its own column is on size. Nearby: CogVideoX split licence, SVD commercial pointer.