Malcolm,

I see we still have some old information on the BPMPD_MEX web page. It turns 
out that the change made to version 2.21.1 eliminated the error for the test 
cases we were using at the time. Later we discovered that there are still 
circumstances under which the current version of BPMPD gives incorrect 
(infeasible) answers. I'll update the info on the web page to reflect this.

So, just so you understand how MATPOWER handles this, if you're using BPMPD_MEX 
to solve a DC OPF (or, for that matter, any problem that calls qps_matpower 
with the appropriate inputs), it will check to make sure the answer is 
feasible. If it is not, it prints the warning and calls qps_matpower again 
using MIPS as the solver.

So, if you want to eliminate the printing of the warning, I suggest you wrap 
lines 444 and 445 of qps_bpmpd.m in an "if verbose > 0 ... end" (or just 
comment them out). I've added this conditional for the next version. However, 
if it is printing this warning for *all* of your DC OPF's then you are 
definitely going to speed things up by just using MIPS in the first place and 
skipping the failing BPMPD attempts.

Hope this helps,

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



On May 26, 2011, at 10:24 AM, Malcolm Barnacle wrote:

> Dear Carlos,
>  
> I am using the BPMPD_MEX solver for DC OPF and it works really well, 
> generating the results I expect. However I can't seem to get rid of the below 
> warning message:
>  
> WARNING: This version of BPMPD_MEX has a bug which caused it to return
>                  an incorrect (infeasible) solution for this particular 
> problem.
>                  equality constraint violated by 23.197
>  
> I understand that this is to do with a bug that was in version 2.21 of the 
> MEX solver. I have version 2.21.1 installed and in use, which, along with the 
> latest stable version of Matpower, outputs the results I need and bypasses 
> this warning. However because this warning message is being constantly 
> printed to my matlab command window, it is greatly slowing down my 
> optimisation program.
>  
> How can I stop this warning message from being displayed? Or how can I change 
> the bpopt m-file so that this error does not occur?
>  
> The function "warning off all" does not work as I'm guessing that the warning 
> is not produced through matlab code.
>  
> I would greatly appreciate a response soon, and if anyone else knows how I 
> can do this then please let me know as well.
>  
> Thanks for your help again.
> Malcolm  
>  
> ---------------------------------
> Malcolm Barnacle, MEng MIET
> PhD Research Student
> 
> Institute for Energy and Environment
> Department of Electronic and Electrical Engineering
> University of Strathclyde
> Royal College Building
> 204 George Street
> Glasgow G1 1XW
> 
> Email:  [email protected]
> Tel:    +44 (0)141 548 4839
>  
> The University of Strathclyde is a charitable body, registered in Scotland, 
> number SC015263

Reply via email to