Difference: HCALOP (1 vs. 2)

Revision 221 Jun 2017 - DanielArcaro

Line: 1 to 1
 
META TOPICPARENT name="DanielArcaro"
Changed:
<
<

Data Analysis with CMS

>
>

HCAL Operations

 
Changed:
<
<

Finding Data

The easiest place to start is the cms workbook page on finding data here
>
>

On Call Cheat Sheet

 
Changed:
<
<
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 
>
>

Setting up Tunnels

Follow the HCAL Connectivity twiki to get tunnels working for lxplus,904, and p5 networks. The best choice for windows is to use linux with a virtual box. If you are on lxplus already at cern with a windows computer putty works well too.
 
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.
>
>

Setup Environment

Bash files
 
Changed:
<
<

Raw Data Analysis / Data Quality Monitoring

>
>

Snippets

Getting the Hcal config files point 5: (should be the same for 904) $ cfgcvs checkout HcalCfg
 
Changed:
<
<
Old DQM
>
>
Very similar to svn $ cvs commit -m "Comment here" $ cvs tag -F pro DTC.cfg
 
Deleted:
<
<
EricDIM
 
Changed:
<
<
Unpacker
>
>

MCH Commands

telnet hcal-mch-20 (the hcal-mch-20 is like in HcalCfg/uTCA/connection.xml with hcal-card-crate-additionaloption)
>> show_fru
(M4 is on)
>> shutdown <fru_number>
(Probably do show_fru again to make sure the state goes to M1 of the particular card)
>> fru_start <fru_number>
 
Changed:
<
<
Unpacker
>
>
>> exit
 
Deleted:
<
<
CMSSW Unpacker
 
Changed:
<
<
CMSSW Unpacker
>
>
To shut down all cards: >>shutdown all
To reboot ( this also restart the MCH so you will be disconnected. Wait ten seconds or so and then telnet back in to see status) >> reboot
 
Changed:
<
<

CMSSW Tricks / Notes

>
>

Run Control Websites

P5: http://cmsrc-hcal.cms:16000/rcms/gui/servlet/RunGroupChooserServlet
 
Changed:
<
<
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.
>
>
904: http://cms904rc-hcal.cms904:16000/rcms/gui/servlet/RunGroupChooserServlet
 
Changed:
<
<
Analyzers
>
>
Building 28: http://cmshcal21:16000/rcms/gui/servlet/RunningConfigurationServlet
 
Changed:
<
<
The best place to start with an Analyzer is the SWGuide. The section mkedanlzr will show how to create a skeleton analyzer to then edit. Once created there are three main files to edit. The first is the analyzerName.cc file which has all the analysis code. The next file is the BuildFile that links any outside code to the analyzer. The last is the python ConfFile_cfg.py script which the cmssw code reads to run your analyzer.
>
>

uHTR

The uHTR tool is pretty straightforward. The only thing to watch out for is that the back and front fpga firmware should not be mixed up (and they can be…). Also, the versions should match between front and back. This should be both the detector part (HF, HBHE) and the number after it which is the speed (1600 = 1.6Gbps, 4800 = 4.8Gbps). Examples match below: uhtr_front_HBHE1600_1_00_07.mcs.xz uhtr_back_HBHE1600_1_00_00.mcs.xz
 
Changed:
<
<
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. The amount of code there is quite hard to sort through so here is a fairly simple one under the data formats directory.
>
>
Correct Use for P5/904: $ uHTRtool.exe -c crate:slot (uHTRtool.exe -c 52:10) Not sure yet what the shell script does (uHTRtool.sh)
 
Deleted:
<
<
Root
 
Changed:
<
<
Dependencies / Buildfiles
Here an example is the best thing to look at. The first six use name statements are built in cmssw libraries. The last library is a user created one that is placed in the src directory of the CMSSW_#_#_# directory. The code for this library must be formatted, put into correct directories, and have a build file itself. Again the best is the look at an example and edit it for your purpose. There are source files, header files, and a buildfile to actually create the library. All of it is built in the end with scram b. When making these libraries or putting an #include statement in your analyzer that they point to the correct place. In the CMSSW Unpacker (same as above) the parse.cc (main analysis code) has an include:
>
>

Log Files

Go to 904 or p5 network Ssh cms904rc-hcal (for 904) Ssh cmsrc-hcal (for p5) Run the handsaw script (this is located in ~hcalsw/bin/): $ Handsaw.pl /var/log/rcms/hcalpro/Logs_hcalpro.xml] $ tail -f /var/log/rcms/hcalpro/Logs_hcalpro.xml | Handsaw.pl Tail streams the errors out. Probably the best to look at.
 
Changed:
<
<
#include <cmsswtools/unpacker/interface/FedEvent.hh>
>
>
Parsing through old Logs: Copy the log file you want to look at. They are usually in a compressed (.gz). To open them: $ gunzip file.gz
 
Changed:
<
<
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.
>
>
Once you have the log file, you can use Handsaw and less to look through them: $ Handsaw.pl logfile.xml | less -R
 
Deleted:
<
<
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.

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.

**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

Drell-Yan Process

Theory

Data

Papers

  -- DanielArcaro - 21 Jun 2017 \ No newline at end of file

Revision 121 Jun 2017 - DanielArcaro

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="DanielArcaro"

Data Analysis with CMS

Finding Data

The easiest place to start is the cms workbook page on 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

EricDIM

Unpacker

Unpacker

CMSSW Unpacker

CMSSW Unpacker

CMSSW Tricks / Notes

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

The best place to start with an Analyzer is the SWGuide. The section mkedanlzr will show how to create a skeleton analyzer to then edit. Once created there are three main files to edit. The first is the analyzerName.cc file which has all the analysis code. The next file is the BuildFile that links any outside code to the analyzer. The last is the python ConfFile_cfg.py script which the cmssw code reads to run your analyzer.

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. The amount of code there is quite hard to sort through so here is a fairly simple one under the data formats directory.

Root

Dependencies / Buildfiles
Here an example is the best thing to look at. The first six use name statements are built in cmssw libraries. The last library is a user created one that is placed in the src directory of the CMSSW_#_#_# directory. The code for this library must be formatted, put into correct directories, and have a build file itself. Again the best is the look at an example and edit it for your purpose. There are source files, header files, and a buildfile to actually create the library. All of it is built in the end with scram b. When making these libraries or putting an #include statement in your analyzer that they point to the correct place. In the CMSSW Unpacker (same as above) the parse.cc (main analysis code) has an include:

#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.

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.

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.

**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

Drell-Yan Process

Theory

Data

Papers

-- DanielArcaro - 21 Jun 2017

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback