Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O
openmc
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Shikhar Kumar
  • openmc
  • Issues
  • #1237

Closed
Open
Opened May 23, 2019 by Shikhar Kumar@shikhark
  • Report abuse
  • New issue
Report abuse New issue

Account for capture branching ratios in depletion chains

Created by: paulromano

This is mentioned in #977 and was originally discussed here, but I thought it deserves its own issue. The depletion chains that we have generated so far (full ENDF/B-VII.1, CASL chain) don't have any capture branching ratios. This leads to wrong isotopic concentrations for higher actinides (since we miss Am241 and Am243 capture branching) as well as Ag110m.

Upon looking at our deplete module, there is nothing that inherently stops us from having multiple <reaction>s with the same type but different targets. In fact, we already have the data structures set up to take a branching ratio on a reaction.

The main questions are:

  • What branching ratios to use? For starters, we can use the values that Serpent uses. These were computed in a typical LWR spectrum, but generally the spectral effects will probably be small.
  • In a reduced chain (e.g., our CASL 255 nuclide chain), what should we do when the metastable product from capture is not in the chain already? The easiest thing to do is to just have it still go to ground, but this will definitely be wrong in some cases. To be more accurate, we should really look at the decay files for the missing product to see what would have happened and adjust the target accordingly.
Assignee
Assign to
v0.11
Milestone
v0.11
Assign milestone
Time tracking
None
Due date
None
2
Labels
Data Depletion
Assign labels
  • View project labels
Reference: shikhark/openmc#1237