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
committable generator constraint fails when min_up_time exceeds length of snapshots #124
Comments
Hey, I would not directly claim it a bug. The error comes from having a network with one snapshot while ramp limits are given. This collides in the lopf. I think it makes sense to make an assertion for this case. Can you please test it for more than the one snapshot? |
Thanks for your help. I will test it. One adicional question please. When you run a linear OPF given n snapshots, you are running n independent optimizers or it is just one in the whole space of the snapshots? |
|
Thanks for your feedback. I tested my grid with more than one snapshots but I am having same issue. Any other clue? |
weird... can you send the network (with multiple snapshots now) again? |
Here you have it again.. Am I doing something wrong when I model my grid? .... Thanks for your support. |
I was running some other tests and I found the variable which is causing problems are |
Actually, the min_up_time for some of your generators is longer than the number of snapshots:
This fails at a specific point in the assignments of the constraints. Can you clip your min_up_time to the length of snapshots. Like this
|
It fix my problem... Thanks a lot |
Keeping it open as this case should be caught in the code. Cf. ongoing pull request #128. |
Checklist
master
branch or the latest release. Please indicate:Describe the Bug
When I try to run a OPF using the network folder attached below I got the following error:
May I know what's missing in my network or any clue relating the error I am getting?
Thanks for your help.
The text was updated successfully, but these errors were encountered: