recojob_dayone.fcl
Go to the documentation of this file.
1 #NuTools Services
2 #include "seedservice.fcl"
3 
4 #GArSoft Services
5 #include "DetectorClocks.fcl"
6 #include "DetectorProperties.fcl"
7 #include "GArProperties.fcl"
8 #include "ECALProperties.fcl"
9 #include "Geometry.fcl"
10 #include "RunHistory.fcl"
11 #include "BackTracker.fcl"
12 
13 #Plugins
14 #include "EventInit.fcl"
15 #include "dayoneconverter.fcl"
16 #include "tpctrackfit2.fcl"
17 
18 process_name: RecoProc
19 
20 services:
21 {
22  # Load the service that manages root files for histograms.
23  TFileService: { fileName: "reco_hist.root" }
24  TimeTracker: {}
25  RandomNumberGenerator: {} #ART native random number generator
26  #See Geometry.fcl for the list of geometries available
27  GeometryGAr: @local::nd_hall_mpd_only_dayone_geo
28  GeometryGArConfigurationWriter: {}
29  ExptGeoHelperInterface: @local::standard_geometry_helper
30  DetectorClocks: @local::standard_clocks
31  DetectorProperties: @local::standard_detproperties
32  GArProperties: @local::standard_garproperties
33  ECALProperties: @local::standard_ecalproperties
34  NuRandomService: @local::standard_NuRandomService
35  MagneticField: @local::standard_mag_garsoft
36  BackTracker: @local::standard_backtracker
37 #RunHistory: @local::standard_runhistory
38 }
39 
40 
41 #Start each new event with an empty event.
42 source:
43 {
44  module_type: RootInput
45 }
46 
47 # Define and configure some modules to do work on each event.
48 # First modules are defined; they are scheduled later.
49 # Modules are grouped by type.
50 physics:
51 {
52 
53  producers:
54  {
55  init: @local::standard_EventInit
56  dayone: @local::standard_dayoneconverter
57  trackpass1: @local::dayone_tpctrackfit2
58  }
59  analyzers:
60  {
61  }
62 
63  #Define the producer and filter modules for this path, order matters. Put init 1st!
64  #Filters reject all following items. ee lines starting physics.producers below
65  reco: [init,dayone,trackpass1]
66  #define the output stream, there could be more than one if using filters
67  stream1: [ out1 ]
68 
69  #trigger_paths is a keyword and contains the paths that modify the ::art::event,
70  #ie filters and producers
71  trigger_paths: [ reco ]
72 }
73 
74 #block to define where the output goes. if you defined a filter in the physics
75 #block and put it in the trigger_paths then you need to put a SelectEvents: {SelectEvents: [XXX]}
76 #entry in the output stream you want those to go to, where XXX is the label of the filter module(s)
77 outputs:
78 {
79  out1:
80  {
81  module_type: RootOutput
82  fileName: "reco.root" #default file name, can override from command line with -o or --output
83  }
84 }