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
The optimizer main loop samples result values at 1/10 of a second by default. When workloads do not produce samples into the value function variables at least this fast, the frame analysis fails. For now, we can require the minimum value to be related.
A defensive check should be added that verifies the rate is always at or above some minimum
The case in which there is not enough data to derive a value should be considered valid for the purposes of stability detection, but it should be treated as a special case such that if it persists for long enough it is considered an error. This should be allowed for each frame.
The minimum rate should be lowered in lieu of ^
The text was updated successfully, but these errors were encountered:
dave2wave
added
validated
validated as an issue to be worked on
complex
These issues require codebase familiarity and will need cross-cutting changes
labels
Jul 19, 2024
The optimizer main loop samples result values at 1/10 of a second by default. When workloads do not produce samples into the value function variables at least this fast, the frame analysis fails. For now, we can require the minimum value to be related.
The text was updated successfully, but these errors were encountered: