训练测试
active 2026-01-13 → 2026-06-13 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 152 days from 2026-01-13 to 2026-06-13. Pushes: 8 total, peak 1 in a day. Pull requests: 3 total, peak 1 in a day. Issues: 22 total, peak 3 in a day. Comments: 39 total, peak 5 in a day. Stars: 184 total, peak 49 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| ZiwenZhuang | 22 | 8 | 0 | 11 |
| zst1406217 | 10 | 0 | 1 | 9 |
| LEECHOONGHO | 6 | 0 | 0 | 2 |
| ZZQ0316 | 4 | 0 | 0 | 2 |
| Lebron-233 | 3 | 0 | 0 | 2 |
| tony-hj | 2 | 0 | 0 | 2 |
| rllearnerntu | 2 | 0 | 0 | 1 |
| WeisonWEileen | 2 | 0 | 0 | 1 |
| nuliguangxiaoyang-crypto | 1 | 0 | 0 | 0 |
| DIMARIA123 | 1 | 0 | 0 | 0 |
| HuiyangCao | 1 | 0 | 0 | 0 |
| BruceXing24 | 1 | 0 | 0 | 1 |
| hkhkhkz | 1 | 0 | 0 | 0 |
| AngLi-00 | 1 | 0 | 0 | 0 |
| fanyahao1 | 1 | 0 | 1 | 0 |
| PapadeStonne | 1 | 0 | 0 | 1 |
| binaryoung | 1 | 0 | 0 | 1 |
| xuwentai | 1 | 0 | 0 | 1 |
| congzz | 1 | 0 | 0 | 0 |
| ozzyc550 | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#39BruceXing242026-06-09 08:33When running the demo, I encountered this issue where there was no action dataset.
- Issue comment#39Yibming2026-05-29 10:30When running the demo, I encountered this issue where there was no action dataset.
- Issue comment#52zst14062172026-05-17 06:21Real machine deployment issues
- Issue comment#49zst14062172026-05-17 06:16sim2sim
- Issue comment#47zst14062172026-04-11 03:14请问，该项目可以在isaac sim4.5的版本下运行吗？
- Issue comment#30zst14062172026-04-11 03:13Do the two path files in AmassMotionCfg have Google Drive examples?
- Issue#42ZZQ03162026-04-02 07:10About the released parkour policy model
- Issue#48hkhkhkz2026-04-02 05:48Robot hesitates/stalls and oscillates before stairs during Parkour task inference
- Issue#43LEECHOONGHO2026-03-28 23:10Do Human Reference motion need to be retargeted to g1_29dof_torsoBase_popsicle_with_shoe.urdf?
- Pull request#44Xinyu-Sheng2026-03-22 11:36
- Issue comment#39xuwentai2026-03-19 03:17When running the demo, I encountered this issue where there was no action dataset.
- Issue#9LEECHOONGHO2026-03-16 04:21Question about the possibility of re-licensing to BSD-3-Clause
- Issue comment#41ZZQ03162026-03-12 01:30sim2sim
- Issue#41congzz2026-03-02 10:22sim2sim
- Pull request#38zst14062172026-02-27 02:33
- Issue comment#31zst14062172026-02-26 03:13Depth image dimension mismatch in parkour code
- Issue comment#7ZiwenZhuang2026-02-13 09:17The raw human motion data
- Issue comment#7binaryoung2026-02-12 07:41The raw human motion data
- Issue#34LEECHOONGHO2026-02-11 09:22Does Instinct-Parkour-Target-Amp-G1-v0 train task supports multi-GPU training?
- Issue#36LEECHOONGHO2026-02-11 04:05Can I add randomization of step_width for pyramid_stairs in terrain generator?
- Issue comment#34ZiwenZhuang2026-02-10 08:00Does Instinct-Parkour-Target-Amp-G1-v0 train task supports multi-GPU training?
- Issue comment#34LEECHOONGHO2026-02-10 03:57Does Instinct-Parkour-Target-Amp-G1-v0 train task supports multi-GPU training?
- Issue#35AngLi-002026-02-10 03:31LFS rules conflict with existing non‑LFS PNG, causing persistent dirty working tree
- Issue comment#17ZiwenZhuang2026-02-09 16:09Bad performance on AMP-Parkour task(Instinct-Parkour-Target-Amp-G1-v0)
- Issue comment#34ZiwenZhuang2026-02-09 11:37Does Instinct-Parkour-Target-Amp-G1-v0 train task supports multi-GPU training?
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 184 stars here means stars gained during the window, not the repo's star count.