Skip to content

Conversation

@ChasingNeutrons
Copy link
Collaborator

Maybe people will disagree with this...

I thought it might be appropriate to rename densityResponse to become invSpeedResponse. This is because, to me, it feels more natural to name the response what it is, rather than what it results in the tally being. Maybe we aren't fully consistent with this, e.g., fluxResponse.

I feel invSpeed is a bit more clear to someone reading rather than density, which is a bit more ambiguous in transport.

Finally, tallying 1/v weighted by flux is something one might do when computing kinetic parameters, so the response is a bit more general than producing a density.

If you disagree, let's fight!

Added in the BEAVRS model with the D-bank partially inserted. Also fixed
a flaw in the geometry where the outermost cell was defined such that
there could be a rare particle lost between it and the geometry
boundary.
Changed to invSpeed, i.e., what the response is, rather than what it
allows one to tally. Partly done because 1/v is useful in kinetic
calculations.
Copy link
Member

@valeriaRaffuzzi valeriaRaffuzzi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine by me!

@valeriaRaffuzzi valeriaRaffuzzi merged commit 7f6f122 into CambridgeNuclear:main Jul 9, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants