cyclus / cyclus/cyclus.github.com
mod cep20 to discuss decommission convention
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
See discussion here: https://groups.google.com/d/msg/cyclus-dev/jt29aJGkIdM/QqWpRpsIgvgJ
The related PRs addressing this are cyclus/cycamore#300 and cyclus/cyclus#1085.
Something along the lines of:
By convention, decommissioning should be treated as occurring at the end of a time step.
So an agent with lifetime 1 would be decommissioned on the same time step it was built.
The lifetime of an agent can be back calculated by `1+exit_time-start_time`.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Google Groups discussion and the related cyclus/cycamore#300 and cyclus/cyclus#1085 pull requests. Update the CEP20 documentation to state the decommissioning convention and lifetime calculation shown in the issue, then verify the wording matches the settled convention.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100