I assumed you were talking only about the single-period OPF problem, in which 
case the best you could do would be to attempt RATE_A and if that proves 
infeasible, switch to RATE_B, and so on. The time profile using apply_proflie() 
could be used in the context of MOST (limited to DC network model) if you know 
beforehand which time periods you will be relaxing the limits.

   Ray


> On Sep 12, 2017, at 7:56 AM, Katarina Knezović <[email protected]> wrote:
> 
> Dear Ray, 
> 
> Thank you for the fast reply. As suggested, I will submit this change as an 
> issue on GitHub.
> However, what I had in mind was not only including rate B instead of rate A 
> in OPF, but to include rate B in addition to rate A. More precisely, I am 
> investigating if MP could be used for dynamic line rating where a higher 
> branch limit could be imposed for a short time (emergency rating for e.g., 
> one time instance).
> Since this is not possible, I assume the best approach would be to define a 
> time profile for the branch limit via apply_profile function. Do you think 
> there is another possibility?
> 
> Thank you, 
> Katarina
> 
> 
> On 11 September 2017 at 22:37, Ray Zimmerman <[email protected] 
> <mailto:[email protected]>> wrote:
> Rates B and C are in the data file format, but there is currently no 
> automated way to run an OPF using, for example Rate B instead of Rate A. 
> However, this is trivial to do with a couple of lines of code …
> 
> define_constants;
> mpc = loadcase(<my case file>);
> mpc.branch(:, RATE_A) = mpc.branch(:, RATE_B);
> results = runopf(mpc);
> 
> I have it on a “to do” list somewhere to add an OPF option to handle this 
> automatically, but it’s not yet implemented and I don’t have a timeline for 
> it. May I suggest that you submit this in the issue tracker on GitHub and 
> maybe someone (yourself?) will contribute a pull request to implement it.
> 
>    Ray
> 
> 
>   
> 
> 
>> On Sep 11, 2017, at 8:34 AM, Katarina Knezović <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Dear MatPower developers, 
>> 
>> As far as I understand, the current MatPower version includes only branch 
>> rate A for OPF.
>> Is there a plan to also include rates B and C, and if yes, is there an 
>> estimated timeline?
>> 
>> Thank you in advance, 
>> Katarina
> 
> 

Reply via email to