art-framework-suite / messagefacility

Other
0 stars 1 forks source link

statistics destination behavior changed #6

Open knoepfel opened 3 years ago

knoepfel commented 3 years ago

This issue has been migrated from https://cdcvs.fnal.gov/redmine/issues/21589 (FNAL account required) Originally created by @rlcee on 2018-12-19 17:14:18


Between art v2_10_04 messagefacility v2_01_07 (mu2e Offline v7_1_5)

and

art v2_11_05 messagefacility v2_02_04 (mu2e Offline v7_2_0)

This destination:

   statistics: {
       stats: {
          type: "cout"
       }
    }

has stopped giving this print:

MessageLogger Summary

type category sev module subroutine count total


1 ArtReport -i SourceEvent 2 2 2 HITS -i StrawDigisFromSt 1 1

and started giving:

============================================================================

Duplicate name for a MessageLogger Statistics destination: "cout" Only original configuration instructions are used.

============================================================================

To reproduce: source /cvmfs/mu2e.opensciencegrid.org/setupmu2e-art.sh source /cvmfs/mu2e.opensciencegrid.org/Offline/X/SLF6/debug/Offline/setup.sh mu2e -n 1 -c Validation/fcl/ceSimReco.fcl where is "X" is "v7_1_5" for the old behavior and "v7_2_0" for the new behavior.

knoepfel commented 3 years ago

Comment by @rlcee on 2021-10-14 20:08:10


I realized this still appears to be incorrect, and could have helped with understanding recent exceptions. I'd still like to have this summary back. Thanks

knoepfel commented 3 years ago

Comment by @rlcee on 2021-10-19 18:13:38


I'm not sure how I missed it before, but I can turn off my second "cout" destination for the statistics, and add outputStatistics : true to the main cout destination. This works to restore the statistics print, so we are fully operational again.

The original error message about duplicate "cout" destinations doesn't make sense if you should be able to have have multiple destinations of type cout. Or maybe you can't?
I can't find a rule in the docs. If you want to keep that question alive as this ticket, then you can keep this open, but I don't need it open any more. Thanks