-
Notifications
You must be signed in to change notification settings - Fork 40
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
New features or new archetype repo? #585
Comments
One thing I regularly need is facility parameters that change over time, e.g., an enrichment facility that increases its SWUs at a given point or switches from natural U to LEU as feed material. I have implemented this but would also be willing to include it in another repo with, say, advanced archetypes. Or discuss with you if there's a smart way to integrate it into existing Cycamore archetypes |
There was an effort to do exactly this with recycle https://github.com/cyclus/recycle, which obviously didn't take off. Perhaps something we can look into for the hackathon |
Thanks @jbae11 - I couldn't remember the name we chose or find this repo... I knew there was something... |
Another new feature to think about is multiple regions in a core, like the driver and blanket in an SFR. Have a reactor archetype that can account for requesting both of those. |
Extra material output (Best way - implement as toolkit) Something like:
and it will just create the material and offer to the DRE? |
Another topic: I put OpenMCyclus into a repo owned by ARFC, but should we transfer it into Cyclus? Also for @dean-krueger's work, deciding the best place to host some of the already-developed archetypes. |
From @jbae11: accounting for non-equilibrium core. Like in an LWR, using fuel initially at a lower enrichment and having fuel go through fewer cycles. Maybe define batch-specific information, or base it on time. Looking to get more accurate spent fuel compositions and prevent overestimating of other resources (like enrichment) when starting up a new reactor. |
In the slack channel we have started some conversations about potential new archetype features, and whether these new features should be added to Cycamore or if it's better to create a new archetype library. Some of the points of this discussion include:
The text was updated successfully, but these errors were encountered: