User Tools

Site Tools


computing:crab

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
computing:crab [2019/10/24 17:13] – [List of configuration parameters] iwncomputing:crab [2019/10/24 17:16] – [CRAB3] iwn
Line 2: Line 2:
 ====== CRAB3 ====== ====== CRAB3 ======
  
-See [[https://github.com/IzaakWN/CRAB]] for an example with CRAB3. +See 
 +  * Tutorial: https://twiki.cern.ch/twiki/bin/view/CMSPublic/WorkBookCRAB3Tutorial 
 +  * Configuration: https://twiki.cern.ch/twiki/bin/view/CMSPublic/CRAB3ConfigurationFile 
 +  * Commands: https://twiki.cern.ch/twiki/bin/view/CMSPublic/CRAB3Commands 
 +  * Example: https://github.com/IzaakWN/CRAB
  
 +\\ \\
 ====== CRAB2 ====== ====== CRAB2 ======
  
Line 46: Line 50:
  
 ===== CRAB configuration file for Monte Carlo data ===== ===== CRAB configuration file for Monte Carlo data =====
-The CRAB configuration file (default name crab.cfg) should be located at the same location as the CMSSW parameter-set to be used by CRAB with the following content:+The CRAB configuration file (default name ''crab.cfg'') should be located at the same location as the CMSSW parameter-set to be used by CRAB with the following content:
 <code> <code>
 [CMSSW] [CMSSW]
Line 75: Line 79:
 ===== Analyse published results ====== ===== Analyse published results ======
 To analyse results that have been published in a local DBS you may use a CRAB configuration identical to any other, with the addition that you must specify the DBS To analyse results that have been published in a local DBS you may use a CRAB configuration identical to any other, with the addition that you must specify the DBS
-instance to which the data was published, datasetpath name of your dataset and the dbs_url. To do this you must modify the [CMSSW] section of your CRAB configuration file, e.g.+instance to which the data was published, datasetpath name of your dataset and the ''dbs_url''. To do this you must modify the ''[CMSSW]'' section of your CRAB configuration file, e.g.
 <code> <code>
 [CMSSW] [CMSSW]
Line 82: Line 86:
 dbs_url=url_local_dbs dbs_url=url_local_dbs
 </code> </code>
-<wrap important>Note</wrap> As ''dbs_url'', the URL for the DBS instance used in publication. Note that dbs_url should point to a read-only URL, which has a slightly different syntax from the one used to write in DBS. E.g.+NoteAs ''dbs_url'', the URL for the DBS instance used in publication. Note that dbs_url should point to a read-only URL, which has a slightly different syntax from the one used to write in DBS. E.g.
 Writing: https://cmsdbsprod.cern.ch:8443/cms_dbs_ph_analysis_02_writer/servlet/DBSSe rvlet Writing: https://cmsdbsprod.cern.ch:8443/cms_dbs_ph_analysis_02_writer/servlet/DBSSe rvlet
 Reading: http://cmsdbsprod.cern.ch/cms_dbs_ph_analysis_02/servlet/DBSServlet Reading: http://cmsdbsprod.cern.ch/cms_dbs_ph_analysis_02/servlet/DBSServlet
Line 93: Line 97:
 https://wiki.chipp.ch/twiki/bin/view/CmsTier3/HowToManageJobsWithCRAB#Example_of_crab_cfg https://wiki.chipp.ch/twiki/bin/view/CmsTier3/HowToManageJobsWithCRAB#Example_of_crab_cfg
  
-<wrap important>Note:</wrap> This type of jobs cannot be used to process a dataset that is not on the tier3. The network connection to the T3 is not fast enough to sustain a useful write speed in the stage-out step and the jobs will fail in the very end - i.e. when trying to copy the results.+Note: This type of jobs cannot be used to process a dataset that is not on the tier3. The network connection to the T3 is not fast enough to sustain a useful write speed in the stage-out step and the jobs will fail in the very end - i.e. when trying to copy the results.
 ===== Non local jobs ===== ===== Non local jobs =====
  
Line 138: Line 142:
 By event: only for MC data. You need to specify 2 of these parameters: By event: only for MC data. You need to specify 2 of these parameters:
 total_number_of_events, number_of_jobs, events_per_job total_number_of_events, number_of_jobs, events_per_job
-  * specify the ''total_number_of_events'' and the ''number_of_jobs'': this will +  * specify the ''total_number_of_events'' and the ''number_of_jobs'': this will assign to each job a number of events equal to ''total_number_of_events/number_of_jobs'' 
-assing to each job a number of events equal to ''total_number_of_events/number_of_jobs'' +  * specify the ''total_number_of_events'' and the ''events_per_job'': this will assign to each job ''events_per_job events'' and will calculate the number of jobs by ''total_number_of_events/events_per_job''
-  * specify the ''total_number_of_events'' and the ''events_per_job'': this will +
-assign to each job ''events_per_job events'' and will calculate the number of jobs by ''total_number_of_events/events_per_job''+
   * or you can specify the ''number_of_jobs'' and the ''events_per_job''   * or you can specify the ''number_of_jobs'' and the ''events_per_job''
-  * By lumi: real data require it. You need to specify 2 of these parameters: +  * By lumi: real data require it. You need to specify 2 of these parameters: ''total_number_of_lumis'', ''lumis_per_job'', ''number_of_jobs''
-''total_number_of_lumis'', ''lumis_per_job'', ''number_of_jobs''+
   * because jobs in split-by-lumi mode process entire rather than partial files, you will often end up with fewer jobs processing more lumis than expected. Additionally, a single job cannot analyze files from multiple blocks in DBS. So these parameters are "advice" to CRAB rather than determinative.   * because jobs in split-by-lumi mode process entire rather than partial files, you will often end up with fewer jobs processing more lumis than expected. Additionally, a single job cannot analyze files from multiple blocks in DBS. So these parameters are "advice" to CRAB rather than determinative.
   * specify the lumis_per_job and the number_of_jobs: the total number of lumis processed will be number_of_jobs x lumis_per_job   * specify the lumis_per_job and the number_of_jobs: the total number of lumis processed will be number_of_jobs x lumis_per_job
computing/crab.txt · Last modified: 2019/10/24 17:17 by iwn