No, I try not to do so except (clear) indication... or new function I 'depend' on.
Just saw the release of 1v73. Will pull it and get it running again.
The reason I asked is: long time ago, I did some simulations (of dog fights)... and all of a sudden, in a fraction of a seconds a plane was flying a very different altitude in same direction (3 dimensional). The change in location/altitude was physically impossible. It turned out that some formulas had critical 'input parameter transitions' in intermediate results - division by very small numbers and multiplication by very large numbers - which challenged the accuracy of a physical computing machine (Numerical Methods/Problems). Resolve the formula in different ways for different input value ranges resolved the issue. --- (Cyclic) calculation of the the timer values could be something with similar issues... (btw, just happened this very moment again - 05:25 to the second - about 9hrs after the last time... so I keep it running for another 6..9 hours with the same release 1v72 and no change, if you think you could get something out of it.)
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
No, I try not to do so except (clear) indication... or new function I 'depend' on.
Just saw the release of 1v73. Will pull it and get it running again.
The reason I asked is: long time ago, I did some simulations (of dog fights)... and all of a sudden, in a fraction of a seconds a plane was flying a very different altitude in same direction (3 dimensional). The change in location/altitude was physically impossible. It turned out that some formulas had critical 'input parameter transitions' in intermediate results - division by very small numbers and multiplication by very large numbers - which challenged the accuracy of a physical computing machine (Numerical Methods/Problems). Resolve the formula in different ways for different input value ranges resolved the issue. --- (Cyclic) calculation of the the timer values could be something with similar issues... (btw, just happened this very moment again - 05:25 to the second - about 9hrs after the last time... so I keep it running for another 6..9 hours with the same release 1v72 and no change, if you think you could get something out of it.)
(05:25:00)=0 / (06:32:50)+0:07:50 / (07:49:35)+2:24:35