← Back to Product Feed

GitHub Open Source PKU-YuanGroup/Helios

Helios: Real Real-Time Long Video Generation Model

1,164
Traction Score
74
Forks
Mar 2, 2026
Launch Date
View Origin Link

Product Positioning & Context

AI Executive Synthesis
A 'Real Real-Time Long Video Generation Model.'
This issue is a direct request for Helios's training data to be made publicly available. This reflects a common developer need for transparency and reproducibility in AI model development. Access to training data is crucial for researchers to understand model biases, replicate results, and potentially fine-tune models for specific use cases. For B2B SaaS, while proprietary training data can be a competitive advantage, making subsets or anonymized versions available can foster community engagement, accelerate research, and build trust. The decision to share or withhold training data has significant implications for ecosystem development and the broader adoption of the model in academic and commercial settings.
Helios: Real Real-Time Long Video Generation Model
acceleration diffusion diffusion-model diffusion-models efficient-tuning high-quality image-to-video image2video

Related Ecosystem & Alternatives

Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.

Deep-Dive FAQs

What is PKU-YuanGroup/Helios?
PKU-YuanGroup/Helios is analyzed by our AI as: A 'Real Real-Time Long Video Generation Model.'. It focuses on This issue is a direct request for Helios's training data to be made publicly available. This reflects a common developer need for transparency and...
Where did PKU-YuanGroup/Helios originate?
Data for PKU-YuanGroup/Helios was aggregated directly from the GitHub Open Source community ecosystem, representing raw developer and early-adopter sentiment.
When was PKU-YuanGroup/Helios publicly launched?
The initial public indexing or launch date for PKU-YuanGroup/Helios within our tracked developer communities was recorded on March 2, 2026.
How popular is PKU-YuanGroup/Helios?
PKU-YuanGroup/Helios has achieved measurable traction, logging over 1,164 traction score and facilitating 74 recorded discussions or engagements.
Which technical categories define PKU-YuanGroup/Helios?
Based on metadata extraction, PKU-YuanGroup/Helios is categorized under topics such as: acceleration, diffusion, diffusion-model, diffusion-models.
Are there active development issues for PKU-YuanGroup/Helios?
Yes, we are currently tracking open architectural debates and bug reports for this project on GitHub. There are currently 5 active high-priority issues logged recently.
What are some commercial alternatives to PKU-YuanGroup/Helios?
Our semantic intelligence engine identifies potential commercial alternatives in the SaaS space, such as Monkey Morse, which offers overlapping value propositions.
How does the creator describe PKU-YuanGroup/Helios?
The original author or development team describes the product as follows: "Helios: Real Real-Time Long Video Generation Model"

Active Developer Issues (GitHub)

open is_amplify_history 和 restrict_self_attn 问题
Logged: Apr 7, 2026
open 参考图加噪问题
Logged: Apr 3, 2026
open Question about Helios-Base speed in Table 3
Logged: Apr 2, 2026
open Is it possible to make the training data available?
Logged: Apr 2, 2026
open 能在双卡H20 上微调吗
Logged: Apr 1, 2026

Community Voice & Feedback

hotfinda • Apr 2, 2026
@SHYuanBest 您好,我重启了一次stage1_init训练,8卡,batchsize=2, i2v的训练任务,把random_drop_t2v_ratio和random_drop_v2v_ratio都设置为了0。样本量比较少,一开始训练了3000step,视频的sections之间的闪烁在减弱,但是后面训练到了7000step,场景变化反而更大了,画面也开始变糊,请问这种现象是正常的吗?还是我应该直接继续做post训练呢?
下面是在3000和7000分别推理的视频

https://github.com/user-attachments/assets/5f1ee867-d6a8-44a0-aa49-b74b925b22ad

https://github.com/user-attachments/assets/24dcfcfc-3f32-4d9a-8ed1-b418806f9d23
SHYuanBest • Apr 1, 2026
1. "现在训练数据采样每次不都是从一段视频中采样连续的帧,一部分作为history 一部分作为待生成的,这样的话长视频和100多帧不是一样的吗":是的
2. “为啥长视频效果会更好呢~”:主要是为了让first frame anchor以"矫正drifting"的功能出现,而不是以"让模型copy首帧的内容"的功能出现。否则如果用短视频,就会出现和longlive、rollingforcing类似的那种运动静止的缺陷
silence401 • Apr 1, 2026
> 我们的视频数据大多是几百帧的clips;可以的,个人感觉是长视频效果更佳。

现在训练数据采样每次不都是从一段视频中采样连续的帧,一部分作为history 一部分作为待生成的,这样的话长视频和100多帧不是一样的吗。为啥长视频效果会更好呢~
hotfinda • Mar 31, 2026
好的好的,感谢~我试一下
SHYuanBest • Mar 31, 2026
我们的视频数据大多是几百帧的clips;可以的,个人感觉是长视频效果更佳。
SHYuanBest • Mar 31, 2026
bs有点小,可以试着把`random_drop_t2v_ratio`关小,不然模型没学多少v2v任务
hotfinda • Mar 31, 2026
您好,我训练了8000step, batchsize1,lr固定5e-5
Yangxiaoda1 • Mar 31, 2026
如果训练数据是长度是1分钟的视频或者更长可以吗
SHYuanBest • Mar 31, 2026
排除代码/权重加载问题前提下,训练一开始是这样的,往后训会逐渐连贯。你这个大概训了多久?batchsize和lr分别是多少?
SHYuanBest • Mar 24, 2026
基于Helios-base模型训完了stage-1-post指的是跑完了以下三个步骤?

1. 加载wan_transformer,用stage-1-inint去训,得到A lora_ckpt + A partial_ckpt
2. merge wan_transformer + A lora_ckpt + A partial_ckpt得到B_transformer
3. 得到B_transformer,用stage-1-post去训,得到B lora_ckpt + B partial_ckpt
4. 此时merge的时候应该加载B_transformer
Iriya99 • Mar 24, 2026
> pipe填wan或者helios的路径都行。transformer得看你训练的时候用了哪个transformer,比如stage-1-init用的是wan的transformer,此时填wan的路径,其他阶段以此类推。

这里没太理解。我目前是基于Helios-base模型训完了stage-1-post,那么我pipe和transformer分别应该填什么?以及合并后的代码对于后续的训练和推理是否都是通用的?
SHYuanBest • Mar 24, 2026
pipe填wan或者helios的路径都行。transformer得看你训练的时候用了哪个transformer,比如stage-1-init用的是wan的transformer,此时填wan的路径,其他阶段以此类推。
Iriya99 • Mar 24, 2026
> [@Iriya99](https://github.com/Iriya99) 感谢关注!请使用`merge_lora_for_helios.py`进行代码合并。 https://github.com/PKU-YuanGroup/Helios/blob/main/tools/merge_lora_for_helios.py

transformer和pipe中from_pretrained都填Helios-Base的路径对吗
SHYuanBest • Mar 24, 2026
@Iriya99 感谢关注!请使用`merge_lora_for_helios.py`进行代码合并。
https://github.com/PKU-YuanGroup/Helios/blob/main/tools/merge_lora_for_helios.py
SHYuanBest • Mar 13, 2026
看着和这个PR有点像: https://github.com/PKU-YuanGroup/Helios/issues/5

Discovery Source

GitHub Open Source GitHub Open Source

Aggregated via automated community intelligence tracking.

Tech Stack Dependencies

No direct open-source NPM package mentions detected in the product documentation.

Media Tractions & Mentions

No mainstream media stories specifically mentioning this product name have been intercepted yet.

Deep Research & Science

No direct peer-reviewed scientific literature matched with this product's architecture.