Add ramp up/down cost (penalty on dispatch change between snapshots)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 699
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 13
Description
PyPSA can limit how fast a component changes its output between snapshots (ramp_limit_up / ramp_limit_down), but it cannot put a cost on ramping. There is no objective term that penalizes the change in dispatch |p_t - p_{t-1}|. To cover this we can add and integrate cost attributes ramp_up_cost/ramp_down_cost for all ramping supporting components.
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 by tracing the existing handling of ramp_limit_up and ramp_limit_down, then follow how dispatch changes and objective terms are assembled for each ramping-supporting component. The work is done when ramp_up_cost and ramp_down_cost are integrated for all such components and tests verify the resulting penalty on |p_t - p_{t-1}|.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100