Difference: RunningOnData (2 vs. 3)

Revision 32010-11-10 - NickEdwards

Line: 1 to 1

META TOPICPARENT	name="Main.NickEdwards"

Running on Real Data

Line: 18 to 18

When you execute the command, prun creates an archive of all of the files in the working directory and below (excluding object files, root files, files over 1048576B and possibly binaries. You can override this with --extFile). These files are sent to the Worker nodes. The --exec flag tells prun what command to execute (or a ; separated list of commands). The %IN gives a comma separated list of the input files (e.g. "file1.root,file2.root"). --inDS specifies the input dataset. --outputs should be a comma separated list of the files that you want returned to you in the output dataset. --outDS specifies the output dataset name and should be in the form user...

Changed:

<
<

The last flags are optional: --athenaTag 15.6.9 sets up an athena release on the worker nodes (~~I needed to use this to get ROOT to see the input files~~ Not necessary for this). --useAthenaPackages let's the worker nodes access Athena packages and --nFiles specifies how many files out of the dataset to use.

>
>

The last flags are optional: --athenaTag 15.6.9 sets up an athena release on the worker nodes. This is the simplest way to get root set up correctly on the worker node. (~~I needed to use this to get ROOT to see the input files~~ Not necessary for this). --useAthenaPackages let's the worker nodes access Athena packages and --nFiles specifies how many files out of the dataset to use.

This is all well and good, but if you have a GoodRunList and want to run over all the evnts in it, you're going to have to find the dataset names for all of the runs in the GRL, and then submit separate prun jobs for each of them. But wait... prun is cleverer than it looks:

View topic | History: r3 < r2 < r1 | More topic actions...