1 # microboone_optical_sim.fcl
2 # Prepared July-2013 by William Seligman <seligman@nevis.columbia.edu>
4 # This is an example job for running the MicroBooNE PMT ADC and FEM simulation.
5 # The input file can come from any standard detector-simulation job
6 # that includes a LArG4 (largeant) step. The output will include digitized,
7 # discriminated, and triggered PMT ADC counts; see the OpticalDetectorData
8 # package for the data products added to the event.
10 #include "services_microboone.fcl"
17 # Load the service that manages root files for histograms.
18 TFileService: {
fileName:
"opt_sim_hist.root" }
22 # message: @local::standard_debug # If you turn this on, uncomment the debug lines below
23 @table::microboone_services
26 # If I want to see all the LogDebug messages from this program.
27 #services.message.destinations.debugmsg.filename: "debug-fem.log"
28 #services.message.destinations.debugmsg.categories.default.limit: 10000
29 #services.message.destinations.debugmsg.categories.default.reportEvery: 1
31 # Needed for the OpDigiProperties service and other digitizer parameters
32 # Pick the "Nwindows" version to match the detector simulation.
33 services.OpDigiProperties: @local::microboone_opdigiproperties
34 #services.OpDigiProperties: @local::microboone_opdigiproperties_3windows
40 # Deliberately commented out, so you have to supply the input file
41 # with a "lar -c" option.
42 # fileNames: [ "simulation.root" ]
45 # Define and configure some modules to do work on each event.
46 # First modules are defined; they are scheduled later.
47 # Modules are grouped by type.
53 optdigitizer: @local::microboone_optdetdigitizer
54 optreadout: @local::microboone_optical_readout
59 #define the output stream, there could be more than one if using filters
62 #trigger_paths is a keyword and contains the paths that modify the art::event,
63 #ie filters and producers
66 #end_paths is a keyword and contains the paths that do not modify the art::Event,
67 #ie analyzers and output streams. these all run simultaneously
71 #block to define where the output goes. if you defined a filter in the physics
72 #block and put it in the trigger_paths then you need to put a SelectEvents: {SelectEvents: [XXX]}
73 #entry in the output stream you want those to go to, where XXX is the label of the filter module(s)
services RandomNumberGenerator
BEGIN_PROLOG triggeremu_data_config_icarus settings PMTADCthresholds sequence::icarus_stage0_multiTPC_TPC physics sequence::icarus_stage0_EastHits_TPC physics sequence::icarus_stage0_WestHits_TPC physics producers purityana0 caloskimCalorimetryCryoE physics caloskimCalorimetryCryoW physics sequence::physics pathW services
process_name drop raw::OpDetWaveforms_DataApr2016RecoStage1_saturation_ * physics
physics producers trigslidewindowOR6mW physics effSlidingOR6mW physics end_paths
process_name can override from command line with o or output dataTier
source drop raw::ubdaqSoftwareTriggerData_ *_ *_ * maxEvents
BEGIN_PROLOG triggeremu_data_config_icarus settings PMTADCthresholds sequence::icarus_stage0_multiTPC_TPC physics sequence::icarus_stage0_EastHits_TPC physics sequence::icarus_stage0_WestHits_TPC physics producers purityana0 module_type
services TFileService fileName
BEGIN_PROLOG sequence::SlidingWindowTriggerPatternsOppositeWindows END_PROLOG simSlidingORM6O6 effSlidingORW output
standard_singlep gaussian distribution ie ie ie gaussian gaussian gaussian larg4Main stream1
process_name showerreco Particles Coinciding wih the Vertex services ScanOptions nu_mu services ScanOptions Number
BEGIN_PROLOG sequence::SlidingWindowTriggerPatternsWindowPair END_PROLOG trigslidewindowOR6m output outputs
process_name sequence::icarus_reco_cluster3d physics trigger_paths
BEGIN_PROLOG sequence::SlidingWindowTriggerPatternsOppositeWindows END_PROLOG process_name