SCONE Guide

❮ SourcesSettings ❯

SCONE Verification Notice

SCONE is a research-oriented code with a smaller user base than MCNP, OpenMC, or SERPENT. Our examples are intended as educational guidance. For authoritative syntax, physics options, and nuclear data requirements, consult the official documentation.

Official SCONE documentationSCONE on GitHubIssues & discussions

Tallies in SCONE

Mapped Scoring and Reaction Response

Core Pattern

Your working deck uses `activeTally` blocks with clerk/response definitions and spatial maps. This should be the reference format for ReactorMC SCONE examples.

plaintext
activeTally {
  fissionRate {
    type collisionClerk;
    response (fission);
    fission { type macroResponse; MT -6; }
    map {
      type multiMap;
      maps (xax yax);
      xax { type spaceMap; axis x; grid lin; N 255; min -161.2773; max 161.2773; }
      yax { type spaceMap; axis y; grid lin; N 255; min -161.2773; max 161.2773; }
    }
  }
}

Reaction-Targeted Scoring

Response blocks can be specialized by reaction target (for example MT 102 capture-like scoring).

plaintext
activeTally {
  captureLikeScore {
    type collisionClerk;
    response (capture);
    capture { type macroResponse; MT 102; }
    map {
      type multiMap;
      maps (xax yax);
      xax { type spaceMap; axis x; grid lin; N 128; min -161.2773; max 161.2773; }
      yax { type spaceMap; axis y; grid lin; N 128; min -161.2773; max 161.2773; }
    }
  }
}

Resolution Strategy

Use lower mesh resolution for debug runs and increase map resolution for production diagnostics.

plaintext
! Spatial map concept used in your deck:
map {
  type multiMap;
  maps (xax yax);
  xax { type spaceMap; axis x; grid lin; N 255; min -161.2773; max 161.2773; }
  yax { type spaceMap; axis y; grid lin; N 255; min -161.2773; max 161.2773; }
}

! Use smaller N for quick debug and larger N for production-quality maps.

Related Topics

❮ SourcesSettings ❯