Error with Casadi v2.3.0 binary: 'explicitRK' is not defined

[adowling2]

When I run the dynamic optimization example in the REAME file, I get the following error:

NameError Traceback (most recent call last)
in ()
----> 1 ocp(T,[u>=-1,u<=1,q.start==0,x.start==1,y.start==0,x.end==0,y.end==0],T=T,N=20)

/usr/local/lib/python2.7/dist-packages/optoy/dynamic.pyc in ocp(f, gl, regularize, verbose, N, T, periodic, integration_intervals, exact_hessian)
303
304 # Create the integrator
--> 305 intg = explicitRK(ode, 1, 4, integration_intervals)
306 intg = try_expand(intg)
307

NameError: global name 'explicitRK' is not defined

I am using the Linux binary of Casadi (python27-numpy1.9.1-v2.3.0) and I installed optoy with the pip command recommended in the documentation. Before calling "from optoy import *", I add the Casadi directory using sys.path.append("casadi_install_directory").

[adowling2]

I should add when I quit Ipython, I also get the following message:
CasADi warning: "Reference counting failure. Possible cause: Circular dependency in user code." (assertion "count==0" on line 125 of file "/home/travis/build/casadi/binaries/casadi/casadi/core/shared_object.cpp" failed.)

[jgillis]

Hi there,

I've had a long code sprint with casadi over the summer, and was not updating optoy.
I guess it makes sense to revive it for our upcoming 2.4.0 release.

Out of curiosity, what are you planning to do with optoy?

[adowling2]

I’m evaluating a few options for an upcoming dynamic optimization project involving energy systems and heat exchanger networks. I don’t know if I’ll using “vanilla” CasADi, optoy, JModelicahttp://JModelica.org or something else.

Nevertheless, optoy looks like a very nice package, even if it is restricted to small systems/applications. I figured I’d report the bug, even if I don’t using optoy in the long run.

Alex

On Aug 24, 2015, at 2:37 PM, jgillis <[email protected]mailto:[email protected]> wrote:

Hi there,

I've had a long code sprint with casadi over the summer, and was not updating optoy.
I guess it makes sense to revive it for our upcoming 2.4.0 release.

Out of curiosity, what are you planning to do with optoy?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-134350615.