Project

General

Profile

Running Jobs » History » Version 10

Gianluca Petrillo, 01/22/2016 09:39 AM

1 1 Erica Snider
{{toc}}
2 1 Erica Snider
3 1 Erica Snider
Under construction... NOT YET A SOURCE OF INFORMATION!!
4 1 Erica Snider
5 3 Gianluca Petrillo
6 1 Erica Snider
h1. Running Jobs
7 1 Erica Snider
8 9 Gianluca Petrillo
This page describes the job configuration file (often, in jargon: _FHiCL file_) and how to run a job using one.
9 1 Erica Snider
10 3 Gianluca Petrillo
It is assumed that you have previously read the [[ Quick-start guide to using and developing LArSoft code ]] and the information on [[Using LArSoft on the GPVM nodes]].
11 1 Erica Snider
12 1 Erica Snider
13 9 Gianluca Petrillo
h2. The Job Configuration File
14 1 Erica Snider
15 9 Gianluca Petrillo
Once a base release is set up, it is easy to run a job. The basic unit for running a job is the job-control script, written in the FHICL language. The FHICL language provides a simple mechanism for including parameter set configurations from different files such that many job configuration files can use the same configuration for a module or service.  
16 1 Erica Snider
17 10 Gianluca Petrillo
There is also a nice "FHiCL quick start guide":https://cdcvs.fnal.gov/redmine/attachments/16021/quick_start.pdf available for more details. 
18 2 Lynn Garren
19 3 Gianluca Petrillo
20 10 Gianluca Petrillo
h3. Key Concepts in FHiCL
21 1 Erica Snider
22 1 Erica Snider
There are a few key concepts to writing a FHICL job control script.  In order, they are
23 1 Erica Snider
24 1 Erica Snider
# Including previously defined configurations for services and modules from other files.  This is done using @#include@ statements. *Be sure you don't have any trailing space or tab characters* on the @#include@ line.
25 9 Gianluca Petrillo
# Service block, denoted by @services: { }@  This block will contain configurations for ART specific services such as the @TFileService@ and the @RandomNumberGenerator@.  It also contains the configuration of LArSoft specific services[1].
26 9 Gianluca Petrillo
# Source block, denoted by @source: { }@.  This block tells the job what kind of source to expect (@EmptyEvent@ in the case of Monte Carlo generation, @RootInput@ in the case of anything downstream of a Monte Carlo generator or reconstruction, and specific modules for data from the detector), the file name for the input source if appropriate, and how many events to process.  Both the file name and number of events to process can be specified on the command line.
27 9 Gianluca Petrillo
# Output block, denoted by @outputs: { }@  This block tells the job what kind of output to make, i.e. @RootOutput@, and what the name of the output file should be.  The output file name can be specified on the command line.  It is possible to define more than one output file if one wanted to run a job that produced different output files based on filter criteria - i.e. empty events are put in one file and events with neutrinos in them are put in another. Multiple output files can only be specified in the job configuration file, not from the command line.
28 9 Gianluca Petrillo
# Physics block, denoted by @physics: { }@  This block is where all producer, analyzer, and filter modules are configured.  Sequences of producer and filter modules to run is defined in user-named _paths_ in this block.  The list of analyzers and output modules to run is defined in a separate user-named path.  The block also defines two keyword parameters, @trigger_paths@ and @end_paths@.  @trigger_paths@ contains all producer and filter paths to run, and @end_paths@ contains the analyzer and output path.
29 3 Gianluca Petrillo
30 10 Gianluca Petrillo
Comments may be included in FHiCL configuration files using the "#" character.  The @#include@ is a keyword so that the parser knows not to ignore what comes after "#include[2]".
31 9 Gianluca Petrillo
32 9 Gianluca Petrillo
fn1. In old FHiCL files you will notice that LArSoft and in general non-art service configuration is enclosed in a @user@ block, that is now deprecated.
33 9 Gianluca Petrillo
34 9 Gianluca Petrillo
fn2. Note that the FHiCL parser can't recognize a comment on the same line as a @#include@ directive.
35 1 Erica Snider
36 3 Gianluca Petrillo
37 10 Gianluca Petrillo
h3. FHiCL Rules
38 1 Erica Snider
39 10 Gianluca Petrillo
There are a few of rules to keep in mind about FHiCL:
40 10 Gianluca Petrillo
* The value of the @process_name@ parameter may not contain underscores as the process name is used in the ROOT file branch name.  Module labels may not contain underscores either, for the same reason.
41 1 Erica Snider
* Parameter set names may not contain numbers, periods, backslashes, stars, etc. They may contain underscores.
42 3 Gianluca Petrillo
* Put the values for all string parameters in double quotes, @"..."@
43 3 Gianluca Petrillo
* Specify input vectors using @[ , , ]@, i.e. if you want a vector of doubles do @MyVector: [1.0, 3e-9, -900.]@
44 10 Gianluca Petrillo
* You pick out configurations from the @PROLOG@ section(s), usually defined in the @#include@ files, using the @ @local::@ syntax.  The value after the "@::@" is the name of the configuration specified in the @PROLOG@ (see the next bullet)
45 3 Gianluca Petrillo
* You can override the value of an included configuration. For example, imagine there is a configuration specified in a included file called @mymoduleconfig@ and it contains the value @-5@ for the parameter named @myint@. One can load the configuration and then change the value of @myint@ by doing the following:
46 3 Gianluca Petrillo
*# inside the producers block:
47 1 Erica Snider
<pre>
48 3 Gianluca Petrillo
physics: {
49 3 Gianluca Petrillo
  producers: {
50 3 Gianluca Petrillo
    # ...
51 3 Gianluca Petrillo
    mymod: @local::mymoduleconfig
52 3 Gianluca Petrillo
  }
53 3 Gianluca Petrillo
}
54 3 Gianluca Petrillo
</pre>
55 3 Gianluca Petrillo
*# out of the physics block 
56 3 Gianluca Petrillo
<pre>
57 1 Erica Snider
physics.producer.mymod.myint: 1
58 1 Erica Snider
</pre>
59 3 Gianluca Petrillo
The last value for a parameter always wins. If the second line was repeated with the value @2@ instead of @1@, the job would run with @myint@ as @2@.
60 3 Gianluca Petrillo
Also note that in the example the original content of @mymoduleconfig@ is not changed when the content of @mymod@ is.
61 3 Gianluca Petrillo
62 1 Erica Snider
63 6 Gianluca Petrillo
h3. Example configuration file: @detsimmodules.fcl@
64 6 Gianluca Petrillo
65 6 Gianluca Petrillo
An example of a file with predefined configurations for modules is in the "larsim/DetSim/detsimmodules.fcl":https://cdcvs.fnal.gov/redmine/projects/larsim/repository/revisions/develop/entry/DetSim/detsimmodules.fcl file.
66 6 Gianluca Petrillo
All the definitions are inside a prologue block.
67 6 Gianluca Petrillo
The following is taken from LArSoft @v02_03_01@ (experiments now use their specific @detsimmodule_Xxxx.fcl@ configuration file though):
68 6 Gianluca Petrillo
69 6 Gianluca Petrillo
<pre>
70 6 Gianluca Petrillo
###### All files that are parameter set definitions must contain BEGIN_PROLOG as their first line ######
71 6 Gianluca Petrillo
###### This tag tells the FHICL parser that parameter set definitions are coming                  ######
72 6 Gianluca Petrillo
BEGIN_PROLOG
73 6 Gianluca Petrillo
74 6 Gianluca Petrillo
75 6 Gianluca Petrillo
###### Generic configuration of the analyser for SimWireXxxx producer output ######
76 6 Gianluca Petrillo
standard_simwireana:
77 6 Gianluca Petrillo
{ 
78 6 Gianluca Petrillo
 module_type:       "SimWireAna"
79 6 Gianluca Petrillo
 DetSimModuleLabel: "daq"
80 6 Gianluca Petrillo
}
81 6 Gianluca Petrillo
82 6 Gianluca Petrillo
###### Configuration of the SimWire module (digitization) for ArgoNeuT ######
83 6 Gianluca Petrillo
# extra comment to test check-in
84 6 Gianluca Petrillo
argoneut_simwire:
85 6 Gianluca Petrillo
{ 
86 6 Gianluca Petrillo
 module_type:        "SimWireT962"
87 6 Gianluca Petrillo
 DriftEModuleLabel:  "largeant"
88 6 Gianluca Petrillo
 ResponseFile:       "shape-argo.root"
89 6 Gianluca Petrillo
 NoiseFact:          0.132        #Noise Scale
90 6 Gianluca Petrillo
 NoiseWidth:         62.4         #Exponential Noise width (kHz)
91 6 Gianluca Petrillo
 LowCutoff:          7.5          #Low frequency filter cutoff (kHz)
92 6 Gianluca Petrillo
 FieldBins:          75
93 6 Gianluca Petrillo
 Col3DCorrection:    2.5
94 6 Gianluca Petrillo
 Ind3DCorrection:    1.5
95 6 Gianluca Petrillo
 ColFieldRespAmp:    0.0354
96 6 Gianluca Petrillo
 IndFieldRespAmp:    0.018
97 6 Gianluca Petrillo
 ShapeTimeConst:     [ 3000., 900. ]
98 6 Gianluca Petrillo
 CompressionType:    "none"        #could also be Huffman
99 6 Gianluca Petrillo
}
100 6 Gianluca Petrillo
###### Configuration of the analyser for SimWireXxxx output for ArgoNeuT (copy of generic) ######
101 6 Gianluca Petrillo
argoneut_simwireana: @local::standard_simwireana
102 6 Gianluca Petrillo
103 6 Gianluca Petrillo
###### Configuration of the SimWire module (digitization) for MicroBooNE ######
104 6 Gianluca Petrillo
microboone_simwire:  
105 6 Gianluca Petrillo
{ 
106 6 Gianluca Petrillo
 module_type:        "SimWireMicroBooNE"
107 6 Gianluca Petrillo
 DriftEModuleLabel:  "largeant"
108 6 Gianluca Petrillo
 NoiseFact:          0.0132       #Noise Scale
109 6 Gianluca Petrillo
 #NoiseFact:          0.15       #Noise Scale to use with histogram
110 6 Gianluca Petrillo
 NoiseWidth:         62.4         #Exponential Noise width (kHz)
111 6 Gianluca Petrillo
 LowCutoff:          7.5          #Low frequency filter cutoff (kHz)
112 6 Gianluca Petrillo
 CompressionType:    "none"       #could also be none
113 6 Gianluca Petrillo
 GetNoiseFromHisto:   false  
114 6 Gianluca Petrillo
 NoiseFileFname:      "uboone_noise_v0.1.root"
115 6 Gianluca Petrillo
 NoiseHistoName:      "NoiseFreq"    
116 6 Gianluca Petrillo
117 6 Gianluca Petrillo
}
118 6 Gianluca Petrillo
###### Configuration of the analyser for SimWireXxxx output for MicroBooNE (copy of generic) ######
119 6 Gianluca Petrillo
microboone_simwireana: @local::standard_simwireana
120 6 Gianluca Petrillo
121 6 Gianluca Petrillo
122 6 Gianluca Petrillo
123 6 Gianluca Petrillo
124 6 Gianluca Petrillo
125 6 Gianluca Petrillo
###### Configuration of a different analyser for SimWireXxxx output, generic and experiment-specific ######
126 6 Gianluca Petrillo
standard_wienerfilterana: 
127 6 Gianluca Petrillo
{
128 6 Gianluca Petrillo
 module_type:        "WienerFilterAna"
129 6 Gianluca Petrillo
 DetSimModuleLabel:  "daq"
130 6 Gianluca Petrillo
}
131 6 Gianluca Petrillo
132 6 Gianluca Petrillo
bo_wienerfilterana:         @local::standard_wienerfilterana
133 6 Gianluca Petrillo
argoneut_wienerfilterana:   @local::standard_wienerfilterana
134 6 Gianluca Petrillo
microboone_wienerfilterana: @local::standard_wienerfilterana
135 6 Gianluca Petrillo
136 6 Gianluca Petrillo
137 6 Gianluca Petrillo
###### All files that are parameter set definitions must contain END_PROLOG as their last line ######
138 6 Gianluca Petrillo
###### This tag tells the FHICL parser that parameter set definitions are ended                ######
139 6 Gianluca Petrillo
END_PROLOG
140 6 Gianluca Petrillo
</pre>
141 6 Gianluca Petrillo
142 6 Gianluca Petrillo
143 5 Gianluca Petrillo
h3. Configuring the "message service":https://cdcvs.fnal.gov/redmine/projects/messagefacility/wiki/Using_MessageFacility#Using-MessageFacility
144 1 Erica Snider
145 4 Gianluca Petrillo
Several standard configurations for the message service are in "lardata/Utilities/messageservice.fcl":https://cdcvs.fnal.gov/redmine/projects/lardata/repository/revisions/develop/entry/Utilities/messageservice.fcl.  There is one configuration for each level of message output - Debug, Info, Warning, and Error.  These configurations will be applied to each message level that is specified and those of higher priority.  For example, the Info configuration will print out Info, Warning and Error level messages while the Warning configuration only print outs Warning and Error level messages. The "standard" debug configurations will cause the messages to go to a specified output file, @debug.log@. The Error configuration redirect to standard error stream (like @std::cerr@), while the others print into the standard output (@std::cout@). All impose some limits on the repetition of some frequent messages.
146 5 Gianluca Petrillo
Remember that to use one of these "standard" configurations you need to include it in your FCL file: they are standard, not default.
147 4 Gianluca Petrillo
If you want to define your own configuration, please take a look at the comments in "lardata/Utilities/messageservice.fcl":https://cdcvs.fnal.gov/redmine/projects/lardata/repository/revisions/develop/entry/Utilities/messageservice.fcl file to determine how to do so.  
148 1 Erica Snider
149 1 Erica Snider
Examples of how to include the usual use of the message service configurations are in the example files below.
150 1 Erica Snider
151 5 Gianluca Petrillo
To get a different level of output from just one module (say @DBSCAN@) one would do:
152 1 Erica Snider
153 1 Erica Snider
<pre>
154 1 Erica Snider
services:
155 1 Erica Snider
{
156 1 Erica Snider
  # Load the service that manages root files for histograms.
157 1 Erica Snider
  TFileService: { fileName: "reco_hist.root" }
158 1 Erica Snider
  Timing:       {}
159 1 Erica Snider
  RandomNumberGenerator: {} #ART native random number generator
160 1 Erica Snider
161 1 Erica Snider
  # configure the message service with the INFO for DBSCAN
162 1 Erica Snider
  # and WARNING level for everything else
163 1 Erica Snider
  message: { 
164 1 Erica Snider
    destinations: {  
165 1 Erica Snider
      infomsg: {
166 1 Erica Snider
        type: "cout"
167 1 Erica Snider
        threshold: "INFO"
168 1 Erica Snider
        append: true
169 1 Erica Snider
        category: {
170 1 Erica Snider
           DBSCAN: {
171 1 Erica Snider
             reportEvery: 1
172 1 Erica Snider
           }
173 1 Erica Snider
        }
174 1 Erica Snider
      }
175 1 Erica Snider
      warningmsg: {
176 1 Erica Snider
        type:      "cout"	
177 1 Erica Snider
        threshold: "WARNING"
178 1 Erica Snider
        append:    true        
179 1 Erica Snider
        categories: {
180 1 Erica Snider
          default: {
181 1 Erica Snider
            limit:       1000   
182 1 Erica Snider
            timespan:    60    
183 1 Erica Snider
          }
184 1 Erica Snider
        } # end categories
185 1 Erica Snider
      } # end warningmsg
186 1 Erica Snider
    } # end destinations
187 1 Erica Snider
  } # end standard_warning
188 1 Erica Snider
189 1 Erica Snider
  user:         @local::argoneut_services 	     
190 1 Erica Snider
}
191 1 Erica Snider
</pre>
192 1 Erica Snider
193 1 Erica Snider
194 5 Gianluca Petrillo
h3. Example job script: @prodgenie.fcl@
195 1 Erica Snider
196 5 Gianluca Petrillo
An example job script to produce Monte Carlo events is "larsim/EventGenerator/GENIE/prodgenie.fcl":https://cdcvs.fnal.gov/redmine/projects/larsim/repository/revisions/develop/entry/EventGenerator/GENIE/prodgenie.fcl .  The job defined by this script will generate neutrino interactions using GENIE, run them through Geant4, do the electron transport and then simulate the electronics.
197 1 Erica Snider
198 1 Erica Snider
Comments on the form of the file are included as ###### Commment ######
199 1 Erica Snider
200 1 Erica Snider
<pre>
201 1 Erica Snider
###### This is how to include configurations from other files ######
202 5 Gianluca Petrillo
#include "services.fcl"
203 5 Gianluca Petrillo
#include "genie.fcl"
204 5 Gianluca Petrillo
#include "largeantmodules.fcl"
205 5 Gianluca Petrillo
#include "detsimmodules.fcl"
206 1 Erica Snider
207 1 Erica Snider
###### give the process a name ######
208 1 Erica Snider
process_name: GenieGen
209 1 Erica Snider
210 5 Gianluca Petrillo
###### Please note the convention of defining detector specific configurations                ######
211 1 Erica Snider
###### Pick out the configurations from the #include files using the @local:: syntax          ######
212 1 Erica Snider
###### for services from LArSoft, in the user{} block - see definitions for configurations in ######
213 1 Erica Snider
###### job/geometry.fcl                                                                       ######
214 1 Erica Snider
###### job/services.fcl                                                                       ######
215 5 Gianluca Petrillo
###### job/simulationservices.fcl                                                             ######
216 5 Gianluca Petrillo
217 5 Gianluca Petrillo
services:
218 1 Erica Snider
{
219 5 Gianluca Petrillo
  # Load the service that manages root files for histograms.
220 1 Erica Snider
  TFileService: { fileName: "genie_hist.root" }
221 1 Erica Snider
  Timing:       {}
222 5 Gianluca Petrillo
  SimpleMemoryCheck:     { ignoreTotal: 1 } # default is one
223 5 Gianluca Petrillo
  RandomNumberGenerator: {} #ART native random number generator
224 5 Gianluca Petrillo
  user:         @local::argoneut_simulation_services
225 1 Erica Snider
}
226 1 Erica Snider
227 1 Erica Snider
###### source is where you get events from - can also be RootInput ######
228 1 Erica Snider
#Start each new event with an empty event.
229 1 Erica Snider
source:
230 1 Erica Snider
{
231 1 Erica Snider
  module_type: EmptyEvent
232 1 Erica Snider
  maxEvents:   10          # Number of events to create
233 1 Erica Snider
  firstRun:    1           # Run number to use for this file
234 1 Erica Snider
  firstEvent:  1           # number of first event in the file
235 5 Gianluca Petrillo
}
236 1 Erica Snider
237 1 Erica Snider
###### physics is the block that controls configuration of modules ######
238 5 Gianluca Petrillo
# Define and configure some modules to do work on each event.
239 1 Erica Snider
# First modules are defined; they are scheduled later.
240 5 Gianluca Petrillo
# Modules are grouped by type.
241 5 Gianluca Petrillo
physics:
242 1 Erica Snider
{
243 1 Erica Snider
244 1 Erica Snider
 ###### the module labels in the output file will be generator, largeant, and daq ######
245 1 Erica Snider
 ###### their configuration is taken from ArgoNeuT defaults                       ######
246 1 Erica Snider
 producers:
247 1 Erica Snider
 {
248 1 Erica Snider
   generator: @local::argoneut_genie_simple_neutrino
249 5 Gianluca Petrillo
   largeant:  @local::argoneut_largeant	       
250 1 Erica Snider
   daq:       @local::argoneut_simwire         
251 1 Erica Snider
   rns:       { module_type: "RandomNumberSaver" }
252 1 Erica Snider
 }
253 1 Erica Snider
254 1 Erica Snider
 #define the producer and filter modules for this path, order matters, 
255 1 Erica Snider
 #filters reject all following items.  see lines starting physics.producers below
256 1 Erica Snider
 simulate: [ rns, generator, largeant, daq, ] 
257 1 Erica Snider
 
258 1 Erica Snider
 #define the output stream, there could be more than one if using filters 
259 1 Erica Snider
 stream1:  [ out1 ]
260 1 Erica Snider
261 1 Erica Snider
 #trigger_paths is a keyword and contains the paths that modify the art::event, 
262 1 Erica Snider
 #ie filters and producers
263 1 Erica Snider
 trigger_paths: [simulate] 
264 1 Erica Snider
265 5 Gianluca Petrillo
 #end_paths is a keyword and contains the paths that do not modify the art::Event, 
266 1 Erica Snider
 #ie analyzers and output streams.  these all run simultaneously
267 5 Gianluca Petrillo
 end_paths:     [stream1]  
268 5 Gianluca Petrillo
}
269 1 Erica Snider
270 1 Erica Snider
#block to define where the output goes.  if you defined a filter in the physics
271 1 Erica Snider
#block and put it in the trigger_paths then you need to put a SelectEvents: {SelectEvents: [XXX]}
272 1 Erica Snider
#entry in the output stream you want those to go to, where XXX is the label of the filter module(s)
273 1 Erica Snider
outputs:
274 1 Erica Snider
{
275 1 Erica Snider
 out1:
276 1 Erica Snider
 {
277 1 Erica Snider
   module_type: RootOutput
278 1 Erica Snider
   fileName:    "genie_gen.root" #default file name, can override from command line with -o or --output
279 1 Erica Snider
 }
280 1 Erica Snider
}
281 1 Erica Snider
282 1 Erica Snider
</pre>
283 1 Erica Snider
284 1 Erica Snider
Notice that you have not specified which libraries to load anywhere. That is because the build system compiles the plugin shared library files (@.so@) against the ones they depend upon.  
285 1 Erica Snider
286 1 Erica Snider
287 1 Erica Snider
h3. Example job script: @standard_reco.fcl@
288 1 Erica Snider
289 6 Gianluca Petrillo
There is an example reconstruction job script available for people to use, "lardata/Utilities/standard_reco":https://cdcvs.fnal.gov/redmine/projects/lardata/repository/revisions/develop/entry/Utilities/standard_reco.fcl .
290 6 Gianluca Petrillo
This script takes the output of either raw data or MC that has produced simulated raw digits and performs a list of reconstruction tasks.
291 6 Gianluca Petrillo
The version from LArSoft @v02_03_01@ is copied here:
292 1 Erica Snider
293 1 Erica Snider
<pre>
294 6 Gianluca Petrillo
#include "services.fcl"
295 6 Gianluca Petrillo
#include "caldata.fcl"
296 6 Gianluca Petrillo
#include "hitfindermodules.fcl"
297 6 Gianluca Petrillo
#include "clustermodules.fcl"
298 6 Gianluca Petrillo
#include "trackfindermodules.fcl"
299 1 Erica Snider
300 1 Erica Snider
process_name: Reco
301 1 Erica Snider
302 1 Erica Snider
services:
303 1 Erica Snider
{
304 1 Erica Snider
  # Load the service that manages root files for histograms.
305 1 Erica Snider
  TFileService: { fileName: "reco_hist.root" }
306 1 Erica Snider
  Timing:       {}
307 1 Erica Snider
  RandomNumberGenerator: {} #ART native random number generator
308 1 Erica Snider
  message:      @local::standard_warning
309 6 Gianluca Petrillo
  user:         @local::argoneut_services 	     
310 1 Erica Snider
}
311 1 Erica Snider
312 6 Gianluca Petrillo
313 1 Erica Snider
#source is now a root file
314 1 Erica Snider
source:
315 1 Erica Snider
{
316 1 Erica Snider
  module_type: RootInput
317 1 Erica Snider
  maxEvents:  10        # Number of events to create
318 1 Erica Snider
}
319 1 Erica Snider
320 1 Erica Snider
# Define and configure some modules to do work on each event.
321 1 Erica Snider
# First modules are defined; they are scheduled later.
322 1 Erica Snider
# Modules are grouped by type.
323 1 Erica Snider
physics:
324 1 Erica Snider
{
325 1 Erica Snider
326 1 Erica Snider
 producers:
327 1 Erica Snider
 {
328 6 Gianluca Petrillo
  caldata:    @local::argoneut_calwire	    
329 6 Gianluca Petrillo
  ffthit:     @local::argoneut_hitfinder # note if job is for MC, use argoneut_mc_hitfinder
330 6 Gianluca Petrillo
  dbcluster:  @local::argoneut_dbcluster	    
331 1 Erica Snider
  hough:      @local::argoneut_houghlinefinder
332 6 Gianluca Petrillo
  linemerger: @local::argoneut_linemerger	    
333 6 Gianluca Petrillo
  track:      @local::argoneut_track	    
334 6 Gianluca Petrillo
  harris:     @local::argoneut_endpointmod    
335 1 Erica Snider
 }
336 1 Erica Snider
337 6 Gianluca Petrillo
 analyzers:
338 6 Gianluca Petrillo
 {
339 6 Gianluca Petrillo
  dbclusterana: @local::argoneut_dbclusterana
340 6 Gianluca Petrillo
 }
341 6 Gianluca Petrillo
342 1 Erica Snider
 #define the producer and filter modules for this path, order matters, 
343 1 Erica Snider
 #filters reject all following items.  see lines starting physics.producers below
344 6 Gianluca Petrillo
 reco: [ caldata, ffthit, dbcluster, hough, linemerger, track, harris ] 
345 6 Gianluca Petrillo
 ana:  [ dbclusterana ]
346 6 Gianluca Petrillo
347 1 Erica Snider
 #define the output stream, there could be more than one if using filters 
348 1 Erica Snider
 stream1:  [ out1 ]
349 1 Erica Snider
350 1 Erica Snider
 #trigger_paths is a keyword and contains the paths that modify the art::event, 
351 1 Erica Snider
 #ie filters and producers
352 1 Erica Snider
 trigger_paths: [reco] 
353 1 Erica Snider
354 1 Erica Snider
 #end_paths is a keyword and contains the paths that do not modify the art::Event, 
355 1 Erica Snider
 #ie analyzers and output streams.  these all run simultaneously
356 6 Gianluca Petrillo
 end_paths:     [ ana, stream1]  
357 1 Erica Snider
}
358 1 Erica Snider
359 1 Erica Snider
#block to define where the output goes.  if you defined a filter in the physics
360 1 Erica Snider
#block and put it in the trigger_paths then you need to put a SelectEvents: {SelectEvents: [XXX]}
361 1 Erica Snider
#entry in the output stream you want those to go to, where XXX is the label of the filter module(s)
362 1 Erica Snider
outputs:
363 1 Erica Snider
{
364 1 Erica Snider
 out1:
365 1 Erica Snider
 {
366 1 Erica Snider
   module_type: RootOutput
367 1 Erica Snider
   fileName:    "standard_reco.root" #default file name, can override from command line with -o or --output
368 1 Erica Snider
 }
369 1 Erica Snider
}
370 1 Erica Snider
371 1 Erica Snider
</pre>
372 1 Erica Snider
373 7 Gianluca Petrillo
374 1 Erica Snider
h3. How to override a default parameter
375 1 Erica Snider
376 1 Erica Snider
If you want to override a default parameter that has been included from a predefined parameter set, you must specify which parameter and its value as
377 1 Erica Snider
378 7 Gianluca Petrillo
<pre>
379 1 Erica Snider
mainBlock.subBlock.label.parameterName: newValue
380 7 Gianluca Petrillo
</pre>
381 1 Erica Snider
382 1 Erica Snider
where 
383 1 Erica Snider
384 7 Gianluca Petrillo
* @mainBlock@ can be services or physics 
385 7 Gianluca Petrillo
* @subBlock@ can be user, producers, filters, or analyzers
386 7 Gianluca Petrillo
* @label@ is the name of the desired service or module in a producers, filters, or analyzers block
387 7 Gianluca Petrillo
* @parameterName@ is the name of the desired parameter
388 7 Gianluca Petrillo
* @newValue@ is the desired new value; lists or entire blocks (that is, a comma-separated list of @key: value@ pairs in braces) can be specified
389 1 Erica Snider
390 7 Gianluca Petrillo
These lines must go after the @mainBlock@ and be outside of any other block.
391 1 Erica Snider
392 7 Gianluca Petrillo
For example, if one wanted to change the default value of the @fhitsModuleLabel@ parameter in the @DBcluster@ module in the previous section, one would put
393 1 Erica Snider
394 7 Gianluca Petrillo
<pre>
395 1 Erica Snider
physics.producers.cluster.fhitsModuleLabel: "differentHitModuleLabel"
396 7 Gianluca Petrillo
</pre>
397 1 Erica Snider
398 7 Gianluca Petrillo
Note that FHiCL allows for completely replacing a value but not for changing it (e.g., it's not possible to add an element to an existing list).
399 1 Erica Snider
400 7 Gianluca Petrillo
401 1 Erica Snider
h3. fhicl Emacs syntax highlighting
402 1 Erica Snider
403 7 Gianluca Petrillo
If you use Emacs as your editor, you can put the following into your @.emacs@ file in your home directory to cause it to display @.fcl@ files with syntax highlighting
404 1 Erica Snider
405 1 Erica Snider
<pre>
406 1 Erica Snider
(setq fclKeywords
407 1 Erica Snider
'(
408 1 Erica Snider
  ;; This, due to poor language design, conflicts with comments and fails
409 1 Erica Snider
  ("#include" . font-lock-keyword-face)
410 1 Erica Snider
  ("@local" . font-lock-keyword-face)
411 1 Erica Snider
  ;; All these names are magic, I think
412 1 Erica Snider
413 1 Erica Snider
414 1 Erica Snider
("process_name:\\|services:\\|source:\\|outputs:\\|physics\\|producers:\\|filters:\\|analyzers:" . font-lock-builtin-face)
415 1 Erica Snider
  ("true\\|false" . font-lock-builtin-face)
416 1 Erica Snider
  ;; Variable definitions are followed by colons
417 1 Erica Snider
418 1 Erica Snider
  ("[a-zA-Z0-9_]*:" . font-lock-variable-name-face)
419 1 Erica Snider
 )
420 1 Erica Snider
)
421 1 Erica Snider
422 1 Erica Snider
;; Python mode gets us comment handling and indentation at colons
423 1 Erica Snider
424 1 Erica Snider
(define-derived-mode fcl-mode python-mode
425 1 Erica Snider
 (setq mode-name "FHICL")
426 1 Erica Snider
 (setq font-lock-defaults '(fclKeywords))
427 1 Erica Snider
;;  (setq tab-width 2) ;; Doesn't seem to work
428 1 Erica Snider
429 1 Erica Snider
)
430 1 Erica Snider
431 1 Erica Snider
(add-to-list 'auto-mode-alist '("\\.fcl\\'" . fcl-mode))
432 1 Erica Snider
</pre>
433 1 Erica Snider
434 7 Gianluca Petrillo
Also, please use _only spaces_ for alignment: it's not the perfect solution, but it makes people using different editors see the same code alignment.
435 7 Gianluca Petrillo
436 7 Gianluca Petrillo
437 1 Erica Snider
h2. Executable and command line options
438 1 Erica Snider
439 7 Gianluca Petrillo
Currently there is one executable to run in LArSoft. The executable to run a typical reconstruction or analysis job is @lar@ which is placed in the user's path by the setup script. To see what options are available do
440 7 Gianluca Petrillo
<pre>
441 7 Gianluca Petrillo
$ lar -h
442 7 Gianluca Petrillo
</pre>
443 7 Gianluca Petrillo
The output for @art@ version @v1_09_03@ is:
444 7 Gianluca Petrillo
<pre>
445 7 Gianluca Petrillo
Usage: lar <-c <config-file>> <other-options> [<source-file>]+
446 1 Erica Snider
447 7 Gianluca Petrillo
Allowed options:
448 7 Gianluca Petrillo
  -c [ --config ] arg           Configuration file.
449 7 Gianluca Petrillo
  -h [ --help ]                 produce help message
450 7 Gianluca Petrillo
  --process-name arg            art process name.
451 1 Erica Snider
452 7 Gianluca Petrillo
  -s [ --source ] arg           Source data file (multiple OK).
453 7 Gianluca Petrillo
  -S [ --source-list ] arg      file containing a list of source files to read,
454 7 Gianluca Petrillo
                                one per line.
455 7 Gianluca Petrillo
  -e [ --estart ] arg           Event # of first event to process.
456 7 Gianluca Petrillo
  -n [ --nevts ] arg            Number of events to process.
457 7 Gianluca Petrillo
  --nskip arg                   Number of events to skip.
458 7 Gianluca Petrillo
  -T [ --TFileName ] arg        File name for TFileService.
459 7 Gianluca Petrillo
  -o [ --output ] arg           Event output stream file.
460 7 Gianluca Petrillo
  --trace                       Activate tracing.
461 7 Gianluca Petrillo
  --notrace                     Deactivate tracing.
462 7 Gianluca Petrillo
  --memcheck                    Activate monitoring of memory use.
463 7 Gianluca Petrillo
  --nomemcheck                  Deactivate monitoring of memory use.
464 7 Gianluca Petrillo
  --default-exceptions          some exceptions may be handled differently by 
465 7 Gianluca Petrillo
                                default (e.g. ProductNotFound).
466 7 Gianluca Petrillo
  --rethrow-default             all exceptions default to rethrow.
467 7 Gianluca Petrillo
  --rethrow-all                 all exceptions overridden to rethrow (cf 
468 7 Gianluca Petrillo
                                rethrow-default).
469 7 Gianluca Petrillo
  --sam-web-uri arg             URI for SAM web service.
470 7 Gianluca Petrillo
  --sam-process-id arg          SAM process ID.
471 7 Gianluca Petrillo
  --sam-application-family arg  SAM application family.
472 7 Gianluca Petrillo
  --sam-app-family arg          SAM application family.
473 7 Gianluca Petrillo
  --sam-application-version arg SAM application version.
474 7 Gianluca Petrillo
  --sam-app-version arg         SAM application version.
475 7 Gianluca Petrillo
  --sam-file-type arg           File type for SAM metadata.
476 7 Gianluca Petrillo
  --sam-data-tier arg           SAM data tier spec (<module-label>:<tier-spec>)
477 7 Gianluca Petrillo
                                .
478 7 Gianluca Petrillo
  --sam-stream-name arg         SAM stream name (<module-label>:<stream-name>).
479 1 Erica Snider
480 7 Gianluca Petrillo
Art has completed and will exit with status 1.
481 7 Gianluca Petrillo
</pre>
482 1 Erica Snider
483 7 Gianluca Petrillo
484 1 Erica Snider
h2. Running a Job
485 1 Erica Snider
486 1 Erica Snider
To run the job defined by the script above, do
487 7 Gianluca Petrillo
<pre>
488 7 Gianluca Petrillo
$ lar -c job/prodgenie.fcl
489 7 Gianluca Petrillo
</pre>
490 1 Erica Snider
491 7 Gianluca Petrillo
One can stop a job in two ways:
492 7 Gianluca Petrillo
# press <Ctrl>+<C> once: the job will complete at the end of the current module. If the job is running in the background type @kill -9 %jobID@ on the command line.
493 7 Gianluca Petrillo
# press <Ctrl>+<C> twice: the job should stop immediately and, depending on the shall settings, might produce a core dump.
494 1 Erica Snider
495 7 Gianluca Petrillo
If you want to have your job keep running even if you get disconnected from a remote session, depending on your shell you might need to start it with:
496 7 Gianluca Petrillo
<pre>
497 7 Gianluca Petrillo
$ nohup lar job/prodgenie.fcl >& pg.out
498 7 Gianluca Petrillo
</pre>
499 1 Erica Snider
500 1 Erica Snider
To stop such a job, then do
501 7 Gianluca Petrillo
<pre>
502 7 Gianluca Petrillo
$ pgrep lar # to find the job ID (use ps to disambiguate if more than one lar process are running)
503 7 Gianluca Petrillo
$ kill -INT jobID
504 7 Gianluca Petrillo
</pre>
505 1 Erica Snider
506 7 Gianluca Petrillo
One can print out the configuration of the job without starting the executable by:
507 7 Gianluca Petrillo
<pre>
508 7 Gianluca Petrillo
$ ART_DEBUG_CONFIG=1 lar -c prodgenie.fcl
509 7 Gianluca Petrillo
</pre>
510 1 Erica Snider
in @bash@, or
511 7 Gianluca Petrillo
<pre>
512 7 Gianluca Petrillo
> env ART_DEBUG_CONFIG=1 lar -c prodgenie.fcl
513 7 Gianluca Petrillo
</pre>
514 7 Gianluca Petrillo
in C-shell, which produces the output
515 7 Gianluca Petrillo
<pre>
516 7 Gianluca Petrillo
** ART_DEBUG_CONFIG is defined: config debug output follows **
517 1 Erica Snider
all_modules: [ "out1"
518 1 Erica Snider
             , "daq"
519 1 Erica Snider
             , "generator"
520 1 Erica Snider
             , "largeant"
521 1 Erica Snider
             , "rns"
522 1 Erica Snider
             ]
523 1 Erica Snider
outputs: { out1: { fileName: "genie_gen.root"
524 1 Erica Snider
                   module_label: "out1"
525 1 Erica Snider
                   module_type: "RootOutput"
526 1 Erica Snider
                 }
527 1 Erica Snider
         }
528 1 Erica Snider
physics: { end_paths: [ "stream1" ]
529 1 Erica Snider
           producers: { daq: { Col3DCorrection: 2.5
530 1 Erica Snider
                               ColFieldRespAmp: 3.54e-2
531 1 Erica Snider
                               CompressionType: "none"
532 1 Erica Snider
                               DriftEModuleLabel: "largeant"
533 1 Erica Snider
                               FieldBins: 75
534 1 Erica Snider
                               Ind3DCorrection: 1.5
535 1 Erica Snider
                               IndFieldRespAmp: 1.8e-2
536 1 Erica Snider
                               LowCutoff: 7.5
537 1 Erica Snider
                               NoiseFact: 1.32e-1
538 1 Erica Snider
                               NoiseWidth: 6.24e1
539 1 Erica Snider
                               ResponseFile: "shape-argo.root"
540 1 Erica Snider
                               ShapeTimeConst: [ 3000
541 1 Erica Snider
                                               , 900
542 1 Erica Snider
                                               ]
543 1 Erica Snider
                               module_label: "daq"
544 1 Erica Snider
                               module_type: "SimWireT962"
545 1 Erica Snider
                             }
546 7 Gianluca Petrillo
                        generator: { BeamCenter: [ -1400
547 7 Gianluca Petrillo
                                                 , -350
548 1 Erica Snider
                                                 , 0
549 1 Erica Snider
                                                 ]
550 7 Gianluca Petrillo
[...]
551 1 Erica Snider
</pre>
552 1 Erica Snider
553 1 Erica Snider
This functionality is particularly helpful when trying to debug what input parameters were passed to the job.
554 1 Erica Snider
555 7 Gianluca Petrillo
556 1 Erica Snider
h2. Why did my job fail?
557 1 Erica Snider
558 8 Gianluca Petrillo
In case of failure, @art@ usually provides some information about the failure.
559 1 Erica Snider
560 8 Gianluca Petrillo
If a job fails, look at the warnings printed to the screen or any output log files.
561 1 Erica Snider
562 8 Gianluca Petrillo
Also check in the [[Breaking_Changes|breaking changes]] page for information about problems (and solutions) caused by changes to the code.
563 1 Erica Snider
564 8 Gianluca Petrillo
You can ask help to the larsoft@fnal.gov mailing list, or open a issue in the appropriate tracker (usually "the LArSoft one":https://cdcvs.fnal.gov/redmine/projects/larsoft/issues), or to artists@fnal.gov .
565 8 Gianluca Petrillo
The usual bug report rules apply: include at least
566 8 Gianluca Petrillo
* the full command line of the failing command
567 8 Gianluca Petrillo
* a full path to the input files
568 8 Gianluca Petrillo
* which LArSoft release you are using
569 8 Gianluca Petrillo
* the complete error message.
570 8 Gianluca Petrillo
571 8 Gianluca Petrillo
If a bug should be reported to the artists@fnal.gov list, attach the _complete output of the job_ to the email.
572 8 Gianluca Petrillo
573 8 Gianluca Petrillo
574 1 Erica Snider
h2. Submitting Jobs to the compute farms
575 1 Erica Snider
576 8 Gianluca Petrillo
We have to find out where the page with the submission instructions went (*TODO*!).