A geometry-first desktop workspace
FARIS uses a Rust model, engine, command-line client, and native desktop app. The demonstration scenario shows an ARC-inspired compact D-T tokamak with two blanket and shield arrangements in a shared 3D scene.
The app supports component selection and inspection, orbit and zoom, visibility controls, cutaway display, and arrangement switching. The cutaway changes only the view; geometry records and reported volumes remain based on the full torus.
The current starting scenario has unassigned materials. Its idealized circular tori and magnet envelope do not reproduce the published ARC engineering design.
An explicit cold-reference transport path
Beyond the default geometry preview, FARIS has a local workflow for an explicitly configured cold-data surrogate using OpenMC. It can report component tritium production, neutron flux, energy spectra, and a three-dimensional Cartesian flux mesh for that scoped setup.
The workflow runs on the user’s machine with local OpenMC software and identified data inputs. FARIS also has an independently specified absorber-sphere control; a passing numerical control applies only to that declared control case and does not establish a reactor prediction.
A local Avila Core workflow can compile a generated study and save the compiler report. Compilation, run readiness, calculation, and scientific assessment are separate steps.
What the demo does not model
Scientific qualification remains NOT_EVALUATED, including for completed transport runs.
Activation, ageing, fuel inventory, maintenance, and power production are not implemented. The timeline is prepared for future operating-history results but does not supply those results. FARIS is not a complete reactor simulator and has no browser build.
Source and run guide
The repository README includes desktop and CLI instructions, platform requirements, the cold-reference workflow, and the project roadmap. Building the native app requires the pinned Rust toolchain; the transport workflow additionally requires local OpenMC and identified data files.
Read the source, current capabilities, workflow guides, and development roadmap.
Read the project license and notices for third-party software and data.
See required local inputs and the scoped transport procedure.