Who it is forAn ML researcher who has a renderer checkpoint and needs to judge its visual quality before deciding what to do next.
The problemJudging a checkpoint by loss numbers alone does not show whether the rendered video looks right against ground truth.
The outcomeDepth, normal, ground truth, and sample comparison videos written under samples/ for visual review.
What you need first
- A CUDA host with Python 3.11+ and PyTorch 2.9+
- Access to the Hugging Face weights for Cosmos3-Nano and Wan2.2-TI2V-5B, plus disk space for them
- Git and the hf command-line tool
- For training: a JSONL manifest of your own clips with depth and normal data
Steps
git clone https://github.com/MirroS-Lab/AgentGarten.gitpip install -e '.[data,media,wandb,te]'cp .env.example .env- Run
hf download nvidia/Cosmos3-Nano --include 'transformer/*' 'text_tokenizer/*' 'assets/negative_prompt.json' --local-dir weights/Cosmos3-Nanoandhf download Wan-AI/Wan2.2-TI2V-5B Wan2.2_VAE.pth --local-dir weights/Wan2.2-TI2V-5B, then set WM_COSMOS3_NANO and WM_WAN22_VAE in .env to those paths. (inferred, check the README) bash scripts/run.sh experiment=cosmos3/bidirectional train.max_iterations=0 train.validate_at_start=true trainer.callbacks.samples.every_n=1(inferred, check the README)
Prompt for your agent
Using the AgentGarten repo at <repo path>, set up the environment, download the weights listed in the README, and render the validation clips of the checkpoint at <checkpoint path> without training. Expected output: comparison videos (depth, normal, ground truth, sample) under samples/. Verify that the samples/ folder contains one video set per validation clip before reporting success.
Caveat. The README does not show how to load a specific checkpoint path directly, so the checkpoint may need to be selected through the training config (inferred).
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page