Project

General

Profile

Feature #17930

Allow configurable dropping of data

Added by Eric Flumerfelt almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Additional Functionality
Target version:
Start date:
10/17/2017
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

In the case where the art process is falling behind, artdaq should be configurable to drop data instead of exerting back-pressure.

History

#1 Updated by Eric Flumerfelt almost 3 years ago

  • Category set to Additional Functionality
  • Status changed from New to Resolved
  • Assignee set to Eric Flumerfelt
  • Target version set to artdaq Next Release

Resolved by c59ec85. User must set both "non_reliable_mode" and "non_reliable_mode_retry_count" (default is size_t::MAX_VALUE). Fragments will then be dropped by DataReceiverManager if it fails to put the fragment into the SharedMemoryEventManager after retry_count attempts.

#2 Updated by Eric Flumerfelt over 2 years ago

  • Status changed from Resolved to Closed
  • Target version changed from artdaq Next Release to artdaq v3_00_01

This may actually have been in artdaq v2_03_03...



Also available in: Atom PDF