<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Mon, Nov 5, 2018 at 3:23 PM Justin Chang via petsc-users <<a href="mailto:petsc-users@mcs.anl.gov">petsc-users@mcs.anl.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi everyone,<div><br></div><div>I am working on a generic AC optimal power flow solver, and I hope to use DMNetwork's data structure and TAO's optimization solvers for this purpose. Last time I inquired about IPM (maybe 3-4 years ago) I was told that it's not suitable for large-scale networks, which is the direction we're hoping to go here at NREL. I see right now from the documentation website: <br><br>"This algorithm is more of a place-holder for future constrained optimization algorithms and should not yet be used for large problems or production code."<br><br>Is there any plans at the moment to have a high performance implementation of IPM in TAO? It would be nice to have a purely PETSc code instead of interfacing to something like IPOPT for the optimization.</div></div></div></blockquote><div><br></div><div>Preliminary question. Are there reasons we expect IPM to be better than active sets?</div><div><br></div><div> Thanks,</div><div><br></div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>Thanks,</div><div>Justin</div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener</div><div><br></div><div><a href="http://www.cse.buffalo.edu/~knepley/" target="_blank">https://www.cse.buffalo.edu/~knepley/</a><br></div></div></div></div></div></div></div></div>