Project

General

Profile

Feature #21072

Add TRACEs around critical operations in art process

Added by Eric Flumerfelt about 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Additional Functionality
Target version:
Start date:
10/09/2018
Due date:
% Done:

0%

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

Description

Implemented on artdaq-core/feature/TracesForTimeSpentInArt and artdaq/feature/TracesForTimeSpentInArt. Additional TRACE calls which help to show the progress of the art process through an event (copying into art memory, writing output in RootDAQOutFile).

History

#1 Updated by Kurt Biery almost 2 years ago

Today, I merged the for_dune-artdaq branches in both artdaq-core and artdaq into the feature/TracesForTimeSpentInArt branches in both repositories to bring them up-to-date. (The for_dune-artdaq branches in both repos are up-to-date with the develop branches.)

I then made a few changes:
  • removed redundant trace messages in RootDAQOutFile::writeOne
  • added app_name to TRACE_NAME in RootDAQOut_module.cc
  • in RootDAQOutFile, added app_name to TRACE_NAME and added trace statements in writeTTrees to provide inside into where time is spent during file closing

An additional change that I'm considering is adding app_name to TRACE_NAME in SharedMemoryReader, so that we can focus on DataLogger SharedMemoryReader messages.

#2 Updated by Eric Flumerfelt over 1 year ago

  • Assignee set to Kurt Biery
  • Status changed from Resolved to Reviewed
  • Co-Assignees Eric Flumerfelt added

The only changes left in this branch are two traces in SharedMemoryManager. I have reviewed the code and am merging into develop.

#3 Updated by Eric Flumerfelt over 1 year ago

  • Target version set to artdaq v3_04_00
  • Status changed from Reviewed to Closed


Also available in: Atom PDF