Skip to content

Current Project Evidence

This page is the sole documentation owner of volatile Project evidence and current application mismatches that affect Project work. A claim that could become stale after a Project-record mutation or relevant source change belongs here; research pages link here instead of copying it. Stable decisions, methods, interpretation, and dated history remain with their subject owners.

Immutable Project records establish what was executed. Deterministic simulation-evidence.json is the machine authority for counts, execution metadata, field values, hotspots, particle-page statistics, and RSE distributions. This page is the reviewed human-readable summary of those sources, not independent evidence.

Current inventory

NATIVE GUI OBSERVATION — 2026-09-24: The Project library contained Application Verification and Composer Verification, but no Paper 1 Project. Created and opened Industrial EB/X-ray Dose Prediction; the GUI assigned Project ID industrial-eb-x-ray-dose-prediction and showed 0 editable Designs. The two verification Projects were left untouched.

The GUI library now contains three Projects. The Paper 1 Project has zero Designs and no Calculation was created during this inspection. The two existing verification Projects have their own scientific records; this inspection did not enumerate all of their child records. The former zero-record inventory was a historical reset snapshot, not the current state. No Paper 1 Result or accepted simulation evidence was observed.

Current application capability and mismatches

VERIFIED EVIDENCE: Current executable source implements GUI mechanisms for Design and Case authoring, Job and Attempt execution, Result inspection, Study and Assessment records, Dataset construction with declared whole-configuration partitions, finalized Models, explicit final-test evaluation, Predictions, and Prediction Verification. The current trainer provides reduced-order baselines for scalar continuous or binary features and per-source-electron fields on one exact grid. Capability does not establish scientific acceptance or completed Project evidence.

VERIFIED EVIDENCE: The current Dataset builder requires the declared-whole-configuration method, a positive split seed, and train, validation, and final-test membership. When an optional binary paired feature is declared, it requires both categories in the same split and checks complete paired groups. D10 grouping keys, paired conditions, proportions, seed, and stratification remain unresolved.

VERIFIED EVIDENCE: Current source authoring can round-trip a one-dimensional scanned source, emit repeated PHITS s-type=13 source subsections, apply normalized trapezoidal weights, require an odd number of positions, refine the scan by halving centre spacing, preview declared centres and support, and validate finite restriction-cell bounds. The implemented scan profile is uniform. The support diameter is a RAMAL preview and validation extent, not a native Gaussian hard cutoff; these capabilities do not approve D5 details.

IMPLEMENTATION-DOC MISMATCH: Study_Inclusion_Criteria stores only max_relative_error, min_reportable_fraction, and min_reportable_voxel_count; the editor preloads 0.10, 0.95, and 1. These editable implementation defaults are not approved D7 values, and the schema does not represent the complete intended inclusion procedure. A Paper 1 Study must not qualify until the approved method can be represented and assessed through the GUI.

NATIVE GUI OBSERVATION — 2026-09-24: Local PHITS (local-phits) was enabled and labelled Ready, local, declared version 3.360, with executable /Users/faiz/phits/bin/phits.sh, process count 1, and PHITS 3.x report completion adapter. This is profile configuration/readiness, not proof of a Paper 1 transport run.

BLOCKER — provenance: The research derivation record explicitly gates the first preliminary Calculation on retaining original raw water and custom-SS304 ESTAR outputs, full-precision reference scales and centimetre operands in Project provenance. The reviewed research page contains approximate 3.7875 and 4.7648 g cm^-2 scales and rounded millimetre labels, not those raw outputs or full-precision operands; no ESTAR file was found in the repository references. The newly created Project has no Design. Do not reconstruct exact inputs from rounded labels, substitute a synthetic source, or launch the scientific Calculation until the original derivation can be recovered and reviewed.

Strictly qualified conclusions

  • NATIVE GUI OBSERVATION: The Paper 1 Project exists under the approved current-format identity with zero Designs at inspection; the two verification Projects remain separate.
  • The former preliminary D4 Design is historical documentation, not current authoring state or evidence.
  • Paper 1 has no observed simulation Result and no accepted simulation evidence.
  • There is no current numerical observation from which to infer transport completion, convergence, verification, validation, uncertainty, shielding adequacy, Dataset eligibility, surrogate accuracy, or regulatory compliance.
  • Successful execution, transport completion, convergence, verification, validation, quantified uncertainty, owner acceptance, Assessment, and Dataset inclusion remain separate statuses as defined in Methods, Verification, and Validation.

Current next action

Recover and retain the original raw ESTAR derivation and full-precision operands in the Paper 1 Project first. Then author and independently verify the centre input and native tallies; only after exact frozen-input and dependency review should the enabled local profile be used for the one short-history 7.5 MeV Preliminary Calculation. Issue #8 remains open; this Project creation and profile inspection do not satisfy execution or Analyze acceptance.