OpenWorldLib
Unified Codebase for Advanced World Models.
Runssource: GitHubPythonApache-2.0commit 32f7553566cc
Python, Apache-2.0 licensed. The project labels itself: 3d scene generation, awesome world model, diffusion models, gaussian splatting, hunyuan world, lingbot world, simulator and vggt.
OpenWorldLib runs. An Argusic agent installed it in 11 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OpenWorldLib installed in Python venv, all 39 pipeline packages import successfully, DepthAnything pipeline runs end-to-end on CPU producing real depth map output from a HuggingFace model.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- pycuda failed to build (missing pyconfig.h / python3-dev headers, no root access)5 minutes
- torchaudio 2.11.0 incompatible with torch 2.5.1 (aoti_torch_abi_version symbol)3 minutes
- numpy 2.x incompatible with compiled pyarrow/pandas modules1 minute
- plyfile module missing for VGGT pipeline0.5 minutes
- Install time
- 11 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- python test/test_depth_anything_v1.py completed -> produced vis_depth/ref_image_depth.png (640x360 RGB, 65675 bytes); all 39 pipeline packages imported successfully
- Model tokens used
- 90,837
- Exact commit tested
- 32f7553566cc
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc "/work/repo/venv/bin/python -c \"from PIL import Image; import os; f='/work/repo/vis_de…
succeeded in 0ms:
verified execution depth_pipeline= True size= (640, 360) mode= RGB bytes= 65675
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 1…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 11, "errors": [{"msg": "py…
exec
/bin/sh -lc "echo \"ARGUSIC_RESULT:{\\\"install_succeeded\\\":true,\\\"launch_succeeded\\\":true,\\…
succeeded in 0ms:
tokens used
90,837Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 11 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.07 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.16 |
Topics (from GitHub)
3d-scene-generationawesome-world-modeldiffusion-modelsgaussian-splattinghunyuan-worldlingbot-worldsimulatorvggtvideo-editingvlavlmworld-modelworld-models
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openworldlib)Questions
- Does OpenWorldLib run?
- Yes. OpenWorldLib runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test OpenWorldLib?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 32f7553566cc. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test OpenWorldLib?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OpenWorldLib take to install?
- 11 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does OpenWorldLib need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OpenWorldLib?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for OpenWorldLib?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.