Difference: DataAnalysis (1 vs. 4)

Shears

Setting up an LPC area for Shears production

CMSSW Version

This section is for determining what CMSSW version to choose for a specific data file and see the contents of the file. The data files are all root files and can be found using the procedures above. The main tools are the Event Data Model (edm). Entering edm on lxplus and then pressing tab twice will give a list of all the different edm tools. The two ones used more are edmProvDump which provides the CMSSW version used the create the file. This version should be the version you are using to do any of the analysis. The other tool is edmDumpEventContent which gives a list of the type of data contained in the file. This is explained in more detail in the analyzer section.

Another option is to use a built in cmssw analyzer. An easy implementation of one is in this python script. There are two options for analyzers: EventContentAnalyzer and DumpFEDRawDataProduct(source code)**. The content analyzer will be a similar to edmDumpEventContent and the raw data product just prints the raw data in hex.

The edm tools should always work for global root files but may not work for the local ones. For the recent local runs any CMSSW_7_#_# should work fine since the edmProbDump does not work and cannot tell the exact version.

example

example

#include <cmsswtools/unpacker/interface/FedEvent.hh>

as if the home directory (or ~/) is CMSSW_#_#_#/src. The same should be done with the source code for the user created libraries like can be seen in the previous example.

Another place to look is at the built in libraries source code or even other peoples libraries/analyzers. A good place I have gathered a lot of information from is here. The link has a huge list of both built in analyzer source code and user created libraries plus analyzers. The format used there has worked for current CMSSW version such as 7_4_2.

Analysis

Drell-Yan Process

Theory

Data

Papers

Data Analysis with CMS

Finding Data

here

The second option is by brute force looking through directory on eos (disk storage).

• eos can be entered into a terminal on an lxplus machine and an interactive session will start. Commands such as ls and cd can be used to navigate directories. There is a directory called data that has most of the relevant global runs. Enter quit to get out of the session.
• Another way is to use eos like this:

      $ eos ls eos/cms/store/data 

These file locations such as eos/cms/store/data/Run2015C/Cosmics/RAW/v1/000/253/982/00000/AAF77D5F-FF3F-E511-83B4-02163E0143BA.root are then entered into python files to be used by cmssw. More on this below.

Raw Data Analysis / Data Quality Monitoring

Old DQM

Unpacker

CMSSW Unpacker

CMSSW Tricks / Notes

Analyzers

Root

Dependencies / Buildfiles

Drell-Yan Process

Theory

Data

Papers