You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, the normal way to handle an equal to comp with floating points is to define a tolerance for them to be equal. Unfortunately, we have an issue where rn we are expressing the entire kinematics calculation as infinitely precise. So we can only do <= in the very literal sense. We should maybe define a precision for the simulation? Or not? Idk. The temp fix is the < instead of <=, which will generally yield the correct results. But this is kind of an annoying problem that we need to address.
The text was updated successfully, but these errors were encountered:
In reaction threshold check, currently say
which is technically incorrect. Should be
However, the normal way to handle an equal to comp with floating points is to define a tolerance for them to be equal. Unfortunately, we have an issue where rn we are expressing the entire kinematics calculation as infinitely precise. So we can only do <= in the very literal sense. We should maybe define a precision for the simulation? Or not? Idk. The temp fix is the < instead of <=, which will generally yield the correct results. But this is kind of an annoying problem that we need to address.
The text was updated successfully, but these errors were encountered: