Bug in fsolve() or just wrong used?

01112015, 05:54 PM
Post: #2




RE: Bug in fsolve() or just wrong used?
I don't think its a bug but an inherent problem of iterative solvers in general: the range in which your solutions lie is "fixed" while you continously increase the "search range".
That is why you can define the algorithm and the variables, how iteration works (in the CASSettings, Page 2). Though I think this is a classical "Layer 8 Problem": If you look at the function, you see, that there is only a certain range where the solution may lie.... 

« Next Oldest  Next Newest »

Messages In This Thread 
Bug in fsolve() or just wrong used?  KonradM  07092015, 08:20 PM
RE: Bug in fsolve() or just wrong used?  RichardZ  01112015 05:54 PM

User(s) browsing this thread: 1 Guest(s)