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

New features or new archetype repo? #585

Open
abachma2 opened this issue Feb 28, 2024 · 7 comments
Open

New features or new archetype repo? #585

abachma2 opened this issue Feb 28, 2024 · 7 comments
Labels
Feature Infrastructure: Packaging Related to different ways to package for simpler installation

Comments

@abachma2
Copy link
Member

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:

  • fuel type caps for a reactor (e.g., 10% of fresh fuel can be MOX, the other 90% have to be UOX)
  • Place for Pyre -- AFRC archetype for pyroprocessing, aimed at safeguards applications (could maybe argue OpenMCyclus for this too).
@abachma2 abachma2 added Infrastructure: Packaging Related to different ways to package for simpler installation Feature labels Feb 28, 2024
@maxschalz
Copy link
Contributor

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

@jbae11
Copy link
Contributor

jbae11 commented Mar 5, 2024

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

@gonuke
Copy link
Member

gonuke commented Mar 6, 2024

Thanks @jbae11 - I couldn't remember the name we chose or find this repo... I knew there was something...

@abachma2
Copy link
Member Author

abachma2 commented Mar 8, 2024

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.

@jbae11
Copy link
Contributor

jbae11 commented Mar 8, 2024

Extra material output (Best way - implement as toolkit)

Something like:

<misc_waste_commodity>
  <val>contam_water</val>
  <val>tritium_gas</val>
</misc_waste_commodity>
<misc_waste_cycle>
  <val>4</val>
  <val>5</val>
</misc_waste_cycle>
<misc_waste_mass>
  <val>100</val>
  <val>1</val>
</misc_waste_mass>
<misc_waste_recipe>
  <val>h2o_contaminated</val>
  <val>h3</val>
</misc_waste_mass>

and it will just create the material and offer to the DRE?

@abachma2
Copy link
Member Author

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.

@abachma2
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Infrastructure: Packaging Related to different ways to package for simpler installation
Projects
None yet
Development

No branches or pull requests

4 participants