Skip to content

CEP 30 - Improvements to Cyclus Supply-Demand Framework #396

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

Open
wants to merge 10 commits into
base: source
Choose a base branch
from

Conversation

dean-krueger
Copy link
Contributor

After gathering informal community feedback, this is a more formal first draft of an official CEP on the website. I made sure it all displays correctly on a local spinup of the website I tested following the instructions in the README.

@dean-krueger dean-krueger requested a review from gonuke December 30, 2024 04:00
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.

A few editorial changes as well as some clarifications.

*********************************************************

:CEP: 30
:Title: Improvements to Cyclus Supply-Demand Framework
Copy link
Member

Choose a reason for hiding this comment

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

This title is vague and all-encompassing.

This CEP should be targeted at sharing financial parameters between the R-I-F hierarchy, and the title should be clear at this more narrow scope.

add economic information to archetypes themselves at the beginning of simulations. This was tested,
but it was discovered that there were problems accessing the information of parent agents, and it
was determined that this approach would be some combination of too cumbersome and less certain to
work. The second idea was to implement some sort of registry, similar to how Microsoft Windows
Copy link
Member

Choose a reason for hiding this comment

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

Not sure we need to focus on MS Windows as the model here.

This is also probably in addition to the Toolkit/code injection, but the code injection would include a facility for archetypes to register their ability to respond to financial requests in some globally accessible place.

@dean-krueger dean-krueger requested a review from gonuke February 6, 2025 16:46
Copy link
Member

@katyhuff katyhuff left a comment

Choose a reason for hiding this comment

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

This seems like an improvement to me if backwards compatibility is indeed maintained.

Plenty of explanation in the docs would be great. Even better would be PRs to repos
that include the kinds of archetypes that might benefit from using this feature.

Copy link
Member

@abachma2 abachma2 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 writing up this CEP, @dean-krueger. This all seems reasonable to me, Looking at some of the other CEPs (and I'm not very familiar with this process so we may not be there yet), it looks like they have sections about documentation and specification & implementation. Would those come after this CEP has been accepted and completed?

Looking through CEP 1 some, I believe this would be a standards CEP.

The CEP 0 page of the website should also be updated to link to this file, so this CEP is easily found.

@gonuke
Copy link
Member

gonuke commented Feb 19, 2025

We haven't exercised this process in a long time @abachma2, so I think things are a little open to reinvention. It's perhaps a little complicated in that there is nominally a process of review after a draft has been published, but publishing a draft is also subject to a PR review here on GH. I think the idea is for the first published draft to be fairly well-formed so that the outside-github review of that (mailing list?) can be based on the substance and not in the weeds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants