Creating a DST with both detector and Reco information

Creating a DST with both detector and Reco information

This is not a guide on how to run Reco, if you want to find out how to run Reco click here.

DATA

When Reco is run on raw data by default all the detector information and some lower level Reco information (1D SMT Hits for example) is discarded to save space. However, when running the level 3 tracking comparison programs you need the Reco data, the detector data (to run the trigger simulation on) and the low level Reco information. It is therefore necessary to run Reco locally on some raw data to keep all this discarded information. To keep all this data you have to run d0reco with a local copy of the rcps with the following modifications.

1 d0reco/rcp/reco_write_data.rcp

Remove the object rdcdistill from string Packages. This will stop the raw data chunk from being cut down to only L1/L2 information. An example altered version can be found here.

2 d0reco/rcp/D0recoWriteEvent.rcp

Remove all items in the string VetoClassList you wish to keep in the DST. For the more advanced track matching program removing all classes with SMT and CFT in the name will be sufficient. An example altered version can be found here.

Make sure that you have plenty of space on disk to save the output, it will typically take up twice the space then just the raw data chunk would.

When Reco is run on MC by default the full raw data chunk is kept, so only the second step needs implementing.

If you want to run on MC which has already been reprocessed you should select the data=mc_reprocess command with the runreco command, this will drop the original Reco chunks and allow the MC to be reprocessed.