mkShapesRDF: Simple Parallel RDF version of LatinoAnalysis
Please refer to the documentation for installation and a quick start guide.
For remote I/O and Condor operation, see docs/condor_remote_io.rst. In short: a fresh checkout has no generated start.sh, so run ./install.sh first; later use ./install.sh --check as a read-only validation. Source start.sh for local and unpackaged shared-filesystem runtime, and use --condor-runtime-package for a deterministic, validated worker-scratch archive. External configurations package only the selected configuration directory, with out-of-tree dependencies declared by repeatable --runtime-include. Proxies are always transferred separately when enabled. Submission uses condor_submit -terse so the raw receipt contains a stable job-ID range; on FNAL, an informational ENOEXEC wrapper fallback may precede an explicit success or failure outcome. The retained 2026-07-12 ZZ_CR evidence is a bounded CERN/FNAL matrix, not proof of production scale or every site.
Latest presentation at Latinos meeting here
Clone the repository:
git clone git@github.com:latinos/mkShapesRDF.git
cd mkShapesRDF
In case you want to use the framework in its latest stable version (i.e., to post-process Run 3 samples from 2022 to 2024) move to the most recent tag:
git checkout tags/Run3_production_2022_2024_jetfix
The previous step can be skipped if you want to develop new features in the framework. In any case, you have to run the following command to complete the installation:
./install.sh
start.sh is generated by that installation and is intentionally absent from a
fresh checkout. Do not source it before the first successful ./install.sh.
After you installed the framework, and every time you log-in, you have to setup the environment in order to use it:
cd <your_base_directory>/mkShapesRDF/
source start.sh
The first step is always to setup the environment. After that, you need to create a proxy to access files in the grid:
voms-proxy-init --voms cms -valid 192:0
If you have already installed mkShapesRDF and you are having problems creating the proxy, modify the file start.sh so that it looks like this:
#!/bin/bash
echo 'first source of start.sh'; source /cvmfs/sft.cern.ch/lcg/views/LCG_105/x86_64-el9-gcc11-opt/setup.sh
source `pwd`/myenv/bin/activate
export STARTPATH=`pwd`/start.sh
export JAVA_HOME=/cvmfs/sft.cern.ch/lcg/releases/java/11.0.21p9-cabd2/x86_64-el9-gcc13-opt
export PATH=$JAVA_HOME/bin:$PATH
export PYTHONPATH=`pwd`/myenv/lib64/python3.9/site-packages:\$PYTHONPATH
export PATH=`pwd`/utils/bin:\$PATH
where pwd represents the path in which you have installed the framework.
The actual command to post-process files will look like the following:
mkPostProc -o 0 -p Summer22EE_130x_nAODv12_Full2022v12 -s MCl2loose2022EEv12__MCCorr2022EEv12JetScaling__l2tight -T <sample_name>
More information about the inputs requested by mkPostProc can be found in the latest framework tutorial.