4 ms·
I think it’s just an artifact of the way the ODE gets discretized. You could probably figure out more precisely by reading the code, though it seems to be writt
by jacobolus 11y ago
I think it’s just an artifact of the way the ODE gets discretized. You could probably figure out more precisely by reading the code, though it seems to be written in an ML-like language without any comments, so code readability is going to depend a bit on your familiarity with such languages.
https://github.com/imeckler/diffgeo/blob/master/Main.elm https://github.com/imeckler/diffgeo/blob/master/Main.elm
https://github.com/imeckler/diffgeo/blob/master/ODE.elm https://github.com/imeckler/diffgeo/blob/master/ODE.elm
- bri3d 11y agoFor the curious (and if it wasn't obvious enough from the file extension), the language is "Elm" : http://elm-lang.org/ http://elm-lang.org/
- archgoon 11y agoThe actual guts of the algorithm are in compiled javascript https://github.com/imeckler/diffgeo/blob/master/Native/ODE.js https://github.com/imeckler/diffgeo/blob/master/Native/ODE.j... However, this seems to simply be using the numeric library. http://www.numericjs.com/documentation.html http://www.numericjs.com/documentation.html Which uses 'Dormand-Prince RK'. https://en.wikipedia.org/wiki/Dormand%E2%80%93Prince_method https://en.wikipedia.org/wiki/Dormand%E2%80%93Prince_method