CAFMaker.fcl
Go to the documentation of this file.
1 BEGIN_PROLOG
2 
3 standard_cafmaker_spyv3:
4 {
5  module_type: CAFMaker
6 
7 # GeneratorLabels is a list of module labels for extracting MCTruth data products.
8 # If it is missing, then the CAFMaker module will look for all MCTruth data products
9 # in the event
10 
11 # GeneratorLabels: [ "generator" ]
12 
13 # the GENIEGeneratorLabels variable is a list of module labels for extracting GTruth data
14 # products, which are made only by GENIE. Often a generator module label will have to
15 # appear in GeneratorLabels and in GENIEGeneratorLabels if you want both kinds of
16 # information stored in the analysis tree. Omit this argument if you want CAFMaker_module
17 # to look for all GTruth data products in the event.
18 
19 # GENIEGeneratorLabels: [ "generator" ]
20 
21  InstanceLabelCalo: "ECAL"
22  InstanceLabelMuID: "MuID"
23 
24  GEANTLabel: "geant"
25  RawCaloHitLabel: "daqsipm"
26  RawMuIDHitLabel: "daqsipmmuid"
27  HitLabel: "hit"
28  CaloHitLabel: "sscalohit"
29  MuIDHitLabel: "sscalohitmuid"
30  TPCClusterLabel: "tpccluster"
31  TrackLabel: "track"
32  TrackTrajectoryLabel: "track"
33  VertexLabel: "vertex"
34  ClusterLabel: "calocluster"
35  MuIDClusterLabel: "caloclustermuid"
36  ECALAssnLabel: "trkecalassn"
37  VeeLabel: "veefinder1"
38 
39  POTSummaryLabel: "generator" # leave blank to skip POTSummary
40 
41 # What to save? ==============================================
42 # MC info is: (a) MCTruth, GTruth, MCParticle if WriteMCinfo; (b) MCPtrajectory if
43 # (WriteMCPTrajectory && WriteMCinfo); and (c) MC info in calorimeter if
44 # (WriteMCCaloInfo && WriteMCinfo).
45 # Write momenta associated with MC trajectories only if the trajectory is also written
46  WriteMCinfo: true
47  WriteMCPTrajectory: false
48  WriteMCPTrajMomenta: false
49  WriteMCCaloInfo: true
50 # The origin of an MCParticle might be a short distance from the MCTrue interaction
51 # vertex - maybe it is a pi0, tau or charm produced in the interaction and decayed
52 # by GEANT. Count the MCParticle as from the vertex if it is less than this distance:
53  MatchMCPtoVertDist: 0.001
54 
55 # Tracking info is: (a) raw hits if WriteHits; (b) TPCClusters and the tracks that
56 # they are associated to if WriteTPCClusters; (c) the track info if WriteTracks (d)
57 # found vertices and their associations to track ends if (WriteVertices && WriteTracks).
58  WriteHits: false
59  WriteTPCClusters: true
60  WriteTracks: true
61  WriteTrackTrajectories: false
62  WriteVertices: true
63  WriteVees: true
64 
65 # Calorimetry info is: (a) calorimeter digits if WriteCaloDigits; (b) hits if
66 # WriteCaloHits; (c) clusters if WriteCaloClusters (d) associations to tracks if
67 # (WriteMatchedTracks && WriteCaloClusters && WriteTracks).
68  WriteMuID: true
69  WriteCaloDigits: false
70  WriteCaloHits: true
71  WriteCaloClusters: true
72  WriteMatchedTracks: true
73 
74 # dE/dx algorithms are still here in the analysis code; hence the IonizeTruncate
75 # parameter. Coherent pion analysis has some code here as well. WriteCohInfo
76 # also needs WriteMCinfo.
77  IonizTruncate: 1.00
78  WriteCohInfo: false
79 }
80 
81 standard_cafmaker_spyv3_edep:
82 {
83  module_type: CAFMaker
84 
85 # GeneratorLabels is a list of module labels for extracting MCTruth data products.
86 # If it is missing, then the CAFMaker module will look for all MCTruth data products
87 # in the event
88 
89 # GeneratorLabels: [ "generator" ]
90 
91 # the GENIEGeneratorLabels variable is a list of module labels for extracting GTruth data
92 # products, which are made only by GENIE. Often a generator module label will have to
93 # appear in GeneratorLabels and in GENIEGeneratorLabels if you want both kinds of
94 # information stored in the analysis tree. Omit this argument if you want CAFMaker_module
95 # to look for all GTruth data products in the event.
96 
97 # GENIEGeneratorLabels: [ "generator" ]
98 
99  InstanceLabelCalo: "ECAL"
100  InstanceLabelMuID: "MuID"
101  GEANTLabel: "edepconvert"
102  RawCaloHitLabel: "daqsipm"
103  RawMuIDHitLabel: "daqsipmmuid"
104  HitLabel: "hit"
105  CaloHitLabel: "sscalohit"
106  MuIDHitLabel: "sscalohitmuid"
107  TPCClusterLabel: "tpccluster"
108  TrackLabel: "track"
109  TrackTrajectoryLabel: "track"
110  VertexLabel: "vertex"
111  ClusterLabel: "calocluster"
112  MuIDClusterLabel: "caloclustermuid"
113  ECALAssnLabel: "trkecalassn"
114  VeeLabel: "veefinder1"
115 
116  POTSummaryLabel: "edepconvert" # leave blank to skip POTSummary
117 
118 # What to save? ==============================================
119 # MC info is: (a) MCTruth, GTruth, MCParticle if WriteMCinfo; (b) MCPtrajectory if
120 # (WriteMCPTrajectory && WriteMCinfo); and (c) MC info in calorimeter if
121 # (WriteMCCaloInfo && WriteMCinfo).
122 # Write momenta associated with MC trajectories only if the trajectory is also written
123  WriteMCinfo: true
124  WriteMCPTrajectory: false
125  WriteMCPTrajMomenta: false
126  WriteMCCaloInfo: true
127 # The origin of an MCParticle might be a short distance from the MCTrue interaction
128 # vertex - maybe it is a pi0, tau or charm produced in the interaction and decayed
129 # by GEANT. Count the MCParticle as from the vertex if it is less than this distance:
130  MatchMCPtoVertDist: 0.001
131 
132 # Tracking info is: (a) raw hits if WriteHits; (b) TPCClusters and the tracks that
133 # they are associated to if WriteTPCClusters; (c) the track info if WriteTracks (d)
134 # found vertices and their associations to track ends if (WriteVertices && WriteTracks).
135  WriteHits: false
136  WriteTPCClusters: true
137  WriteTracks: true
138  WriteTrackTrajectories: false
139  WriteVertices: true
140  WriteVees: true
141 
142 # Calorimetry info is: (a) calorimeter digits if WriteCaloDigits; (b) hits if
143 # WriteCaloHits; (c) clusters if WriteCaloClusters (d) associations to tracks if
144 # (WriteMatchedTracks && WriteCaloClusters && WriteTracks).
145  WriteMuID: true
146  WriteCaloDigits: false
147  WriteCaloHits: true
148  WriteCaloClusters: true
149  WriteMatchedTracks: true
150 
151 # dE/dx algorithms are still here in the analysis code; hence the IonizeTruncate
152 # parameter. Coherent pion analysis has some code here as well. WriteCohInfo
153 # also needs WriteMCinfo.
154  IonizTruncate: 1.00
155  WriteCohInfo: false
156 }
157 
158 standard_cafmaker_dayone:
159 {
160  module_type: CAFMaker
161 
162 # GeneratorLabels is a list of module labels for extracting MCTruth data products.
163 # If it is missing, then the CAFMaker module will look for all MCTruth data products
164 # in the event
165 
166 # GeneratorLabels: [ "generator" ]
167 
168 # the GENIEGeneratorLabels variable is a list of module labels for extracting GTruth data
169 # products, which are made only by GENIE. Often a generator module label will have to
170 # appear in GeneratorLabels and in GENIEGeneratorLabels if you want both kinds of
171 # information stored in the analysis tree. Omit this argument if you want CAFMaker_module
172 # to look for all GTruth data products in the event.
173 
174 # GENIEGeneratorLabels: [ "generator" ]
175 
176  InstanceLabelCalo: "TrackerSc"
177  InstanceLabelMuID: "MuID"
178  GEANTLabel: "geant"
179  RawCaloHitLabel: "daqsipm"
180  RawMuIDHitLabel: "daqsipmmuid"
181  HitLabel: "hit"
182  CaloHitLabel: "sscalohit"
183  MuIDHitLabel: "sscalohitmuid"
184  TPCClusterLabel: "dayone"
185  TrackLabel: "trackpass1"
186  TrackTrajectoryLabel: "trackpass1"
187  VertexLabel: "vertex"
188  ClusterLabel: "calocluster"
189  MuIDClusterLabel: "caloclustermuid"
190  ECALAssnLabel: "trkecalassn"
191  VeeLabel: "veefinder1"
192 
193  POTSummaryLabel: "edepconvert" # leave blank to skip POTSummary
194 
195 # What to save? ==============================================
196 # MC info is: (a) MCTruth, GTruth, MCParticle if WriteMCinfo; (b) MCPtrajectory if
197 # (WriteMCPTrajectory && WriteMCinfo); and (c) MC info in calorimeter if
198 # (WriteMCCaloInfo && WriteMCinfo).
199 # Write momenta associated with MC trajectories only if the trajectory is also written
200  WriteMCinfo: true
201  WriteMCPTrajectory: true
202  WriteMCPTrajMomenta: true
203  WriteMCCaloInfo: true
204 # The origin of an MCParticle might be a short distance from the MCTrue interaction
205 # vertex - maybe it is a pi0, tau or charm produced in the interaction and decayed
206 # by GEANT. Count the MCParticle as from the vertex if it is less than this distance:
207  MatchMCPtoVertDist: 0.001
208 
209 # Tracking info is: (a) raw hits if WriteHits; (b) TPCClusters and the tracks that
210 # they are associated to if WriteTPCClusters; (c) the track info if WriteTracks (d)
211 # found vertices and their associations to track ends if (WriteVertices && WriteTracks).
212  WriteHits: false
213  WriteTPCClusters: true
214  WriteTracks: true
215  WriteTrackTrajectories: true
216  WriteVertices: false
217  WriteVees: false
218 
219 # Calorimetry info is: (a) calorimeter digits if WriteCaloDigits; (b) hits if
220 # WriteCaloHits; (c) clusters if WriteCaloClusters (d) associations to tracks if
221 # (WriteMatchedTracks && WriteCaloClusters && WriteTracks).
222  WriteMuID: true
223  WriteCaloDigits: false
224  WriteCaloHits: false
225  WriteCaloClusters: false
226  WriteMatchedTracks: false
227 
228 # dE/dx algorithms are still here in the analysis code; hence the IonizeTruncate
229 # parameter. Coherent pion analysis has some code here as well. WriteCohInfo
230 # also needs WriteMCinfo.
231  IonizTruncate: 1.00
232  WriteCohInfo: false
233 }
234 
235 standard_cafmaker_dayone_edep:
236 {
237  module_type: CAFMaker
238 
239 # GeneratorLabels is a list of module labels for extracting MCTruth data products.
240 # If it is missing, then the CAFMaker module will look for all MCTruth data products
241 # in the event
242 
243 # GeneratorLabels: [ "generator" ]
244 
245 # the GENIEGeneratorLabels variable is a list of module labels for extracting GTruth data
246 # products, which are made only by GENIE. Often a generator module label will have to
247 # appear in GeneratorLabels and in GENIEGeneratorLabels if you want both kinds of
248 # information stored in the analysis tree. Omit this argument if you want CAFMaker_module
249 # to look for all GTruth data products in the event.
250 
251 # GENIEGeneratorLabels: [ "generator" ]
252 
253  InstanceLabelCalo: "TrackerSc"
254  InstanceLabelMuID: "MuID"
255  GEANTLabel: "edepconvert"
256  RawCaloHitLabel: "daqsipm"
257  RawMuIDHitLabel: "daqsipmmuid"
258  HitLabel: "hit"
259  CaloHitLabel: "sscalohit"
260  MuIDHitLabel: "sscalohitmuid"
261  TPCClusterLabel: "dayone"
262  TrackLabel: "trackpass1"
263  TrackTrajectoryLabel: "trackpass1"
264  VertexLabel: "vertex"
265  ClusterLabel: "calocluster"
266  MuIDClusterLabel: "caloclustermuid"
267  ECALAssnLabel: "trkecalassn"
268  VeeLabel: "veefinder1"
269 
270  POTSummaryLabel: "edepconvert" # leave blank to skip POTSummary
271 
272 # What to save? ==============================================
273 # MC info is: (a) MCTruth, GTruth, MCParticle if WriteMCinfo; (b) MCPtrajectory if
274 # (WriteMCPTrajectory && WriteMCinfo); and (c) MC info in calorimeter if
275 # (WriteMCCaloInfo && WriteMCinfo).
276 # Write momenta associated with MC trajectories only if the trajectory is also written
277  WriteMCinfo: true
278  WriteMCPTrajectory: true
279  WriteMCPTrajMomenta: true
280  WriteMCCaloInfo: true
281 # The origin of an MCParticle might be a short distance from the MCTrue interaction
282 # vertex - maybe it is a pi0, tau or charm produced in the interaction and decayed
283 # by GEANT. Count the MCParticle as from the vertex if it is less than this distance:
284  MatchMCPtoVertDist: 0.001
285 
286 # Tracking info is: (a) raw hits if WriteHits; (b) TPCClusters and the tracks that
287 # they are associated to if WriteTPCClusters; (c) the track info if WriteTracks (d)
288 # found vertices and their associations to track ends if (WriteVertices && WriteTracks).
289  WriteHits: false
290  WriteTPCClusters: true
291  WriteTracks: true
292  WriteTrackTrajectories: true
293  WriteVertices: false
294  WriteVees: false
295 
296 # Calorimetry info is: (a) calorimeter digits if WriteCaloDigits; (b) hits if
297 # WriteCaloHits; (c) clusters if WriteCaloClusters (d) associations to tracks if
298 # (WriteMatchedTracks && WriteCaloClusters && WriteTracks).
299  WriteMuID: true
300  WriteCaloDigits: false
301  WriteCaloHits: false
302  WriteCaloClusters: false
303  WriteMatchedTracks: false
304 
305 # dE/dx algorithms are still here in the analysis code; hence the IonizeTruncate
306 # parameter. Coherent pion analysis has some code here as well. WriteCohInfo
307 # also needs WriteMCinfo.
308  IonizTruncate: 1.00
309  WriteCohInfo: false
310 }
311 
312 END_PROLOG
Generated by   doxygen 1.8.11