Skip to content

Commit cf897dd

Browse files
authored
Merge pull request #65 from nsryan2/thesis_reactors
Add dynamic power reactor
2 parents 634b9ff + 136d185 commit cf897dd

7 files changed

+1892
-3
lines changed

.gitignore

+2
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1+
*.DS_Store
2+
13
## Core latex/pdflatex auxiliary files:
24
*.aux
35
*.lof

CHANGELOG.md

+1
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ Includes New Features, Enhancements, and Bug Fixes.
99
* EVER low fidelity recipe update (#7, #17, #33)
1010
* Install script (#23, #24)
1111
* Start CLOVER (#8, #16)
12+
* Create DPR (#65)
1213

1314
### Documentation
1415

DPR/README.md

+31
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Dynamic Power Reactor (DPR)
2+
DPR is a Cyclus reactor archetype based on Cycamore's Reactor, except that it has the ability to update the power output over time.
3+
4+
## Cite this work
5+
Pending...
6+
7+
## power_percent_list
8+
Outside of refueling, the power output of the reactor can be modified by a percentage in the Tock phase of each time step. This feature is optional, and will default to 100% of the power_cap variable the user identifies. At each time step, the reactor will progress through the percentages; as such, there must be a percentage for each time step (if the length of the power_percent_list is shorter than the number of time steps, the reactor will default to 100%).
9+
10+
To simulate 10 time steps, a user could provide a list like:
11+
```
12+
<power_percent_list>
13+
<val>0.3</val>
14+
<val>1</val>
15+
<val>1</val>
16+
<val>1</val>
17+
<val>1</val>
18+
<val>1</val>
19+
<val>0.9</val>
20+
<val>0.5</val>
21+
<val>1</val>
22+
<val>1</val>
23+
</power_percent_list>
24+
```
25+
If the simulation was extended to 11 time steps with out the list changing, the 11th time step would have a power output of 1 (or 100%).
26+
27+
> [!Important]
28+
> When the reactor is refueling, the power output will be overwritten to 0, so
29+
> we recommend that you ensure your outages align with when the reactor goes
30+
> into outage if you are modeling a historical example.
31+

0 commit comments

Comments
 (0)