Vikshep Studio
Simulate with Geant4.
Analyze deterministically.
Prove it.
Studio is a single application that runs on your desktop and on the Vikshep hosted plane. Both shells use the same engine, so a cloud result and a local result for the same input are identical bytes — verifiable by anyone with the free conformance tool.
Three pillars
Simulate. Analyze. Prove.
Geant4 inside
Simulate
Vikshep embeds your Geant4 detector — it does not replace it. Pass a CSV export from any Geant4 run, or use the bundled Geant4 runner (Desktop) to drive simulation directly from the Workspace. Vikshep ingests the shower, not the simulation logic.
Supported inputs: Geant4 CSV (komal_v1, generic column-map), ROOT TTree, HDF5 Well schema.
Screenshot placeholder
Studio Ingest screen — drag-drop Geant4 CSV, schema detection, aggregate preview
Owner to supply
Deterministic features
Analyze
The wavelet scattering transform cascades fixed analytic Morlet wavelets through the ingested grid. No weights are learned during feature extraction. The feature map cannot adapt to leak mass or encode nuisance variables — that is a theorem, not a tuning choice.
r₂ = S₂/S₁ is scale-free by construction. DisCo enforces statistical independence from the resonance mass.
Screenshot placeholder
Studio Features screen — J/Q/L config form with live filter bank preview and coefficient count
Owner to supply
Determinism Certificates
Prove
Every Studio result carries a Determinism Certificate: the provenance manifest, the conformance evidence (suite version, numerics version, backend, local self-test result), and an optional Ed25519 signature that identifies the installation that produced it. The certificate proves which computation ran; any reviewer can re-run the computation and verify the output OIDs match.
Certificate format: VDS-1. Free offline verifier: vikshep-conformance (open source).
Screenshot placeholder
Studio Provenance screen — hash chain panel with Reproduce button and certificate export
Owner to supply
VDS-1 — Vikshep Determinism Specification
What "deterministic" means, exactly.
VDS-1 defines three tiers. Every Vikshep computation declares which tier its outputs belong to. The certificate records this alongside the engine version and conformance evidence. Plain-language explanation →
Tier 1
Bit-exact on every conforming backend
Tier-1 outputs are identical bytes on CPU (reference Rust), CUDA, and Metal, for the same input and numerics version. Tier 1 covers all S₀, S₁, S₂ and r₂ tensor computations — all IEEE-754 binary32, explicit flush-to-zero semantics, no FMA unless this specification permits it, no libm.
Tier 2
Bit-exact on every platform — Rust CPU only
Tier-2 computations always run in the reference Rust CPU code, regardless of which backend is active. This covers filter and twiddle-table construction, the DisCo statistics (dCorr_w, JSD), anomaly search, and report generation. GPU backends must not re-implement Tier-2 code; they receive Tier-2 results as inputs.
Tier 3
Provenance recorded — not certified
Tier-3 covers operations outside VDS-1 control: Geant4 simulation, loader pre-processing from non-deterministic sources, external model inference. Studio records Tier-3 provenance (tool, version, build, platform, seed), but this specification does not certify Tier-3 reproducibility.
Free offline verifier: vikshep-conformance verify <certificate> --inputs <dir> — re-runs the recorded computation with the open CPU reference and compares every output OID. Prints VERIFIED or MISMATCH. Works fully offline.
Two shells, one engine
Desktop. Hosted. Same bytes.
Desktop
Run on your hardware
The Tauri desktop application bundles the engine and runs compute locally on CPU or GPU (Metal on macOS, CUDA on Linux/Windows). Data never leaves your facility. Optional burst-to-cloud routes individual jobs through your org API key.
- +CPU reference backend — VDS-1 Tier 1 certified
- +Metal (macOS 13+) — in development
- +CUDA (Linux / Windows) — in development
- +Offline licence verification (Ed25519, 24h lease)
- +2 concurrent devices per seat
Hosted
Run on Vikshep workers
The same Studio application served at vikshep-engine.vercel.app, authenticated by your account. Compute runs on managed CPU and GPU workers. Results are content-addressed (28-char OIDs) and carry the same VDS-1 certificates as local runs.
- +CPU workers — VDS-1 Tier 1 certified
- +GPU workers — in development
- +Metered by dataset-shard and scattering run
- +Results stored in content-addressed blob storage
- +7-day trial + 900 GPU-seconds (Lab tier)