Project

General

Profile

Feature #13305

Modifications to support the running of multiple disk-writing Aggregators

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

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
07/20/2016
Due date:
% Done:

0%

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

Description

There is the desire to be able to run multiple disk-writing Aggregators. We should investigate what changes are needed to support that and make those changes.

History

#1 Updated by Kurt Biery over 3 years ago

  • Target version set to v1_13_00

#2 Updated by Kurt Biery over 3 years ago

  • Status changed from Assigned to Resolved

These changes were completed a while ago. In the artdaq repository, they were the following:

AggregatorCore.cc was changed so that we can specify which Aggregator(s) should write data to disk and which one should handle online monitoring
  • these are controlled with "is_data_logger" and "is_online_monitor" FHiCL configuration parameters

RootMPIOutput_module.cc was changed to send multiple copies of the InitFragment and the EndOfSubRunFragment, when needed.

The related changes in the artdaq_demo repository were the following:

generateAggregator.rb was changed so that it supports the setting of the aggregator type parameters

generateAggregatorMain.rb was changed to assign the Aggregator types and include the Aggregator Index in the disk file name, if there are more than one disk-writing Aggregators.

generateEventBuilderMain.rb was changed to correctly set the number of data_receiver_count when more than one disk-writing AG is configured.

start2x2x4System.sh and manage2x2x4System.sh scripts were created

#3 Updated by Kurt Biery over 3 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF