Getting Started with GDBS Pro
GDBS Pro is a research-grade physics simulation platform that runs in your browser. No cluster queue, no Python install, no conda environment.
What's here
Domain modules cover the textbook ranges of:
- Plasma - tokamak / stellarator / FRC stability + equilibrium
- Fluids - Reynolds, boundary-layer, compressible
- Quantum - DFT, ground-state, multi-electron
- Materials - band structure, lattice dynamics
- Geophysics - gravitational, seismic
- Ballistics - hypersonic trajectory
- Theory - Hawking, fine-structure, SPARC galaxies
Each module ships in two tiers:
- Standard - single-physics exploratory tools (included).
- Pro - multi-physics workflows, optimizer, predictor, validation suite, GeoNum-tracked precision. See the pricing page or the in-app pricing modal for current tiers.
How to read a result
Every solver reports:
- the figure of merit (β_N, q_95, etc.) - hover any symbol for a glossary entry and citation;
- the wall-clock time in milliseconds;
- the GeoNum drift when precision tracking is enabled - uncertainty in shades, not just a number;
- the GeoNum trust verdict - a badge appended to the readout summarising that drift in one word, so you see the true precision of a run and not just its value. Verdicts run from EXACT / PRECISE / VALID (trustworthy at the stated precision) down through DEGRADED / UNRELIABLE / CANCELLED (the result lost significance and should not be trusted). When an engine routes no drift through GeoNum, the badge reads [UNTRACKED] - an honest "we did not track precision here", not a pass;
- the canonical reference the result was benchmarked against, where applicable.
What makes this research-grade
- GeoNum drift tracking. Engines that route their arithmetic through GeoNum carry an uncertainty band on each value, surfaced in the UI. Engines that do not are labelled [UNTRACKED] rather than shown as a pass.
- Validation matrix. Solvers in the matrix are benchmarked against a published, peer-reviewed value. The per-module Validation Suite runs the full matrix and marks each row green (within tolerance of the cited result) or red (out of tolerance), with the reference and DOI shown inline. Only published references are cited - the matrix is checkable against the source paper, not against us.
- Honest runtimes. Most interactive solvers return in seconds; heavier engines state their expected runtime up front (the Euler3D GPU example below takes about 40 seconds).
- Reproducibility. Results export with their inputs and drift readout, so a run can be repeated and checked.
Plugins
Beyond the built-in modules, GDBS loads drop-in plugins. Each tier (Standard, Pro, HPC) has a Plugins link in its module nav that opens a shared plugin catalog.
- Catalog. Plugins appear as cards. A free-text search filters across name, tags, and description, and topic-tag chips narrow the list. First-party VaultSync and VSS-Approved plugins sort to the top; the rest rank by community rating.
- Running one. Click a card to open the plugin panel. A plugin mounts with the full stack - engine, charts, 3D view where applicable, the GeoNum trust verdict badge, and the dev-log / bug-log buttons - exactly like a built-in engine.
- Isolation. Each plugin runs in a hardened sandboxed worker with no network access and a watchdog. Plugins are isolated and run off the main thread, so a long browser-side run will not freeze the page, and a Cancel button stops a running plugin without reloading.
- Examples. First-party example plugins ship across tiers, each tied to a published result: Standard (damped oscillator, double pendulum, GeoNum cancellation); Pro (Blasius boundary layer, H2 binding curve, 2D Ising, 1D Schrodinger, 2D standing wave, Taylor-Green decay); HPC (3D Euler Taylor-Green on CPU and GPU, FDTD Maxwell, Mercury precession, ideal-MHD HLLD, multigrid Poisson, 5D third-law violation).
One HPC example to try: Euler3D GPU Taylor-Green runs a WebGPU compressible-Euler solver and checks its GPU output against the CPU path on the Taylor-Green vortex, up to 128^3 in-browser (a full default run is about 40 seconds and reports a GeoNum Exact verdict). As with every engine, this is browser-side pre-cluster prototyping with honest runtime notes, not an HPC replacement.
Share links (kiosk view)
A share link opens the app directly into one target - a single view, engine, module, or plugin - in read-only kiosk mode. Anyone with the link (no login) sees that one target with its inputs locked to a frozen snapshot: only Run works, and any other action routes to Register. Access is live-gated, so if the link is revoked the page locks.
Visitors land in kiosk mode by opening a URL of the form ...?share={token}. Minting share links is an account action, but the kiosk view is what a trial-curious visitor sees first, so a shared result is a no-login way to show exactly one run.
Beyond running engines
Two workspace features sit alongside the physics modules:
- Sandbox - a saved workspace over the stateless engines: named parameter sets, a history of your own runs, and shareable experiments. Included on Pro and HPC, or available as an add-on. See Sandbox.
- Worklog - a separate per-seat case-management app with workflows, forms, checklists, queues, in-app roles, and (on HPC) engine-bound automations. See Worklog.
Next steps
- Run Plasma -> Equilibrium (Soloviev) with ITER inputs. Verify I_p is about 14.2 MA and β_N about 1.42, and read the GeoNum trust verdict badge on the result.
- Run Plasma -> Validation Suite -> ITER baseline. Verify the figure of merit matches the cited paper and the row is green.
- Open the Plugins catalog from any tier nav link and run an example plugin - for instance Standard -> Damped oscillator or HPC -> Euler3D GPU Taylor-Green.
- On any HPC engine panel, open the dev-log and bug-log buttons. The dev log records how the engine was built and validated against published references; the bug log lists real defects the validation gates caught, or a single honest "No defects surfaced" entry.
- Open Help & Support from the user menu (top-right, click your name), or the floating Help button. The Ask tab files a ticket auto-filled with your current module, view, and last result; My Tickets tracks replies; Knowledge Base holds the markdown guides.