Making Ntuples & Developing in CMSSW_7_2_0

The most recent tag is used for NtupleProduction. For development, make a new branch and merge it to "master" when you're sure it works. The branch and the most recent tag should be identical during nTupling.

Auto Ntuples

If you are making Ntuples, you should probably use the AutoTupler utility:
https://github.com/cmstas/NtupleTools/tree/master/AutoTuple Instructions at that site. That will take care of all the below automatically -- if it does not, e-mail Alex/Jason

Development

If you are trying to develop, I suggest:

1. Taking the setup.sh file from the AutoTupler
2. Comment out the first six lines and the last two lines
3. Replace line 8, hard coding the global tag you want to use
4. Replace line 9, hard coding the CMS3 tag or branch you want to develop
5. ". setup.sh"

This will install everything properly for you. Then you can test it by doing 6. "scram b -j 20" to compile 7. "cmsRun test/MCProduction2015_NoFilter_cfg.py". This will make a CMS3 baby with <100 entries.

Then you can develop, and repeat lines 6-7 as needed.

Basic Manual Setup (for Ntuples or Development, if you don't want to use the AutoTupler for some reason)

export SCRAM_ARCH=slc6_amd64_gcc481
cmsrel CMSSW_7_2_0
cd CMSSW_7_2_0/src
cmsenv
git clone [email protected]:cmstas/NtupleMaker.git CMS3/NtupleMaker
cd CMS3/NtupleMaker
git checkout CMS3_V07-02-02 #for development, want the branch instead 7_2_0_dev
source setup/patchesToSource.sh
cd $CMSSW_BASE/src
scram b -j 10

Making Ntuples (without AutoTupler)

Do the "basic manual setup" above.
Then you can follow the instructions here:
http://www.t2.ucsd.edu/tastwiki/bin/view/CMS/MakingCMS3Ntuples#Setting_up_your_crab_working_dir

Development

To run on a test sample do:
cmsRun test/Slim_MCProduction2012_NoFilter_cfg.py
If you get "cmsRun: command not found" you need to "cmsenv" inside the release area and try again.

Pushing changes

git add filename
git commit -m "your commit message"
git push

You can find more info about using git here.