Skip to main content
replaced http://mathematica.stackexchange.com/ with https://mathematica.stackexchange.com/
Source Link

This seems to be the same problem (bug?) as mentioned in this commentthis comment. Add SolveDelayed->True to NDSolve will resolve the problem. (This option is red, but don't worry. )

BTW, when n >= 10, NDSolve spits out ndsz warning and stops before t reaches 5, and it seems to be the nature of the equation set. If the singularity isn't expected, probably there's something wrong with the definition of equations.

This seems to be the same problem (bug?) as mentioned in this comment. Add SolveDelayed->True to NDSolve will resolve the problem. (This option is red, but don't worry. )

BTW, when n >= 10, NDSolve spits out ndsz warning and stops before t reaches 5, and it seems to be the nature of the equation set. If the singularity isn't expected, probably there's something wrong with the definition of equations.

This seems to be the same problem (bug?) as mentioned in this comment. Add SolveDelayed->True to NDSolve will resolve the problem. (This option is red, but don't worry. )

BTW, when n >= 10, NDSolve spits out ndsz warning and stops before t reaches 5, and it seems to be the nature of the equation set. If the singularity isn't expected, probably there's something wrong with the definition of equations.

Source Link
xzczd
  • 68.4k
  • 9
  • 174
  • 489

This seems to be the same problem (bug?) as mentioned in this comment. Add SolveDelayed->True to NDSolve will resolve the problem. (This option is red, but don't worry. )

BTW, when n >= 10, NDSolve spits out ndsz warning and stops before t reaches 5, and it seems to be the nature of the equation set. If the singularity isn't expected, probably there's something wrong with the definition of equations.