Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • $\begingroup$ Seems that "StateSpace" method is triggered by WorkingPrecision option. ({state}=NDSolve`ProcessEquations[…]; state["NumericalFunction"]["FunctionExpression"] shows that NDSolve is still dealing with a DAE system, StateSpace seems to be the only available DAE solver for arbitrary precision in this case, and adding Method -> {"TimeIntegration" -> {"StateSpace"}} to your code doesn't seem to change the timing. ) It's a bit surprising that adding WorkingPrecision->8 speeds up the code. $\endgroup$ Commented Nov 15, 2019 at 12:56
  • $\begingroup$ Another somewhat surprising thing is, adding SolveDelayed->True to the sample fails in v12 resolves the problem. $\endgroup$ Commented Nov 15, 2019 at 13:03
  • $\begingroup$ @xzczd I guess that the speeding up with WorkingPrecision->8 is probably because the default AccuracyGoal and PrecisionGoal is half of the WorkingPrecision according to the NDSolve documentation. $\endgroup$ Commented Nov 16, 2019 at 16:19