Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
...
The filenames will be of the form: <expname>_Run<runnr>.h5
Setup and automatic production
During the experiment we will produce the smallData files automatically. Since Run 18, we are using the Automatic Run Processing for that. During experimental setup, we usually take test runs of the appropriate length to set up production to finish close to the end of run. Jobs can be rerun and stopped. The job will print out where is it. We can set up a second job, started when the hdf5 production is done that can either make data quality plots or produce the binned data.
While the processing is generally done from the elog (ARP), if you would like to run an interactive test job with only a few events, you can use:./arp_scripts/submit_smd.sh -r <#> -e <experiment_name> --nevents <#> --interactive
The full list of options is here:
Code Block | ||||
---|---|---|---|---|
| ||||
(ana-4.0.30-py3) -bash-4.2$ ./arp_scripts/submit_smd.sh -h
submit_smd.sh:
Script to launch a smalldata_tools run analysis
OPTIONS:
-h|--help
Definition of options
-e|--experiment
Experiment name (i.e. cxilr6716)
-r|--run
Run Number
-d|--directory
Full path to directory for output file
-n|--nevents
Number of events to analyze
-q|--queue
Queue to use on SLURM
-c|--cores
Number of cores to be utilized
-f|--full
If specified, translate everything
-D|--default
If specified, translate only smalldata
-i|--image
If specified, translate everything & save area detectors as images
--norecorder
If specified, don't use recorder data
--nparallel
Number of processes per node
--postTrigger
Post that primary processing done to elog to seconndary jobs can start
--interactive
Run the process live w/o batch system |
Setup and automatic production
During the experiment we will produce the smallData files automatically. Since Run 18, we are using the Automatic Run Processing for that. During experimental setup, we usually take test runs of the appropriate length to set up production to finish close to the end of run. Jobs can be rerun and stopped. The job will print out where is it. We can set up a second job, started when the hdf5 production is done that can either make data quality plots or produce the binned data.Overview
Content Tools