Direct crab tests
Problems
Sept 13th 2012: Job is submitted and running but status shows created
- submited a job with the following configuration
[CRAB]
jobtype = cmssw
scheduler = remoteGlidein
use_server = 0
#scheduler = glidein
#use_server = 1
[CMSSW]
datasetpath = /DoubleMu/Run2012C-PromptReco-v2/AOD
pset = ../test/muontreemaker_Data2012_cfg.py
total_number_of_lumis = -1
lumis_per_job = 200
runselection = 198934-202504
output_file = leptonTree.root
[USER]
return_data = 1
copy_data = 0
#ui_working_dir = DoubleMu_Run2012C-PromptReco-v2_AOD_198934_202504
ui_working_dir = TEST_DoubleMu_Run2012C-PromptReco-v2_AOD_198934_202504
[GRID]
maxtarballsize = 50
se_black_list = T2_US_Caltech
Observed that when I do
crab -status -c ...
it says all the jobs are created, but really they are running.
- Job log is copied here
- = /afs/cern.ch/user/d/dlevans/public/TEST_DoubleMu_Run2012C-PromptReco-v2_AOD_198934_202504.log=
- In dashboard it is here
--
DaveEvans - 13-Sep-2012
Topic revision: r1 - 2012-09-13
- unknown