MATPOWER / MATPOWER/most

eliminate min up/down time constraints for units with min up/down = 1

Open
#18 1 comment 0 reactions 1 assignee View on GitHub

@rdzman is already working on this.

Since Sep 24, 2020.

enhancement
Dominant language
MATLAB
Stars
40
Forks
15
PR merge metrics
No merged PRs in 30d

Description

From https://www.mail-archive.com/matpower-l@cornell.edu/msg06940.html ...

It looks like this would be a good place for some optimization of the code. I believe it’s true that the min up and down time constraints are essentially unnecessary when the min up and down time values are 1. It seems to me that the only difference is that it becomes feasible to have a startup and shutdown event (v = w = 1) for a given unit at a given period, resulting in no change in state. However, this should have no impact unless the startup and shutdown costs are non-zero, in which case that solution would not be optimal. So, I believe, simply eliminating these constraints when the min up/down times are 1 should result in an equivalent optimization problem.

To optimize this code to handle the general case more efficiently for large systems, it seems like maybe we should be indexing these constraints by (t, tau) instead of (t, i).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.