Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect reaction rates reported for assemblies with symmetry factors!=1 #2059

Open
bsculac opened this issue Jan 21, 2025 · 2 comments · May be fixed by #2068
Open

Incorrect reaction rates reported for assemblies with symmetry factors!=1 #2059

bsculac opened this issue Jan 21, 2025 · 2 comments · May be fixed by #2068
Labels
bug Something is wrong: Highest Priority complex Expected to be a complex issue

Comments

@bsculac
Copy link
Contributor

bsculac commented Jan 21, 2025

Incorrect reaction rates are reported for assemblies with symmetry factors. This is caused by components' volumes being reported at full value even when a block is partially outside the core. This effects the calculation of the integrated multigroup flux at either:

volumeFraction = self.getVolume() / self.parent.getVolume()

or

return pinFluxes[self.p.pinNum - 1] * self.getVolume()

Related discussion discusses some approaches to solving this issue. While it would be semi-nonphysical, reducing the calculated component volume by the symmetry factor of the parent objects like what is done here would likely solve the issue:

volume = self.getVolume() / (
self.parent.getSymmetryFactor() if self.parent else 1.0
)

@bsculac bsculac added bug Something is wrong: Highest Priority complex Expected to be a complex issue labels Jan 21, 2025
@mgjarrett mgjarrett linked a pull request Jan 31, 2025 that will close this issue
7 tasks
@john-science
Copy link
Member

@bsculac So, I had trouble following your question in that the lines you were pointing to were no longer valid.

So, on GitHub, you can technically point to any line of code as you originally did:

https://github.com/terrapower/armi/blob/main/armi/reactor/components/component.py#L1244

But that points to a line in the main branch. And since you opened this ticket, that exact line number changed 5 times. So, on GitHub, we can navigate to an exact commit and put a reference in like this:

https://github.com/terrapower/armi/blob/471e9e247f0bcb113611596c358ba43c603fdca2/armi/reactor/components/component.py#L1244

And the benefit there is that it will actually render as the line of code you want to point to visibly, and as long as that commit isn't deleted (unlikely on a main branch), then it can never go stale:

volumeFraction = self.getVolume() / self.parent.getVolume()

Anyway. I tried to revive the lines you were referencing. Can you look and see if I got it right?

Thanks!

@bsculac
Copy link
Contributor Author

bsculac commented Feb 7, 2025

I think that's correct, I am not sure what the original lines were but I think the meaning is captured!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is wrong: Highest Priority complex Expected to be a complex issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants