This is not a version 2 format. Version 2 format is a struct. You might try 
using savecase() to generate a valid version 2 case file. Then edit it with 
your own values.

-- 
Ray Zimmerman
Senior Research Associate
B30 Warren Hall, Cornell University, Ithaca, NY 14853
phone: (607) 255-9645





On Jun 20, 2013, at 3:34 AM, Cédric Josz <cedric.j...@gmail.com> wrote:

> Hello Ray :
>  
> I don't seem to be able to resolve the issue on my own so here is an M-file 
> containing the data.
>  
> Thanks a lot for your help.
>  
> Enjoy your break.
> Cédric
> On Sat, Jun 15, 2013 at 6:06 PM, Ray Zimmerman <r...@cornell.edu> wrote:
> If you are unable to resolve the issue on your own, feel free to send me a 
> case file (I prefer an M-file … just use savecase() to save it) and maybe I 
> can have a look (in a few weeks when I'm back from some time off).
> 
> -- 
> Ray Zimmerman
> Senior Research Associate
> B30 Warren Hall, Cornell University, Ithaca, NY 14853
> phone: (607) 255-9645
> 
> 
> 
> 
> 
> On Jun 14, 2013, at 5:17 AM, Cédric Josz <cedric.j...@gmail.com> wrote:
> 
>> Hi Ray,
>>  
>> I'm getting back to you on an issue I was experiencing earlier with setting 
>> branch angle difference limits when running runopf.
>>  
>> I was using the old version format for case files so I converted my data to 
>> .mat files (version 2) as you suggested.
>>  
>> Yet runopf still ignores branch angle difference limits, however tight I 
>> make them.
>>  
>> I've highlighted the bound I wish to impose below :
>>  
>> s =
>>     baseMVA: 100
>>         bus: [4x13 double]
>>         gen: [3x10 double]
>>      branch: [4x13 double]
>>       areas: [1 1]
>>     gencost: [3x7 double]
>>  
>> >> s.baseMVA
>> ans =
>>    100
>>  
>> >> s.bus
>> ans =
>>   Columns 1 through 7
>>     1.0000    3.0000         0         0         0         0    1.0000
>>     2.0000    2.0000         0         0         0         0    1.0000
>>     3.0000    1.0000    1.6300    0.1600         0         0    1.0000
>>     4.0000    2.0000         0         0         0         0    1.0000
>>   Columns 8 through 13
>>     1.0000         0  230.0000    1.0000    1.1000    0.9500
>>     1.0000         0  230.0000    1.0000    1.1000    0.9500
>>     1.0000         0  230.0000    1.0000    1.1000    0.9500
>>     1.0000         0  230.0000    1.0000    1.1000    0.9500
>>  
>> >> s.gen
>> ans =
>>   Columns 1 through 7
>>     1.0000         0         0   10.0000  -10.0000    1.1000  100.0000
>>     2.0000         0         0   10.0000  -10.0000    1.1000  100.0000
>>     4.0000         0         0         0   -5.0000    1.1000  100.0000
>>   Columns 8 through 10
>>     1.0000   10.0000  -10.0000
>>     1.0000   10.0000  -10.0000
>>     1.0000         0  -10.0000
>>  
>> >> s.branch
>> ans =
>>   Columns 1 through 7
>>     1.0000    3.0000    1.5000   15.7000    0.0002  250.0000  250.0000
>>     1.0000    4.0000    1.5000   15.7000    0.0002  250.0000  250.0000
>>     2.0000    3.0000   12.0000  125.6000    0.0014  250.0000  250.0000
>>     3.0000    4.0000    3.0000   31.4000    0.0004    0.2600  250.0000
>>   Columns 8 through 13
>>   250.0000         0         0    1.0000         0    1.0000
>>   250.0000         0         0    1.0000         0    1.0000
>>   250.0000         0         0    1.0000         0    1.0000
>>   250.0000         0         0    1.0000         0    0.1000
>>  
>> >> s.areas
>> ans =
>>      1     1
>>  
>> >> s.gencost
>> ans =
>>      2     0     0     3     0     1     0
>>      2     0     0     3     0     1     0
>>      2     0     0     3     0     0     0
>>  
>> Thanks for you help.
>>  
>> Cédric
>> On Wed, Apr 24, 2013 at 3:01 PM, Ray Zimmerman <r...@cornell.edu> wrote:
>> The issue is that you are defining your case in the version 1 format for 
>> MATPOWER case files, but you are adding columns (ANGMIN and ANGMAX) that are 
>> only available in the version 2 format, so they are not being read, but are 
>> being set to the default (unconstrained) values.
>> 
>> Simply convert your case file to version 2 format and it should work.
>> 
>> -- 
>> Ray Zimmerman
>> Senior Research Associate
>> 419A Warren Hall, Cornell University, Ithaca, NY 14853
>> phone: (607) 255-9645
>> 
>> 
>> 
>> 
>> On Apr 23, 2013, at 12:55 PM, Cédric Josz <cedric.j...@gmail.com> wrote:
>> 
>>> Ray, thank you for getting back to me so quickly.
>>> You shouldn't have to do anything besides specify the angle limits. Are you 
>>> saying that you have specified ANGMIN and ANGMAX (in degrees) and the OPF 
>>> converges successfully, but the angles violate the specified limits? And 
>>> you didn't set the OPF_IGNORE_ANG_LIM option?
>>>  
>>> Yes that is what I am saying. 
>>>  
>>> 
>>> If so, can you send me the case off-list so I can confirm. It could be a 
>>> bug.
>>>  
>>> Ok I'll send it to you.
>>>  
>>> Thanks for your time.
>>>  
>>> Cédric
>>>  
>>> 
>>> --Ray
>>> 
>>> 
>>> On Apr 23, 2013, at 10:24 AM, Cédric Josz <cedric.j...@gmail.com> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> I would like to run an OPF with branch angle difference limits, which is 
>>>> possible according to Matpower's 2011 manual (section 5.4.4 : Optimal 
>>>> power flow / standard extensions / branch angle difference limits ).
>>>> 
>>>> However, the program "runopf" doesn't take them into account when I run it 
>>>> on a data file on which I've specified "angmin" and "angmax" in the branch 
>>>> matrix.
>>>> 
>>>> How must one proceed to specify such constraints ?
>>>> 
>>>> Thanks in advance for your help.
>>>> 
>>>> Cédric Josz
>>>> PhD student at Paris 6 University 
>>> 
>> 
>> 
> 
> 
> <test.m>

Reply via email to