[SciPy-user] [OpenOpt] problem with ralg (latest SVN)

[Emanuele Olivetti]

Dear all and Dmitrey,

I've just updated to latest openopt (SVN). When using numpy 1.0.3
and scipy 0.5.2 (standard in Ubuntu 7.10 gutsy gibbon) openopt says
that "ralg" (NLP) algorithm is missing! With more recent numpy
and scipy it seems to work reliably. But what happened with respect
to older numpy+scipy? In that case even running examples/nlp_1.py
returns:
----
$ python nlp_1.py
OpenOpt checks user-supplied gradient df (shape: (150,) )
according to:
    prob.diffInt = [  1.00000000e-07]
    |1 - info_user/info_numerical| <= prob.maxViolation = 0.01
derivatives are equal
========================
OpenOpt checks user-supplied gradient dc (shape: (2, 150) )
according to:
    prob.diffInt = [  1.00000000e-07]
    |1 - info_user/info_numerical| <= prob.maxViolation = 0.01
derivatives are equal
========================
OpenOpt checks user-supplied gradient dh (shape: (2, 150) )
according to:
    prob.diffInt = [  1.00000000e-07]
    |1 - info_user/info_numerical| <= prob.maxViolation = 0.01
derivatives are equal
========================
OO Error:incorrect solver is called, maybe the solver "ralg" is not
installed. Maybe setting p.debug=1 could specify the matter more precisely
Traceback (most recent call last):
  File "nlp_1.py", line 110, in <module>
    r = p.solve('ralg')
  File
"/usr/lib/python2.5/site-packages/scikits/openopt/Kernel/BaseProblem.py",
line 185, in solve
    return runProbSolver(self, solvers, *args, **kwargs)
  File
"/usr/lib/python2.5/site-packages/scikits/openopt/Kernel/runProbSolver.py",
line 48, in runProbSolver
    p.err('incorrect solver is called, maybe the solver "' + solver_str
+'" is not installed. Maybe setting p.debug=1 could specify the matter
more precisely')
  File
"/usr/lib/python2.5/site-packages/scikits/openopt/Kernel/oologfcn.py",
line 16, in ooerr
    raise OpenOptException(msg)
scikits.openopt.Kernel.oologfcn.OpenOptException: incorrect solver is
called, maybe the solver "ralg" is not installed. Maybe setting
p.debug=1 could specify the matter more precisely
----

This did not happen before so I guess it is due to a recent
commit. It is possible to solve the problem?

Kind Regards,

Emanuele