Project

General

Profile

Bug #22371

TimeTracker summary wrong when only one event in the job

Added by Gianluca Petrillo 4 months ago. Updated 4 months ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
Infrastructure
Target version:
Start date:
04/12/2019
Due date:
% Done:

100%

Estimated time:
4.00 h
Spent time:
Occurs In:
Scope:
Internal
Experiment:
-
SSI Package:
art
Duration:

Description

When processing a single event from a file, TimeTracker shows two events in the summary Full event output:

%MSG-i LArG4:  LArG4:largeant@BeginModule 12-Apr-2019 13:11:50 CDT  run: 20000002 subRun: 0 event: 1
Geant4 simulated 928 MC particles, we keep 928 .
%MSG
12-Apr-2019 13:11:50 CDT  Opened output file with pattern "%ifb_g4.root" 
12-Apr-2019 13:11:51 CDT  Closed output file "prodgenie_nue_dune10kt_1x2x6_gen_Reference_g4.root" 
12-Apr-2019 13:11:51 CDT  Closed input file "xroot://fndca1.fnal.gov:1094/pnfs/fnal.gov/usr/dune/persistent/users/vito/ci_tests_inputfiles/DUNEFD/gen/prodgenie_nue_dune10kt_1x2x6_gen_Reference.root" 

================================================================================================================================
TimeTracker printout (sec)                        Min           Avg           Max         Median          RMS         nEvts   
================================================================================================================================
Full event                                     0.260577       97.9552       195.65        97.9552       97.6947         2     
--------------------------------------------------------------------------------------------------------------------------------
source:RootInput(read)                         0.377006      0.377006      0.377006      0.377006          0            1     
simulate:rns:RandomNumberSaver                0.000953754   0.000953754   0.000953754   0.000953754        0            1     
simulate:largeant:LArG4                         195.268       195.268       195.268       195.268          0            1     
[art]:TriggerResults:TriggerResultInserter    0.000205158   0.000205158   0.000205158   0.000205158        0            1     
end_path:out1:RootOutput                      6.9429e-05    6.9429e-05    6.9429e-05    6.9429e-05         0            1     
:out1:RootOutput(write)                        0.260577      0.260577      0.260577      0.260577          0            1     
================================================================================================================================
%MSG-i NuRandomService:  RootOutput:out1@EndJob 12-Apr-2019 13:11:51 CDT  ModuleEndJob
[...]
TrigReport ---------- Event  Summary ------------
TrigReport Events total = 1 passed = 1 failed = 0

TrigReport ------ Modules in End-Path: end_path ------------
TrigReport  Trig Bit#        Run    Success      Error Name
TrigReport     0    0          1          1          0 out1

TimeReport ---------- Time  Summary ---[sec]----
TimeReport CPU = 195.483282 Real = 197.089752

It basically made up another event taking 0.26 seconds, and averaged it with the real one.

This was the output of

lar --rethrow-all -n 1 --config standard_g4_dune10kt_1x2x6.fcl xroot://fndca1.fnal.gov:1094/pnfs/fnal.gov/usr/dune/persistent/users/vito/ci_tests_inputfiles/DUNEFD/gen/prodgenie_nue_dune10kt_1x2x6_gen_Reference.root

run on dunebuild01.fnal.gov with something close to LArSoft v08_14_01.

History

#1 Updated by Kyle Knoepfel 4 months ago

  • Assignee set to Kyle Knoepfel
  • Subject changed from TineTracker summary wrong when only one event in the job to TimeTracker summary wrong when only one event in the job

#2 Updated by Kyle Knoepfel 4 months ago

  • Estimated time set to 4.00 h
  • Status changed from New to Assigned

#3 Updated by Kyle Knoepfel 4 months ago

  • % Done changed from 0 to 100
  • Status changed from Assigned to Resolved
  • Category set to Infrastructure

The bug was due to an incorrectly set path name, which left the TimeTracker in an incongruent state. Fix implemented with commit art:8cc497f.

#4 Updated by Kyle Knoepfel 4 months ago

  • Target version set to 3.02.05

#5 Updated by Kyle Knoepfel 4 months ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF