Skip to content

Conversation

@abachma2
Copy link
Member

Summary of Changes

This PR addresses some of the items identified by me in #427 to update the user tutorial. The changes are generally pretty minor: fixing typos, correcting formats, making things consistent across the tutorial. Some of the wording changes improve the clarity of the tutorial for me and I welcome discussion if you think the changes make things less clear.

Design Notes

Check the box if your change does not break any of the following:

  • API for Cyclus modules
  • Input files
  • Output tables for post processing tools

Related CEPs and Issues

This PR addresses some of the items in #427, but not all of them so the issue should remain open after merging.

Associated Developers

Testing and Validation

  • I have read the Contributing to Cyclus guide
  • I have compiled and run the code locally
  • I have added or updated relevant tests
  • I have added documentation for new or changed features
  • This code follows the style guide
  • I have updated the changelog

Reviewers, please refer to the Cyclus Guide for Reviewers.

@gonuke
Copy link
Member

gonuke commented Oct 29, 2025

See also #426

@abachma2
Copy link
Member Author

See also #426

I will add that to the Tutorial update project. I don't want to do that update with this PR to maintain some formal scope. I can get another PR in to address that issue.

Copy link
Member

@gonuke gonuke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this careful review @abachma2 . I have reviewed all your changes, but haven't done a full read to confirm that the changes are any more/less consistent with the tutorial - I'll trust you on that. There are a few places where I did look at the context of the changes and asked some questions.

</archetypes>
Once complete, append the archetypes section under the control section of input file [#f1]_.
The order of the archetypes in this block is of minor consequence. Once complete, append the archetypes section under the control section of input file [#f1]_.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I know what "minor consequence" means.... does the order matter at all?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I know, the only ordering that matters in a Cyclus input file is that the control block needs to go first. I don't know if there are any other things that matter. I can change minor to no if that is more accurate.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "no consequence" would be better

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Forgot to save that with my last round of edits. It is now changed.

Comment on lines +181 to +183
There can be multiple ``entry`` blocks within the same institution, hence the
``...`` in the block. Multiple entry blocks means that multiple prototypes
are deployed at the start of the simulation.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have ... in this example. I think we need to add that for this to make sense

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did add that in. Line 193.

<item>
<comp>_______</comp>
<eff>_______</eff>
<comp>[nuclide]</comp>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs to refer to an element??? or is that just a convention. Separations acts on elements not isotopes...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Elsewhere on the website I see that we have nuclide: https://fuelcycle.org/user/cycamoreagents.html#cycamore-separations. I don't actually know that answer.

Copy link
Member

@gonuke gonuke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have one minor comment and then ready to approve these.

That said, we had a discussion in my group meeting today about the high level design of the tutorials and may want to discuss that on the next Cyclus call, if not sooner.

<config>
<Archetype>
<outcommod>outcommod</outcommod>
<Source>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In all the other places that we describe "templates" we leave these as <Archetype> and then replace it later.

This has led to a different conversation about how verbose these tutorials are where we often:

  • give an example
  • give the template
  • give the filled in template that is often the same as the example

I don't expect this PR to fix that, but we should discuss the overall flow of the tutorials some time.

Comment on lines +138 to +139
* ``RegionArchetype``: name of the Region archetype you wish to use in your simulation, and the dotted line in this section represents any inputs that the archetype might have.

Copy link
Contributor

@dean-krueger dean-krueger Nov 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps a note that RegionArchetype isn't (currently, at least) a valid input in this block and that it must be replaced with the actual region name with an example like <NullRegion>. What you have implies this, but users new to Cyclus/XML may get tripped up by this.

</facility>
Append this prototype right after the ``1178MWe BRAIDWOOD_1`` prototype.
Append this prototype right after the ``1178MWe BRAIDWOOD_1`` prototype in your input file.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think in the last tutorial you changed 1178MWe BRAIDWOOD_1 to 1178MWe ReactorPlant Unit 1

</entry>
below the ``1178MWe BRAIDWOOD_1`` entry block. The Reactor section
below the ``1178MWe BRAIDWOOD_1`` entry block. The second institution section
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See above about 1178MWe ReactorPlant Unit 1 vs BRAIDWOOD

Copy link
Contributor

@dean-krueger dean-krueger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome work, this is a lot better for having been gone through like you did. I left two or three comments separately, but they're all pretty minor. Otherwise looks good to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants