Project

General

Profile

Support #19517

artdaqDriver splits output data into two files; not sure why

Added by Kurt Biery over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Low
Category:
Known Issues
Target version:
Start date:
03/28/2018
Due date:
% Done:

0%

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

Description

To help with testing disk rate performance, we have created artdaq-demo/tools/fcl/DemoDriverNoDisk.fcl and DemoDriverWithDisk.fcl. These can be run from an artdaq-demo installation using 'artdaqDriver -c <path>/DemoDriverNoDisk.fcl' after running setupARTDAQDEMO.

To test artdaq-v3-related changes to scripts, I tested them on mu2edaq01. Admittedly, this computer does not have very fast disks, and the "WithDisk" test takes noticeably longer than the "NoDisk" one.

Eric has already made changes to SharedMemoryEventManager to allow the draining of the pipeline in cases like the WithDisk test in which the rate of creation of events is much higher than the rate of writing them out.

Something that I noticed is that there are two data files created by the current version of DemoDriverWithDisk.fcl. 90 of the requested 100 events go into the first file, and 10 of them go into the second file. The SMEM buffer count is set to 10, and I wonder if those two values of 10 are correlated.

This is not a high priority, but it is probably worth investigating in case this behavior gives us some insight into the running of full artdaq systems.

History

#1 Updated by Eric Flumerfelt over 2 years ago

  • Category set to Known Issues
  • Status changed from Assigned to Closed
  • Target version set to artdaq v3_01_00


Also available in: Atom PDF