ap-utilities 0.1.4

Utilities needed for analysis productions in LHCb

ap_utilities

For documentation specific to MVA lines of the RD group, check this

Decay nicknames

Table with nicknames and event types

The following lines:

export DECPATH=/home/acampove/Packages/DecFiles

update_decinfo

will:

1. Set the path to the DecFiles root directory such that update_decinfo can use it.
2. Read the event types and nicknames and save them to a YAML file

Accessing table

These nicknames can be accessed from python scripts with:

import ap_utilities.physics.utilities as aput

# To get exactly what was saved
literal = aput.read_decay_name(event_type=event_type, style='literal')

# To get representation with special symbols like "," or "-" replaced
safe_1  = aput.read_decay_name(event_type=event_type, style= 'safe_1')

Check for samples existence

Given a set of MC samples specified in a YAML file like:

settings:
  year      : 2024
  mc_path   : 2024.W31.34
  polarity  : MagUp
  nu_path   : Nu6.3
  sim_vers  : Sim10d
  generator : Pythia8
  ctags     : sim10-2024.Q3.4-v1.3-mu100
  dtags     : dddb-20240427
event_type :
  - '12113002'
  - '12113004'
event_type_split_sim:
  # These event types are associated with two samples and should be saved twice in the text file
  - '11102202'
  - '11102211'

run:

check_samples -i samples.yaml -n 6

to check if the samples exist using 6 threads (default is 1) and store them in samples_found.yaml

To run this one has to be in an environment with:

1. Access to DIRAC.
2. A valid grid token.

Validate outputs of pipelines

In order to do this:

Mount EOS in laptop

# install SSHF
...
# Check that it's installed
which sshfs

# Make directory to mount EOS

APDIR=/eos/lhcb/wg/dpa/wp2/ci/
sudo mkdir -p $APDIR
sudo chown $USER:$USER $APDIR 

# Mount EOS
sshfs -o idmap=user [e-mail]:$MNT_DIR $MNT_DIR

Run Validation

# This project is in pip
pip install ap_utilities

validate_ap_tuples -p PIPELINE -f ntuple_scheme.yaml -t 5

where:
-l: Logging level, by default 20 (info), but it can be 10 (debug) or 30 (warning)
-t: Is the number of threads to use, if not passed, it will use one.
-p: Is the pipeline number, needed to find the ROOT files in EOS
-f: passes the file with the configuration

# -----------------------------------------
# Needed to find where files are in EOS
# -----------------------------------------
paths:
  pipeline_dir : /eos/lhcb/wg/dpa/wp2/ci
  analysis_dir : rd_ap_2024
# -----------------------------------------
# Each key corresponds to a MC sample, the value is a list of lines that must be found
# as a tree in the file. If any, then the sample is not signal for any of the HLT2 lines
# therefore no tree (equivalent to a line) is required to be made
# -----------------------------------------
samples:
  # These is a sample without a dedicated trigger
  Bu_K1ee_eq_DPC:
    - any 
  # This is a sample with two triggers targetting it
  Bd_Kpiee_eq_DPC:
    - Hlt2RD_B0ToKpPimEE
    - Hlt2RD_B0ToKpPimEE_MVA

a few examples of config files can be found here