example_test_job.fcl
Go to the documentation of this file.
1 #include "services_dune.fcl"
2 #include "imagepatternalgs.fcl"
3 
4 # Example configuration of job file which can access CNN outputs
5 # produced for tracks / clusters / single hits and test the
6 # efficiency. Mudule can write out info to text file so you can
7 # plot results and MC truth.
8 # Configured for ProtoDUNE, hopefully straight-forward to adopt
9 # to other experiments.
10 
11 process_name: TestPointId
12 
13 services:
14 {
15  TFileService: { fileName: "reco_hist.root" }
16  MemoryTracker: {}
17  TimeTracker: {}
18  RandomNumberGenerator: {} #ART native random number generator
19  message: @local::dune_message_services_prod_debug
20  FileCatalogMetadata: @local::art_file_catalog_mc
21  @table::protodune_simulation_services
22 }
23 
24 source:
25 {
26  module_type: RootInput
27  maxEvents: -1 # Number of events to create
28 }
29 
30 physics:
31 {
32  analyzers:
33  {
34  # efficiency test, mostly on for EM vs track separation
35  testeff: @local::standard_pointidefftest
36  }
37  anatest: [ testeff ]
38 
39  trigger_paths: [ ]
40  end_paths: [ anatest ]
41 }
42 
43 physics.analyzers.testeff.NNetModuleLabel: "emtrkmichelid:emtrkmichel:RecoEm" # usually instance name is used in MVA data products, usually you can skip the process name
44 physics.analyzers.testeff.View: 2 # do the test in selected projection
45 physics.analyzers.testeff.SaveHitsFile: true # this will put to text file CNN output at hit positions
46