Funkerfish

Hi！It seems that you have the same problem as me. My suggestion is to use the ```success``` field to test first if it can cause the not a number thing...

when the diction of parameters is set as: ``` as = 2:0.1:8; bs = -0.9:0.05:0.01; ``` the warning comes immediately.

it seems that the loop would never end when the instability warning comes, I don't know but I guess it would be the NaN, so as the function ```trajectory()``` returns....

```lyapunovspectrum``` never returns once the warning comes. I check the matrix which saves the values and find that it still be zero (already pre-assign 0 values to the matrix)

Because this problem comes from the ODE solver, the same warning would take place in other functions like ```Interactive Trajectory Evolution``` when we slide the bar of parameters. I think...

Of course, the ```success``` field would work. But my point is, many people like me would use more than one coding language to do the calculation, for example, obtaining the...

> What is the additional benefit of making the state NaN as well as having a false return code for success? To be more specific, please allow me to show...

>But I am curious. Why are you doing your timeseries analysis in Matlab instead of Julia...? I really agree with you that Julia is superfast when doing calculation and that...

Okey, I will look forward to this update! Would we still see the warning message in REPL before returning NaN? because its quite annoying and would block the progress bar....

Hello again! I have another question. Inspired by @rusandris，I use ```check_error``` to detect whether the parameter could cause the instability and then pass them to the ```trajectory```. My question is,...