Sienna-Platform / Sienna-Platform/PowerOperationsModels.jl
NonSpinningReserve: using minimum up time as startup time
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 2
- Forks
- 1
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 26
Description
If this is a question, something isn't working or an idea please start a Q&A discussion in the Discussion tab
Open a bug report only if you can provide the details below
Describe the bug
service_models/reserves.jl line#469, startup_time = PSY.get_time_limits(d).up.
The PSY.get_time_limits(d).up seem to give the minimum up time, and the startup time should be a different parameter?
To Reproduce
service_models/reserves.jl line#469, startup_time = PSY.get_time_limits(d).up.
Expected behavior
startup time would be a individual parameter.
If this startup time is considered, this parameter seem to drive the unit commitment problem as well. If the commitment is made at t, the unit will be on at t+startup time
Screenshots
Additional context
Add any other context about the problem here.
Contributor guide
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 at service_models/reserves.jl line 469 and inspect how PSY.get_time_limits(d).up is used for startup_time. Compare that value with the expected distinct startup-time behavior and how commitment timing is affected; the issue is done when minimum up time no longer incorrectly supplies startup time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100