Configure Skim Modes

Configure Skim Modes#

The method for the configuration of skim modes in VIBE is very similar to the one for analysis modes as detailed in Mode Configuration.

Similar to the analysis mode the configuration has to be placed with the same name in the directory where the skim mode is defined. In contrast to the analysis mode configuration, where a [dataset_dict] has to be given, for skimming a [skim_dataset_dict] has to be provided. This is due the fact that VIBE is able to run the full skim analysis workflow, what will become the inputs of [dataset_dict] does not actually exist yet. If we look back to our example workflow diagram:

../_images/skim_validation_pipeline.png

The first two tasks on the far left are submitting skim projects to the grid using the SkimAttributes that were introduced in Skimming in VIBE. The datasets that are produced from this first set of tasks, known as SkimProductionNtupleProductionTask’s will become the input for the AnalysisNtupleProductionTask’s upstream in the workflow. VIBE will dynamically update the respective configuration file with the new datasets under the key [dataset_dict] along with any parameters set in AnalysisParameters inside of SkimAttributes during run time. Then when the AnalysisNtupleProductionTask’s are ran, all the information required will be present and it can submit the basf2 path defined in the method create_basf2_path of your skim production mode for the validation step of VIBE.

A minimal skim configuration looks like this:

[skim_dataset_dict]
    [skim_dataset_dict.charged]
    lpn = "/path/to/charged/MC/dataset/on/grid"

    [skim_dataset_dict.mixed]
    lpn = "/path/to/mixed/MC/dataset/on/grid"

Note

For more detailed insight into skimming in VIBE check out Skimming Expert Info Dump