Unfortunately, the current MATPOWER design did not have such modifications via callbacks in view. I don’t think there is currently a simple workaround. It involves redesigning and refactoring the MATPOWER OPF code.
Ray > On Mar 14, 2016, at 5:02 AM, Paul Radvan <[email protected]> wrote: > > Dear all, > > I have a question regarding the extension of Matpower OPF by user-defined > non-linear constraints. > I implemented some additional non-linear constraints in the matpower code > itself, following pretty much Ray's guidelines from an earlier post found > here: https://www.mail-archive.com/matpower-l%40cornell.edu/msg01565.html > <https://www.mail-archive.com/matpower-l%40cornell.edu/msg01565.html>. > > This seems to work fine but I would now like to migrate the constraint, > jacobian and hessian declaration to separate files, to make usage with an > unmodified matpower package possible. However the usual procedure of > registering it as a callback function seems impossible, as there is no stage > provided inside the OPF execution itself. > Is this correct and is there a workaorund for this problem? > Any other ideas on how to define the modifications externally would also be > appreciated. > > Kind Regards, > Paul Radvan > > -- > Paul Radvan > Studentische Hilfskraft > > Technische Universität Berlin > Fakultät IV Elektrotechnik und Informatik > Fachgebiet Energieversorgungsnetze und Integration Erneuerbarer Energien > > Straße des 17. Juni 135, 10623 Berlin > > [email protected] <mailto:[email protected]>
