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
Is your feature request related to a problem? Please describe.
In a pipeline a module running at a higher fps may need to be throttled to match successive module requirements. The throttling is limited by source module fps. We need a logic to throttle a module (non-source) to required fps within a pipeline.
Describe the solution you'd like
The solution is to skip frames during step() using skipN and skipD. The skip logic needs an improvement as the skipRatio may get complex values and cannot be simplified.
Describe alternatives you've considered
Alternate solution is to add the skip logic within the module instead of framework level. This may work as a temporary solution but the above solution is permanent and tested.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In a pipeline a module running at a higher fps may need to be throttled to match successive module requirements. The throttling is limited by source module fps. We need a logic to throttle a module (non-source) to required fps within a pipeline.
Describe the solution you'd like
The solution is to skip frames during step() using skipN and skipD. The skip logic needs an improvement as the skipRatio may get complex values and cannot be simplified.
Describe alternatives you've considered
Alternate solution is to add the skip logic within the module instead of framework level. This may work as a temporary solution but the above solution is permanent and tested.
The text was updated successfully, but these errors were encountered: