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
In following up to issue #135, if there is time please add the other mass's name, so these "go-beyond-edge" alerts so they would look like this:
Random examples for mass 1:
Farthest from mass 2, force arrows tiny, forces 0.7 newtons.
Closest to mass 2, force arrows tiny, forces 39.5 newtons.
Extremely close to mass 2, force arrows very small, forces 144.2 newtons.
Very close to mass 2, force arrows huge, forces 1067.9 newtons.
Random examples for mass 2:
Extremely close to mass 1, force arrows small, forces 184.7 newtons.
Far from mass 1, force arrows tiny, forces 11.5 newtons.
Very close to mass 1, force arrows large, forces 454 newtons.
Farthest from mass 1, force arrows tiny, forces 21.7 newtons.
As mentioned in #135 (comment), I don't want this request to block this sim from going into Dev Testing.
If logic to handle this request does not already exist, we could make this addition when we are finishing off GFL Regular. I am marking as low priority (so as not be a blocking issue).
The text was updated successfully, but these errors were encountered:
In following up to issue #135, if there is time please add the other mass's name, so these "go-beyond-edge" alerts so they would look like this:
Random examples for mass 1:
Random examples for mass 2:
As mentioned in #135 (comment), I don't want this request to block this sim from going into Dev Testing.
If logic to handle this request does not already exist, we could make this addition when we are finishing off GFL Regular. I am marking as low priority (so as not be a blocking issue).
The text was updated successfully, but these errors were encountered: