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
Pausing/Splitting/Starting should happen when you think they happen. "Maybe" logic triggers those events, but undoes them if it turned out to be incorrect.
The text was updated successfully, but these errors were encountered:
So, would maybe logic include some sort of popup asking for a few seconds (maybe 10-20 by default but also configurable), if that was supposed to split, and if you confirm it, then it uses the original time it expected for the split to happen.
Maybe logic could also include if it thinks it should split, but within a certain window of time it gets a higher confidence level to split, would ignore the first time, while also working with the prompt I suggested above.
Ideally it should be scripted to tell the "maybe" if it's correct or incorrect at a later time.
Here's a example that I believe would work, but is far from elegant:
split{if(features["foo"]>70.0){// Current time plus 10 secondsvars.lastSplitTime=timer.CurrentTime.RealTime.Value.Add(newTimeSpan(0,0,10);returntrue;}}undo{returnfeatures["bar"]>80.0&&timer.CurrentTime.RealTime.Value<vars.lastSplitTime;}
Pausing/Splitting/Starting should happen when you think they happen. "Maybe" logic triggers those events, but undoes them if it turned out to be incorrect.
The text was updated successfully, but these errors were encountered: