Maintenance script: Created page with " === How to get the code === The Top Quark Analysis code as we will develop in Brussels will be part of the Top-package in the CMSSW-software. Every stable version of this co..."

2015-08-26T12:29:24Z

Created page with " === How to get the code === The Top Quark Analysis code as we will develop in Brussels will be part of the Top-package in the CMSSW-software. Every stable version of this co..."

New page

=== How to get the code ===
The Top Quark Analysis code as we will develop in Brussels will be part of the Top-package in the CMSSW-software. Every stable version of this code should be accessible by means of the central CVS-server from CERN. However, for daily development, a CVS server is setup in Brussels. In order to get a recent version of the code, you should:
**login to the lxpub2 or lxpub3 machine
<pre>
e.g: ssh -X username@lxpub2.iihe.ac.be
</pre>
**make sure the CMS software is sourced
<pre>
setenv VO_CMS_SW_DIR /msa3/cmssoft
source $VO_CMS_SW_DIR/cmsset_default.csh ## initialiseert de cms env
</pre>
**get a recent CMSSW workspace (CMSSW_1_2_0) in your /beo5/<tt>username</tt> directory
<pre>
scramv1 p CMSSW CMSSW_1_2_0; cd CMSSW_1_2_0/src
</pre>
**make a symlink to this latest version
<pre>
in /beo5/<tt>uname</tt>, type 'ln -s CMSSW_1_2_0 CMSSW'
</pre>
**set the path's to the Brussels' CVS server
<pre>
export CVS_RSH=/usr/bin/ssh
export CVSROOT=:pserver:<tt>uname</tt>@pc150.iihe.ac.be:/home/cvs/cms
</pre>
**login to this server
<pre>
cvs login (and type your normal lxpub password)
</pre>
(these two lines might be put your .bashrc)
**get the Top -code from the Brussels' CVS server
<pre>
cvs co -r Top_1_0 Top
</pre>
**compile the code
<pre>
scramv1 b
</pre>
**make your own library
<pre>
look in e.g. TtObjectResolutions to have an example on how to do this
</pre>
As you will notice, you will have to change all the PATH's in your header files when importing your code into the new framework. Another important difference is the extraction of the KinFit package to a standalone library. Now <tt>scramv1 b</tt> will as well take care of the compilation of this package. 
 
For the moment, only Jan Heyninck is supposed to commit changes to the code. In near future however, everyone should be able to do this. This means that if you would like to add a feature to the code, or you have found a bug, this is send on the top quark mailing list.
 
Get the code from global dbs
**make sure the CMS software is sourced
**set the path
<pre>
setenv CVSROOT :pserver:anonymous@cmscvs.cern.ch:/cvs_server/repositories/CMSSW
</pre>
**login to this server
<pre>
cvs login (and type following password: 98passwd)
</pre>
**go in the source directory and type
<pre>
cvs co TopQuarkAnalysis
</pre>

----
 

=== Some useful cvs commands ===
still to add
----
 

=== Documentation ===
A [http://w3.iihe.ac.be/~heyninck/ Ttbar doxygen documentation page] is available and similar to [http://cmsdoc.cern.ch/cms/sw/slc3_ia32_gcc323/cms/cmssw/CMSSW_1_2_0/doc/html/ the global CMSSW-software page]. This page is updated each night, and is meant to be a never ending work-in-progress, where everyone should contribute! To know how to add documentation, compare the content of the doc directories in the Top-code subdirectories with what you see on the doxygen page.
----
 

=== Running your analysis on the locally produced Ttbar sample ===
If you want to run on the 200k of inclusive Ttbar reco data, please find the ROOT-files in:
<pre>
Top/TtEventProducers/test/TtRecoFiles.cfi
</pre>
If you want to access the 200k of semileptonic Ttbar events, a list of ROOT-files can be found in:
<pre>
Top/TtEventProducers/test/TtSemiEvents.cfi
</pre>
(TODO)

----
 
=== Frequently Asked Questions ===
shoot!

{{TracNotice|{{PAGENAME}}}}

TtBar Analysis Framework - Revision history

Maintenance script: Created page with " === How to get the code === The Top Quark Analysis code as we will develop in Brussels will be part of the Top-package in the CMSSW-software. Every stable version of this co..."