GREY: For commands.
GREEN: For the output example of the executed commands (nearly what the user should see in his/her terminal).
PINK: For CMSSW parameter-set configuration files.
BLUE: For configuration files.
YELLOW: For any other type of file.
cmsrel CMSSW_8_0_0_pre5 # or later cd CMSSW_8_0_0_pre5/src git clone git@github.com:CTPPS/CTPPSFastSim.git . cmsenv scram b -j 8
ssh -XY <username>@lxplus.cern.chSetup CRAB3 by sourcing:
source /cvmfs/cms.cern.ch/crab3/crab.shThere is also an alternative way to do this by using the light client script. The crab_light.sh script sources the crab.sh script without polluting the environment with extra variables. The sourced CRAB3 Client is the same with both scripts.
source /cvmfs/cms.cern.ch/crab3/crab_light.shCheck the version being used by executing:
which crabGet a CMS VO proxy
voms-proxy-init --voms cms --valid 168:00To submit a task, execute the following CRAB command:
crab submit -c crabConfig.pyTo check the status of a task, execute the following CRAB command:
crab status --dir/-d <CRAB-project-directory>CRAB allows the user to resubmit a task, which will actually resubmit only the failed jobs in the task. The resubmission command is as follows:
crab resubmit --dir/-d <CRAB-project-directory>In case one wants to retrieve some output ROOT files of a task, one can do so with the following CRAB command:
crab getoutput --dir/-d <CRAB-project-directory> [--jobids <comma-separated-list-of-jobs-and/or-job-ranges>]
cmsDriver.py MinBias_13TeV_pythia8_TuneCUETP8M1_cfi -n 1000 --fast --conditions auto:run2_mc --magField 38T_PostLS1 // --beamspot Realistic50ns13TeVCollision -s GEN,SIM,RECOBEFMIX --eventcontent FASTPU --datatier GEN-SIM-RECO // --era Run2_25ns --fileout minbias.root --no_exec
$ cd CMSSW_8_0_12/src $ cmsenv $ git clone git@github.com:uerj-cms-cep-studies/CTPPSTools.git $ git clone git@github.com:uerj-cms-cep-studies/DataUtils.git $ scram b -j 8On your configuration file add the follow statements:
process.load('CTPPSTools.Filters.doubleArmFilter_cfi') process.doubleArmFilter.vertices = 'offlineSlimmedPrimaryVertices' process.doubleArmFilter.tofRes = 50 #ToF resolution in ps process.p1 = cms.Path(process.doubleArmFilter * [anything] )To get the protons in your analyzer:
edm::EDGetTokenT<std::vector<std::pair<size_t,size_t> > > token; edm::Handle<std::vector<std::pair<size_t,size_t> > > protons; token = consumes<std::vector<std::pair<size_t,size_t> > >(edm::InputTag("doubleArmFilter","protons"))); // in your constructor event.getByToken(token, protons); // in the event loop
source /afs/cern.ch/project/eos/installation/user/etc/setup.sh export EOS_MGM_URL=root://eosuser.cern.ch eosmount $HOME/eosif it works, you will see something like this:
.... trying to create ... /afs/cern.ch/user/m/mdealmei/eos OK ===> Mountpoint : /afs/cern.ch/user/m/mdealmei/eos ===> Fuse-Options : kernel_cache,attr_timeout=30,entry_timeout=30,max_readahead=131072,max_write=4194304,fsname=eosuser.cern.ch root://eosuser.cern.ch//eos/ ===> xrootd ra : 131072 ===> xrootd cache : 393216 ===> fuse debug : 0 ===> fuse write-cache : 1 ===> fuse write-cache-size : 100000000
![]() |
![]() |
![]() |
![]() |
|
![]() |
|
![]() |