@@ -104,8 +104,29 @@ If you have changed any scripts or code, you must redo this.
104104
105105will take a while, produce a tarball on ` /exp/dune/data/users/$USER/ ` and put the cvmfs location in cvmfs.location in ` $DIRECTORY `
106106
107+ ### Configure your job with job_config.sh
108+
107109Then edit ` job_config.sh ` to reflect the # of events you want and other run-time parameters.
108110
111+ #### Details of job_config.sh
112+
113+ Here is what is in job_config.sh
114+ ~~~
115+ {% include job_config.sh %}
116+ ~~~
117+
118+ - ` FCL_FILE ` = the top level fcl file - assumes it is in DIRECTORY or in the ` PHICL_FILE_PATH `
119+ - ` OUTPUT_DATA_TIER1 ` data_tier for artroot output (full-reconstructed, ...)
120+ - ` OUTPUT_DATA_TIER2 ` data_tier for root output - normally plain root-tuple
121+ - ` MQL ` Metacat query that you wish to run over
122+ - ` APP_TAG ` this is a tag that goes into the output filename, like reco2, ana ...
123+ - ` DESCRIPTION ` the jobname that shows up in justIN
124+ - ` USERF ` make certain the grid knows who your are without overwriting whatever internal ` USER ` it has
125+ - ` NUM_EVENTS ` the ` -n ` argument of larsoft
126+ - ` FNALURL ` sends output to subdirectories of your area on scratch
127+ - ` NAMESPACE ` rucio/metacat namespace for your output, normally ` usertests ` or possibly your username or physics group unless you are doing production.
128+
129+
109130### Test your jobscript interactively
110131
111132[ test_workflow.sh] ( https://github.com/hschellman/computing-basics-batch-devel/blob/gh-pages/_includes/test_workflow.sh )
@@ -140,9 +161,3 @@ You should get a workflow number back
140161go to [ justin] ( https://dunejustin.fnal.gov/dashboard/?method=list-workflows )
141162
142163to track your job.
143-
144- [ internal link] ( /files/setup-grid )
145-
146-
147-
148-
0 commit comments