Simjecture

Try online · Documentation · Research loop · Recorded studies · Contributing

中文安装、使用与开发指南

Hypothesize. Simulate. Falsify.

Simjecture runs autonomous numerical investigations from a human-defined scientific question. An agent designs experiments, searches for counterexamples and tests revised hypotheses. The evidence system preserves what ran and a separate reviewer examines whether the results justify the conclusion.

You set the question, physical scope and budget. The agent chooses how to work. You can inspect intermediate results, steer the investigation and continue it in a new phase. The result is a research record you can follow from hypothesis to code, measurements, counterexamples and review.

The research loop

A counterexample must survive the relevant numerical controls. Under the repair completion policy, the agent then proposes the smallest justified change to the hypothesis, commits its predictions before testing them, and collects fresh validation evidence. Missing evidence sends the work back through the loop.

The answer policy can also finish with a reviewed falsification of the original claim. New browser studies default to answer; the CLI defaults to repair. Both use minimal mode by default: flexible agent strategy, recorded experiments and explicit scientific acceptance. A deadline can leave the question unresolved.

New minimal studies allow experimental solver development by default. The agent can work in a private source fork while preserving the reference installation. Changed builds need independent, source-bound qualification before supporting a claim. Turn this off in the study brief or with --no-allow-solver-development; see solver development and qualification.

The optional research director can stop unaffordable experiments, request a replan and tune remote instrument probe deadlines and retries. Operators can also delegate storage increases for large builds and checkpoints. The monitor shows failures, before/after limits and the reasons for changes; scientific acceptance and the campaign deadline remain separate. See director control and recovery.

Read how the loop works or how evidence is checked.

Follow a real investigation

The 48 hour FRC campaign on eight GPUs ended with its merger hypothesis unresolved. Its report shows the retained plasma fields, numerical controls, model usage, API cost estimates and the controller failures exposed by two days of research. Public tables reproduce the accounting.

Magnetic-island coalescence with FLASH shows density, magnetic geometry and a current sheet evolving in a real MHD calculation. Follow five resistivity cases, two refinements and their evidence map to see what was measured and why the full-range question remains open. The classic campaign and subsequent diagnostic audits remain available.

FLASH → WarpX kinetic follow-up follows an actual MHD current sheet into a kinetic particle simulation. The visual walkthrough locates the patch, opens its pressure-measurement region, and connects field maps and numerical controls to the unresolved scientific claim.

Both plasma investigations include preserved continuation records, downloadable figures and explicit distinctions between a completed simulation, an approved method and an accepted scientific conclusion.

The orbital-accuracy walkthrough uses the current minimal workflow to investigate a concrete question: does small energy error imply an accurate trajectory? It connects the operator's brief, actual numerical experiments, hypothesis revisions and independent review. It found five counterexamples in the original case matrix, then supported a four-case repair using fresh simulations and independent review. The retained record can be verified without a model call.

Earlier records remain available. In the historical Gray–Scott study, the harness rejected an attempt to close a claim using evidence commissioned for a different claim. The agent registered the missing contract and ran fresh experiments before closing it. That record documents the classic workflow; it is not presented as a new-version run.

What the evidence system preserves

A repaired claim cannot reuse old exploratory results as fresh validation. Changed committed source, missing committed cases and altered recorded outputs are checked by the service. Numerical adequacy and scientific interpretation remain review judgments. See the evidence guide.

Try it

Open simjecture.com for the hosted workspace with supplied inference and compute within usage limits. Signed-in visitors can upload files and retain projects. Guest conversations and artifacts are temporary.

For your own Linux or WSL machine, install the latest stable release:

curl -fsSL https://github.com/tomzhu0225/simjecture/releases/latest/download/install.sh | bash

The installer verifies the release bundle and prepares Python and the browser workspace. Reopen it with ~/simjecture/start-workspace. Research files live under ~/simjecture/artifacts/projects. See installation options.

1. Choose a compatible API model or an authenticated native agent in the workspace.
2. Discuss your question and prepare a study brief with Autonomous research.
3. Review its hypothesis, evidence requirements, completion policy and budget.
4. Start the investigation and follow its experiments and Evidence & review.

The first-study tutorial walks through the full counterexample-and-repair workflow. Headless studies cover terminal launches and automation.

For longer-running work, optional projects and workspaces group conversations and shared context, or keep separate local lab environments. The default remains a single personal workspace. CLI and HTTP interfaces expose the same project operations for external agents and scripts.

Bring your instruments and compute

Ordinary Python studies work without an external solver. Optional capabilities include WarpX, operator-supplied FLASH, EOS/opacity tools, ITER diagnostics and GPU cylinder flow. The cylinder solver and its validation records were contributed by Zifei Meng.

An experimental Windows application interface shares job execution, input snapshots and artifact collection across product adapters. It supports CST magnetostatic jobs, native CST Python scripts, and an initial SOLIDWORKS part rebuild/export adapter. These use trusted Windows processes and record exploratory jobs; SOLIDWORKS still needs native model commissioning.

• Commission a scientific instrument or add your own capability.
• Run experiments on local or SSH workers.
• Steer or continue an investigation.
• Compare agents on recorded diagnostic tasks.
• Operate a hosted service.

Native agents retain their existing tools and run with their host-account access. Numerical experiments use the selected execution backend, Bubblewrap by default. Read security guidance and restricted-host setup when deploying workers.

Contribute

Help us test the research process on meaningful questions. Contributions can add scientific instruments, validated diagnostics, reproducible studies, numerical review, documentation or infrastructure. Start with CONTRIBUTING.md or open an issue to discuss a study or a substantial change.

Release notes · Release checks · Research status · Historical records

Citation and license

Use CITATION.cff and identify the exact version and Git commit used for a result. The concept DOI identifies the release series.

Copyright 2026 Bowen Zhu and contributors. Licensed under Apache 2.0. See third-party notices for upstream attribution and redistribution requirements.