From: Sawyer F. <mi...@se...> - 2013-03-26 15:55:08
|
Is anybody experiencing terrible performance of the integrator, used in functions like "step_response"? I see glitches and other random behavior when running my own code, and even for example the pvtol-nested.py example code. The integrator it uses, scipy.integrate.odeint, is derived from some fortran code somewhere and appears to be doing optimization that is giving unwanted behavior. One can force a short simulation interval dt for a fixed-step integration by passing "hmax=dt" to "step-respose" and get a response that looks like Matlab's, but I'd rather just have a working integrator that optimizes correctly. Anybody know a good workaround, eg settings for the integrator that make it behave normally? Or why it is giving odd behavior? S ------------------------ Sawyer B. Fuller, Ph.D. Harvard School of Engineering and Applied Science Wyss Institute for Biologically Inspired Engineering http://people.seas.harvard.edu/~minster/ |