run_filter.fcl
Go to the documentation of this file.
1 #NuTools Services
2 #include "magfield.fcl"
3 #include "seedservice.fcl"
4 
5 #GArSoft Services
6 #include "DetectorClocks.fcl"
7 #include "DetectorProperties.fcl"
8 #include "GArProperties.fcl"
9 #include "ECALProperties.fcl"
10 #include "Geometry.fcl"
11 #include "RunHistory.fcl"
12 #include "BackTracker.fcl"
13 
14 #Filters
15 #include "Filters.fcl"
16 
17 process_name: Filtering
18 
19 services:
20 {
21 # Load the service that manages root files for histograms.
22 TFileService: { fileName: "readoutsim_hist.root" }
23 TimeTracker: {}
24 RandomNumberGenerator: {} #ART native random number generator
25 GeometryGAr: @local::nd_hall_mpd_only_SPYv2_geo
26 ExptGeoHelperInterface: @local::standard_geometry_helper
27 DetectorClocks: @local::standard_clocks
28 DetectorProperties: @local::standard_detproperties
29 GArProperties: @local::standard_garproperties
30 ECALProperties: @local::standard_ecalproperties
31 NuRandomService: @local::standard_NuRandomService
32 MagneticField: @local::standard_mag_garsoft
33 #BackTracker: @local::standard_backtracker
34 #RunHistory: @local::standard_runhistory
35 }
36 
37 
38 #Start each new event with an empty event.
39 source:
40 {
41 module_type: RootInput
42 }
43 
44 # Define and configure some modules to do work on each event.
45 # First modules are defined; they are scheduled later.
46 # Modules are grouped by type.
47 physics:
48 {
49 filters:
50 {
51 fsp: @local::standard_fspevtfilter
52 }
53 producers:
54 {
55 
56 }
57 analyzers:
58 {
59 
60 }
61 
62 #define the producer and filter modules for this path, order matters,
63 #filters reject all following items. see lines starting physics.producers below
64 simulate: [ fsp ]
65 
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: [ simulate ]
72 
73 end_paths: [ stream1 ]
74 }
75 
76 #block to define where the output goes. if you defined a filter in the physics
77 #block and put it in the trigger_paths then you need to put a SelectEvents: {SelectEvents: [XXX]}
78 #entry in the output stream you want those to go to, where XXX is the label of the filter module(s)
79 outputs:
80 {
81 out1:
82 {
83 module_type: RootOutput
84 fileName: "readoutsim.root" #default file name, can override from command line with -o or --output
85 SelectEvents: [ simulate ]
86 }
87 }