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

Stochastic placement of cells (for TRISO fuels) #324

Closed
smharper opened this issue Sep 29, 2014 · 4 comments
Closed

Stochastic placement of cells (for TRISO fuels) #324

smharper opened this issue Sep 29, 2014 · 4 comments

Comments

@smharper
Copy link
Contributor

I'm working on a random geometry feature similar to what is described in LA-UR-04-8668 for MCNP. It is mostly finished, but I will wait on the PR until #313 is closed because it makes this feature much easier to implement.

@paulromano
Copy link
Contributor

Thanks @smharper. Once the 0.6.1 release is wrapped up, I'll start reviewing your hex lattice PR and this one as well.

@smharper
Copy link
Contributor Author

This issue has gotten a little stale, and I think I would like to close it, un-resolved as it is. I implemented the algorithm, but I don't think it is worth merging in. It adds a lot of code and input bloat, and it also didn't provide a very random placement for the packing fractions we were interested in.

I think the superior way to model TRISO reactors is to make a script that automatically generates geometry.xml files with TRISOs explicitly placed in their positions. I was much happier with the results from that approach. I don't think it's appropriate to include such a script in the OpenMC repo (except maybe as an example?). So, yeah. I'm closing this.

@wbinventor
Copy link
Contributor

Make it an example IPython Notebook!

On Tue, Aug 11, 2015 at 11:15 PM, Sterling Harper notifications@github.com
wrote:

This issue has gotten a little stale, and I think I would like to close
it, un-resolved as it is. I implemented the algorithm, but I don't think it
is worth merging in. It adds a lot of code and input bloat, and it also
didn't provide a very random placement for the packing fractions we were
interested in.

I think the superior way to model TRISO reactors is to make a script that
automatically generates geometry.xml files with TRISOs explicitly placed in
their positions. I was much happier with the results from that approach. I
don't think it's appropriate to include such a script in the OpenMC repo
(except maybe as an example?). So, yeah. I'm closing this.


Reply to this email directly or view it on GitHub
#324 (comment).

Will Boyd
Nuclear Science & Engineering
Massachusetts Institute of Technology
Cell: 423.413.8469
wbinventor@gmail.com

@paulromano
Copy link
Contributor

That would be a great example that we could point people to!

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

No branches or pull requests

3 participants