[Ipopt-tickets] [Ipopt] #167: Any plan to make Ipopt thread-safe
Ipopt
coin-trac at coin-or.org
Wed Sep 14 19:05:38 EDT 2011
#167: Any plan to make Ipopt thread-safe
--------------------------------+-------------------------------------------
Reporter: FabF1 | Owner: ipopt-team
Type: enhancement | Status: new
Priority: normal | Component: Ipopt
Version: 3.8 (C++ Version) | Severity: normal
Resolution: | Keywords: thread-safety
--------------------------------+-------------------------------------------
Comment (by andreasw):
Hi Fabrice,
Sorry, there are not plans at the moment to make Ipopt threadsafe. It
might actually not be that difficult, as long as none of the smart
pointers are shared between the individual threads. But beside the smart
pointers, we currently use global variables for the tagging of vector and
matrix objects - this could be changed, probably with not too much
problems, but I don't think I will get to this soon...
If you would want to take a look at it, I'm talking about the
"unique_tag_" member of the TaggedObject class in
Ipopt/src/Common/IpTaggedObject.hpp . It might be possible to change the
definition of a tag to include the basic pointer of the VectorSpace of
MatrixSpace so that then the unique_tag_ could be moved into those
spaces....
Andreas
--
Ticket URL: <https://projects.coin-or.org/Ipopt/ticket/167#comment:1>
Ipopt <http://projects.coin-or.org/Ipopt>
Interior-point optimizer for nonlinear programs.
More information about the Ipopt-tickets
mailing list