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
  • Merge Requests
  • !763

Merged
Opened Nov 28, 2016 by Shikhar Kumar@shikhark
  • Report abuse
Report abuse

Track Density-Weighted Average MGXS

  • Overview 4
  • Commits 2
  • Changes 6

Created by: wbinventor

This PR is a re-opened version of #732. This PR fixes an issue in the MGXS.get_subdomain_avg_xs(...) method, among a few other minor bug fixes. Currently, this method will take the geometric average of the MGXS for a bunch of distribcells or mesh cells. However, the geometric average does not preserve global reactivity.

Instead, a track density-weighted (TD-weighted) average MGXS should be computed. Fortunately, this is as simple as substituting Tally.summation(...) for Tally.average(...) in the get_subdomain_avg_xs(...) method. In effect, this computes the average MGXS from tally sums which are equivalent to what one would obtain if an explicit cell or material tally were specified for the subdomains of interest. And as my thesis broadly confirms, the TD-weighted average MGXS does indeed preserve global reactivity.

I made these changes a few months ago, and ran into some issues when merging with the develop branch earlier today due to #723 and #725. As a result, this PR is likely not ready for merging - I'm not yet sure I've fixed all of the issues. I haven't been able to run my scripts which use TD-weighted MGXS since something with the new MeshFilter is breaking when loading from a statepoint. I'll post here again once I have a chance to sort that out.

Assignee
Assign to
v0.9
Milestone
v0.9
Assign milestone
Time tracking
3
Labels
Bugs MGXS Python API
Assign labels
  • View project labels
Reference: shikhark/openmc!763