Delayed postprocessing timeout logic

[denizergonul]

Description

What is changing and why. For example, what prompted this change?

Delayed postprocessing timeout logic is changing due to:

• Frames getting stuck in buffer indefinitely without being postprocessed if no new items arrive.
• Trigger needing to define additional steps to take in case of a timeout.

Solution includes:

• With each timeout, ending point for the processing window is widened, allowing all frames to eventually meet the processing threshold.
• A timeout policy function that will be defined by DataHandlingModel variants. (e.g. TriggerDataHandlingModel)

Testing Suggestions

For example, what steps would a reviewer use to see the change in action?

TODO

Correlated Issues and/or PRs

If multiple Issues or PRs are part of this change, list them here. The sub-issue functionality in GitHub can also be used.

Delayed postprocessing timeout logic #104
Delayed postprocessing timeout logic #416

Useful Coordination

List whatever coordination between developers or groups will be useful, such as the timing of merges or updating of documentation or updating of configurations

TriggerDataHandlingModel<RDT, RHT, LBT, RPT, IDT>::invoke_postprocess_schedule_timeout_policy() has to be implemented.

Impact on Developers or Users

For example, API changes or new run control commands

// Actions postprocess scheduler takes if no data arrives in a configured time
DataHandlingModel<RDT, RHT, LBT, RPT, IDT>::invoke_postprocess_schedule_timeout_policy()
TriggerDataHandlingModel<RDT, RHT, LBT, RPT, IDT>::invoke_postprocess_schedule_timeout_policy()

Changes in System Behavior

For example, changes in how data is drained from the system when a run is stopped

TODO

Needed Changes in Testing

For example, new regression tests that are needed, or instructions for special tests that should be run at EHN1

TODO