Skip to content

ldcorpe/ECALELF

 
 

Repository files navigation

ECALELF

Code for electron calibration in CMS Testing

====== Preliminary instructions: GitHub account Be sure to have a GitHub account and have followed the instructions here: http://cms-sw.github.io/cmssw/faq.html#how_do_i_subscribe_to_github

====== Download instructions.

wget --no-check-certificate https://raw.github.com/ECALELFS/ECALELF/master/setup_git.sh

chmod +x setup_git.sh

./setup_git.sh CMSSW_5_3_14_patch2

cd CMSSW_5_3_14_patch2/src/

cmsenv

cd Calibration/ZFitter && make && cd -

If you are using a tcsh shell: cd Calibration && source initCmsEnv.csh

If you are using a bash shell: cd Calibration && source initCmsEnv.sh

Every time you enter in a new shell you have to do: source initCmsEnv.csh or source initCmsEnv.sh

Problem: if you have an error in compilation like

consider to edit the following file: DataFormats/CaloRecHit/src/classes_def.xml changing the following lines:

<class name="reco::CaloCluster" ClassVersion="11">

<version ClassVersion="11" checksum="3936140"/>

</class>

to

<class name="reco::CaloCluster" ClassVersion="11">

<version ClassVersion="12" checksum="4003646624"/>

</class>

====== Code documentation: Code documentation is updated using doxygen system. You can find the documentation related to the master branch here: http://ecalelfs.github.io/ECALELF/index.html

It can be generated locally following the instructions below: Once downloaded the code, in Calibration/ you can run the command

doxygen fulldoc

to have the code documentation produced by doxygen opening the doc/doxygen/fulldoc/html/index.html with your browser

====== Instructions for developments: fork the repository in GIT to your own area (if you didn't it already) [email protected]:ECALELFS/ECALELF.git

Add your git repository to the list of remotes to be used like: git remote add -f myfork [email protected]:hengne/ECALELF.git git checkout devel-42X_44X_53X

====== If you want to develop the code: Create a new branch for your development (use a meaningful name) git branch myNewBranch Switch to the new branch: git checkout myNewBranch Push it to your git repository (create a new branch with the same name also in your remote GIT repository) git push myfork

Then start to develop, remember to do commits as much as possible

====== Remember to update regularly the code doing when you are in the branch devel-42X_44X_53X: git pull

About

Code for electron calibration in CMS

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C++ 42.3%
  • Python 36.9%
  • Shell 19.6%
  • Other 1.2%