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

add CapacityReserveMargin = 2 option that applies reserve constraint at peak load #807

Closed
wants to merge 61 commits into from

Conversation

NLaws
Copy link
Contributor

@NLaws NLaws commented Jan 4, 2025

No description provided.

lbonaldo and others added 30 commits August 21, 2024 09:29
Update develop branch with release v0.4.1 branch
Update PrecompileTools dep in Project.toml
simple_operation does not exist, so don't `export` it.
Abstract some of the extraction of values from the model to improve
readability.
* Fix typo in write_co2; 
* Fix init in reduce and mapreduce

---------

Co-authored-by: Jacob Schwartz <[email protected]>
Put all maintenance docs under `Model_Reference/Resources/Thermal/`

Remove a page under `Model_Reference/Resources` which was almost the
same thing; merge the differences.
Add optional fusion plant features to THERM resources. Optional features include pulse behavior, several kinds of parasitic (recirculating) power, variation of parasitic power during scheduled maintenance periods, a maximum annual power throughput limit, and a maximum annual pulse start limit.
Update Julia version requirements and recommendations
had to pull some output writing out of the block of "# Temporary! Suppress these outputs until we know that they are compatable with multi-stage modeling"
the separation gives greater clarity to what each solvers are doing as well as gets us a step closer to (perhaps) reducing the RAM impact of multistage models by only keeping as many models, inputs, and results in memory as necessary
this is what I do as I go through the code to understand it
NLaws and others added 28 commits January 4, 2025 11:53
just makes the module slow to start, have to pay the build cost anyway
had to pull some output writing out of the block of "# Temporary! Suppress these outputs until we know that they are compatable with multi-stage modeling"
the separation gives greater clarity to what each solvers are doing as well as gets us a step closer to (perhaps) reducing the RAM impact of multistage models by only keeping as many models, inputs, and results in memory as necessary
this is what I do as I go through the code to understand it
@NLaws
Copy link
Contributor Author

NLaws commented Jan 4, 2025

wrong repo

@NLaws NLaws closed this Jan 4, 2025
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.

6 participants