Add TRACEs around critical operations in art process
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).
#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.