Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Data Analysis with CMS | ||||||||
Line: 39 to 40 | ||||||||
RootDependencies / Buildfiles | ||||||||
Added: | ||||||||
> > | ||||||||
Here an example![]() ![]() | ||||||||
Changed: | ||||||||
< < | #include <cmsswtools/unpacker/interface/FedEvent.hh> | |||||||
> > | #include <cmsswtools/unpacker/interface/FedEvent.hh> | |||||||
as if CMSSW_#_#_#/src is the home directory (or ~/). The same should be done with the source code for the user created libraries like can be seen in the previous example. | ||||||||
Line: 67 to 69 | ||||||||
Papers | ||||||||
Added: | ||||||||
> > | ShearsSetting up an LPC area for Shears production | |||||||
-- DanielArcaro - 28 Oct 2015 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Data Analysis with CMS | ||||||||
Line: 34 to 34 | ||||||||
The best place to start with an Analyzer is the SWGuide![]() | ||||||||
Added: | ||||||||
> > | The CMSSW Unpacker as listed above is a good place to start looking at some source code examples. Another good example is the built in CMSSW analyzers that can be seen here![]() ![]() | |||||||
RootDependencies / Buildfiles | ||||||||
Line: 41 to 43 | ||||||||
#include <cmsswtools/unpacker/interface/FedEvent.hh> | ||||||||
Changed: | ||||||||
< < | 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. | |||||||
> > | as if CMSSW_#_#_#/src is the home directory (or ~/). 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![]() | ||||||||
Changed: | ||||||||
< < | Data | |||||||
> > | CMSSW VersionThis 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![]() ![]() | |||||||
Changed: | ||||||||
< < | 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. | |||||||
> > | **The source code for DumpFEDRawDataProduct is a pretty simple one page analyzer because if only prints some data to screen so it is a very good reference. The site also provides pretty much all the source code for the analyzers. It may be quite complicated but very useful. | |||||||
Analysis |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Data Analysis with CMS | ||||||||
Line: 10 to 10 | ||||||||
$ eos ls eos/cms/store/data | ||||||||
Changed: | ||||||||
< < | 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. | |||||||
> > | 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 | ||||||||
Added: | ||||||||
> > | ||||||||
Old DQM | ||||||||
Added: | ||||||||
> > |
EricDIM![]() | |||||||
Unpacker | ||||||||
Added: | ||||||||
> > | Unpacker | |||||||
CMSSW Unpacker | ||||||||
Added: | ||||||||
> > | CMSSW Unpacker | |||||||
CMSSW Tricks / Notes | ||||||||
Added: | ||||||||
> > |
All of this is for lxplus machines except for a few things in the root section. To install a CMSSW version use $ cmsrel CMSSW_#_#_# . Change to the CMSSW_#_#_#/src direction and enter cmsenv to set the environment. To select a specific version number read the Data section. Since some of those tools below require the environment already set just use CMSSW_7_4_2 for the first version and get others when needed. | |||||||
Analyzers | ||||||||
Added: | ||||||||
> > |
The best place to start with an Analyzer is the SWGuide![]() | |||||||
Root | ||||||||
Added: | ||||||||
> > | ||||||||
Dependencies / Buildfiles | ||||||||
Changed: | ||||||||
< < | Drell-Yan ProcessTheory | |||||||
> > | Here an 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![]() | |||||||
Data | ||||||||
Changed: | ||||||||
< < | Papers | |||||||
> > |
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.
AnalysisDrell-Yan ProcessTheory Data Papers | |||||||
-- DanielArcaro - 28 Oct 2015 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
Data Analysis with CMSFinding DataThe easiest place to start is the cms workbook page on finding data here![]()
$ eos ls eos/cms/store/dataThese 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 MonitoringOld DQMUnpackerCMSSW UnpackerCMSSW Tricks / NotesAnalyzersRootDependencies / BuildfilesDrell-Yan ProcessTheoryDataPapers-- DanielArcaro - 28 Oct 2015 |