Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 23 to 23 | ||||||||
Creating a CMSSW projectYou must have setup your environment first !!! | ||||||||
Deleted: | ||||||||
< < | mkdir CMSSW_1_5_4 cd CMSSW_1_5_4 | |||||||
scramv1 project CMSSW CMSSW_1_5_4 | ||||||||
Added: | ||||||||
> > | This creates the release directory for you. You'll be working inside of the src directory in here. | |||||||
Setup the scram environment for compilation/runtimeYou must have created the CMSSW project within which you want to compile or run. | ||||||||
Line: 36 to 36 | ||||||||
Checking out S&T codeYou must check out this code into the src directory of your CMSSW project | ||||||||
Changed: | ||||||||
< < | cd CMSSW_1_5_4/src export CVSROOT :pserver:anonymous@cmscvs.cern.ch:/cvs_server/repositories/CMSSW= | |||||||
> > | cd CMSSW_1_5_4/src export CVSROOT=:pserver:anonymous@cmscvs.cern.ch:/cvs_server/repositories/CMSSW | |||||||
cvs login 98passwd | ||||||||
Changed: | ||||||||
< < | cvs co -d CMS1 UserCode? /Gutsche/CMS1 | |||||||
> > | cvs co -d CMS1 UserCode/Gutsche/CMS1 | |||||||
Compiling the S&T codeYou must have setup the scram environment for compilation first. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 7 to 7 | ||||||||
setting up the environment | ||||||||
Changed: | ||||||||
< < | source /code/osgcode/cmssoft/cmsset_default.sh CMSSW_1_5_4
source /code/osgcode/cmssoft/cms/setup/bashrc
export SCRAM_ARCH=slc4_ia32_gcc345
export VDT_LOCATION=/data/vdt
export EDG_WL_LOCATION=$VDT_LOCATION/edg
source /data/vdt/setup.sh | |||||||
> > | source /code/osgcode/cmssoft/cmsset_default.sh CMSSW_1_5_4 source /code/osgcode/cmssoft/cms/setup/bashrc export SCRAM_ARCH=slc4_ia32_gcc345 export VDT_LOCATION=/data/vdt export EDG_WL_LOCATION=$VDT_LOCATION/edg source /data/vdt/setup.sh | |||||||
Getting a proxyvoms-proxy-init -voms cms -valid 500:00 | ||||||||
Line: 23 to 23 | ||||||||
Creating a CMSSW projectYou must have setup your environment first !!! | ||||||||
Changed: | ||||||||
< < | mkdir CMSSW_1_5_4
cd CMSSW_1_5_4
scramv1 project CMSSW CMSSW_1_5_4 | |||||||
> > | mkdir CMSSW_1_5_4 cd CMSSW_1_5_4 scramv1 project CMSSW CMSSW_1_5_4 | |||||||
Setup the scram environment for compilation/runtimeYou must have created the CMSSW project within which you want to compile or run. | ||||||||
Changed: | ||||||||
< < | cd CMSSW_1_5_4/src
eval `scramv1 runtime -sh` | |||||||
> > | cd CMSSW_1_5_4/src eval `scramv1 runtime -sh` | |||||||
Checking out S&T codeYou must check out this code into the src directory of your CMSSW project | ||||||||
Changed: | ||||||||
< < | cd CMSSW_1_5_4/src
export CVSROOT :pserver:anonymous@cmscvs.cern.ch:/cvs_server/repositories/CMSSW=
cvs login
98passwd
cvs co -d CMS1 UserCode? /Gutsche/CMS1 | |||||||
> > | cd CMSSW_1_5_4/src export CVSROOT :pserver:anonymous@cmscvs.cern.ch:/cvs_server/repositories/CMSSW= cvs login 98passwd cvs co -d CMS1 UserCode? /Gutsche/CMS1 | |||||||
Compiling the S&T codeYou must have setup the scram environment for compilation first. | ||||||||
Changed: | ||||||||
< < | cd CMSSW_1_5_4/src/CMS1
./Configuration/installCMS1.pl CMSSW_1_5_4 | |||||||
> > | cd CMSSW_1_5_4/src/CMS1 ./Configuration/installCMS1.pl CMSSW_1_5_4 | |||||||
Running the Ntuplemaker on uafYou must have compiled the S&T code and setup the scram environment for compilation/runtime. I created a wgamma-uaf.cfg file based on info from Matt N. This is in/home/users/fkw/CMS/crab/CMSSW_1_5_4/CMS1/NtupleMaker/test/ | ||||||||
Changed: | ||||||||
< < | cd CMSSW_1_5_4/src/CMS1
cmsRun NtupleMaker? /test/wgamma-uaf.cfg | |||||||
> > | cd CMSSW_1_5_4/src/CMS1 cmsRun NtupleMaker? /test/wgamma-uaf.cfg | |||||||
Running NtupleMaker? via crabYou must have done your runtime setup of cmssw, as well as the crab installation. | ||||||||
Changed: | ||||||||
< < | cd ~fkw/CMS/crab
export X509_USER_PROXY=/tmp/x509up_u`id -u`
source CRAB_1_5_4/crab.sh | |||||||
> > | cd ~fkw/CMS/crab export X509_USER_PROXY=/tmp/x509up_u`id -u` source CRAB_1_5_4/crab.sh | |||||||
Then edit the file "files" to include whatever datasets you want to analyze. | ||||||||
Changed: | ||||||||
< < | ./script | |||||||
> > | ./script | |||||||
This will do as follows:
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
fkw's Getting Started with CMSSW pageNote that there are some README files in fkw's home directory in addition t the stuff here.setting up the environmentsource /code/osgcode/cmssoft/cmsset_default.sh CMSSW_1_5_4
source /code/osgcode/cmssoft/cms/setup/bashrc
export SCRAM_ARCH=slc4_ia32_gcc345
export VDT_LOCATION=/data/vdt
export EDG_WL_LOCATION=$VDT_LOCATION/edg
source /data/vdt/setup.sh
Getting a proxyvoms-proxy-init -voms cms -valid 500:00
Getting and installing a new version of CRABGo to Matt L.'s page via link above.Creating a CMSSW projectYou must have setup your environment first !!!mkdir CMSSW_1_5_4
cd CMSSW_1_5_4
scramv1 project CMSSW CMSSW_1_5_4
Setup the scram environment for compilation/runtimeYou must have created the CMSSW project within which you want to compile or run.cd CMSSW_1_5_4/src
eval `scramv1 runtime -sh`
Checking out S&T codeYou must check out this code into the src directory of your CMSSW projectcd CMSSW_1_5_4/src
export CVSROOT :pserver:anonymous@cmscvs.cern.ch:/cvs_server/repositories/CMSSW=
cvs login
98passwd
cvs co -d CMS1 UserCode? /Gutsche/CMS1
Compiling the S&T codeYou must have setup the scram environment for compilation first.cd CMSSW_1_5_4/src/CMS1
./Configuration/installCMS1.pl CMSSW_1_5_4
Running the Ntuplemaker on uafYou must have compiled the S&T code and setup the scram environment for compilation/runtime. I created a wgamma-uaf.cfg file based on info from Matt N. This is in/home/users/fkw/CMS/crab/CMSSW_1_5_4/CMS1/NtupleMaker/test/
cd CMSSW_1_5_4/src/CMS1
cmsRun NtupleMaker? /test/wgamma-uaf.cfg
Running NtupleMaker? via crabYou must have done your runtime setup of cmssw, as well as the crab installation.cd ~fkw/CMS/crab
export X509_USER_PROXY=/tmp/x509up_u`id -u`
source CRAB_1_5_4/crab.sh
Then edit the file "files" to include whatever datasets you want to analyze.
./script
This will do as follows:
|