prod4_gen_protoDUNE_beam_cosmics_datadriven_6GeV.fcl

Go to the documentation of this file.

#include "services_dune.fcl"
#include "singles_dune.fcl"
#include "corsika_protodune.fcl"
#include "protodunebeam.fcl"
#include "dune_radiological_model.fcl"

process_name: SinglesGen

services:
{
  # Load the service that manages root files for histograms.
  TFileService: { fileName: "gensingle_protoDUNE_hist.root" }
  TimeTracker:       @local::dune_time_tracker
  MemoryTracker:     @local::dune_memory_tracker
  RandomNumberGenerator: {} #ART native random number generator
  FileCatalogMetadata:  @local::art_file_catalog_mc
  @table::protodune_simulation_services
}

#Start each new event with an empty event.
source:
{
  module_type: EmptyEvent
  timestampPlugin: { plugin_type: "GeneratedEventTimestamp" }
  maxEvents:   10
  firstRun:    1           # Run number to use for this file
  firstEvent:  1           # number of first event in the file
}

# Define and configure some modules to do work on each event.
# First modules are defined; they are scheduled later.
# Modules are grouped by type.
physics:
{

 producers:
 {
   generator: @local::protodune_triggeredbeam
   cosmicgenerator: @local::protodune_corsika_cmc  
   ar39:  @local::protodunesp_39ar
   ar42:  @local::protodunesp_42ar
   kr85:  @local::protodunesp_85kr
   rn222: @local::protodunesp_222rn
 }


 #define the producer and filter modules for this path, order matters, 
 simulate: [ generator, cosmicgenerator, ar39, ar42, kr85, rn222 ]

 #define the output stream, there could be more than one if using filters 
 stream1:  [ out1 ]

 #trigger_paths is a keyword and contains the paths that modify the art::event, 
 #ie filters and producers
 trigger_paths: [simulate] 

 #end_paths is a keyword and contains the paths that do not modify the art::Event, 
 #ie analyzers and output streams.  these all run simultaneously
 end_paths:     [stream1]  
}

#block to define where the output goes.  if you defined a filter in the physics
#block and put it in the trigger_paths then you need to put a SelectEvents: {SelectEvents: [XXX]}
#entry in the output stream you want those to go to, where XXX is the label of the filter module(s)
outputs:
{
 out1:
 {
   module_type: RootOutput
   fileName:    "gensingle_protoDUNE.root" #default file name, can override from command line with -o or --output
   dataTier: "generated"
   compressionLevel: 1
 }
}

# Specific to the GEANT H4 Beam simulation by Nikos and paths at CERN
physics.producers.generator.GoodParticleTreeName: "NTuples/GoodParticle"
physics.producers.generator.AllParticlesTreeName: "Detector/NP04front" # Background particles should fire from here
physics.producers.generator.FileName: "/pnfs/dune/persistent/dunepro/beam_data/simulation/G4beamlineVersion3.06/v34b_6GeV_G4beamlineVersion3.06/H4_v34b_6GeV_-27.7_10M_1.root"
physics.producers.generator.StartEvent: 0 ## Needs to be iterated for each set of events available in the file above


## This block controls the datadriven primary generator. 
physics.producers.generator.SamplingFileName:   "EventGenerator/ProtoDUNE_DataDrivenBeam/6GeV_PDF.root"
physics.producers.generator.ResolutionFileName: "EventGenerator/ProtoDUNE_DataDrivenBeam/6GeV_res.root" 
physics.producers.generator.NominalP: "6" ## Determines how things are set up on the data driven side
                                          ## Options are "0.5" "1" "2" "3" "6" "7" (all strings)
physics.producers.generator.UseDataDrivenPrimary: true 

## Specific .fcl for the +6 GeV/c momentum setting
services.TFileService.fileName: "gen_protoDune_beam_p6GeV_cosmics_datadriven_hist.root"
outputs.out1.fileName: "gen_protoDune_beam_p6GeV_cosmics_datadriven.root"