Open scientific software / BNCT

OpenBNCT

BNCT transport
and dose analysis.

Open-source software for boron neutron capture therapy research. Prepare geometry, run or import transport calculations, and compare dose components using separately versioned biological models.

MIT · Browser, desktop, CLI & Python

PHYSICAL DOSE COMPONENTS
BORON / PHYSICAL DOSE

The boron-capture contribution to physical dose. Biological weighting is a separate step.

Physical dose stays distinct from biological interpretation.
Conceptual illustration, not a dose map.

OpenBNCT 0.2.2 is the current published release. The handbook describes newer current-source workflows; check release notes before following a command that may postdate the packaged version.

Downloads and release notes Source on GitHub Benchmark guide

From geometry to dose analysis

OpenBNCT records physical dose components separately from assumptions about boron distribution and biological response. Researchers can compare each component and trace it to the input data.

  1. Define the case.Import DICOM geometry, establish materials and sources, and preserve coordinate systems, units, and input identities.
  2. Run or import transport.Use desktop or CLI workflows to prepare and run an OpenMC case, or import external results. The browser workbench is for supported local viewing and analysis.
  3. Inspect physical dose.Review boron, nitrogen, hydrogen, and photon components with voxel uncertainty and region-level metrics.
  4. Evaluate the interpretation.Apply separately versioned biological models and sensitivity scenarios. Results retain their model assumptions and research qualification.

Available capabilities

The browser workbench opens bundled examples and supported dose files for local viewing and analysis. Files remain in the browser. Case folders and external process execution require desktop or CLI.

Transport & component dose

Current source supports deterministic transport, OpenMC workflows, and versioned physical-dose records with component results and uncertainty.

Images & regions

DICOM and NIfTI workflows support image geometry, region operations, and dose inspection. Browser operations are described in the handbook.

Metrics & model studies

Dose-volume metrics, biological models, timing, uncertainty, and plan studies retain their assumptions and research scope.

Interchange & comparison

MCNP and PHITS adapters and comparison records support research interchange. Format fixtures do not establish agreement on real-engine cases.

These are research capabilities; external validation and roadmap work remain incomplete. The usage guide documents current source interfaces. The handbook distinguishes current-source workflows from packaged releases.

NF-BNCT-001 benchmark results

NF-BNCT-001 is a frozen synthetic case with declared geometry, materials, source, and acceptance criteria. Three OpenMC runs at 600 million histories per seed passed the case’s predeclared statistical gates.

3 × 600Mhistories across frozen seeds
≈ 2.7%photon median relative standard error
291 + 378estimator comparisons + seed-consistency checks

The earlier 300-million-history evaluation missed the photon voxel-precision gate. That report remains published alongside the later passing result. Increasing particle histories followed the benchmark’s declared protocol; the gate was not relaxed.

Remaining validation work

  1. Independent transport reproduction.The frozen case still needs reproduction through a separate transport implementation, such as Geant4 or licensed MCNP/PHITS operated by a licensed user.
  2. Real-engine adapter acceptance.MCNP and PHITS importers have documented-format conformance fixtures. Those checks do not establish agreement on real-engine cases.
  3. External research validation.Broader applicability, end-to-end workflow coverage, and reproduction by other researchers remain active work. Implemented biological functions are research models, not validated clinical predictions.

OpenBNCT is not a medical device and does not establish clinical equivalence or regulatory suitability. Read the use boundary.

Get started

Choose the browser workbench to inspect bundled examples and supported local files, or use desktop, CLI, or Python workflows for broader research tasks.

Formerly NCTForge. The CLI and Python package still use nctforge; internal crate and schema names retain that namespace. Existing links to the former website address redirect here.

Working on an independent comparison?

Contact us to discuss reproducing a benchmark, testing an adapter, or comparing transport codes.

Discuss your research