| 67 |
|
|
| 68 |
|
Parameters for CRAB usage and configuration are provided by the user changing the configuration file B<crab.cfg>. |
| 69 |
|
|
| 70 |
< |
CRAB generates scripts and additional data files for each job. The produced scripts are submitted directly to the Grid. CRAB makes use of BOSS to interface to the Grid scheduler, as well as for logging and bookkeeping and eventually real time monitoring. |
| 70 |
> |
CRAB generates scripts and additional data files for each job. The produced scripts are submitted directly to the Grid. CRAB makes use of BossLite to interface to the Grid scheduler, as well as for logging and bookkeeping. |
| 71 |
|
|
| 72 |
|
CRAB support any CMSSW based executable, with any modules/libraries, including the user provided one, and deals with the output produced by the executable. Up to version 1_2_1, also ORCA (and FAMOS) based executable were supported. CRAB provides an interface with CMS data discovery services (DBS and DLS), which are completely hidden to the final user. It also splits a task (such as analyzing a whole dataset) into smaller jobs, according with user requirements. |
| 73 |
|
|
| 224 |
|
|
| 225 |
|
=item B<-status> |
| 226 |
|
|
| 227 |
< |
Check the status of the jobs, in all states. If BOSS real time monitor is enabled, also some real time information are available, otherwise all the info will be available only after the output retrieval. |
| 227 |
> |
Check the status of the jobs, in all states. All the info (e.g. application and wrapper exit codes) will be available only after the output retrieval. |
| 228 |
|
|
| 229 |
|
=item B<-getoutput|-get [range]> |
| 230 |
|
|
| 311 |
|
The scheduler to be used: I<glitecoll> is the more efficient grid scheduler and should be used. Other choice are I<glite>, same as I<glitecoll> but without bulk sumbission (and so slower) or I<condor_g> (see specific paragraph) or I<edg> which is the former Grid scheduler, which will be dismissed in some future |
| 312 |
|
From version 210, also local scheduler are supported, for the tim being only at CERN. I<LSF> is the standard CERN local scheduler or I<CAF> which is LSF dedicated to CERN Analysis Facilities. |
| 313 |
|
|
| 314 |
– |
=item B<server_mode> |
| 315 |
– |
|
| 316 |
– |
To use the CRAB-server mode put 1 in this field. If the server_mode key is equal to 0 crab works, as usual, in standalone way. |
| 317 |
– |
|
| 314 |
|
=item B<server_name> |
| 315 |
|
|
| 316 |
< |
The name of the server that you want to use plus the path of the server storage (eg: hostname/data/cms/). The server available to users can be found from CRAB web page. |
| 316 |
> |
To use the CRAB-server support it is needed to fill this key with server name as server_<Server_DOMAIN> (e.g. server_cnaf). If I<server_name=None> crab works in standalone way. |
| 317 |
> |
The server available to users can be found from CRAB web page. |
| 318 |
|
|
| 319 |
|
=back |
| 320 |
|
|
| 449 |
|
|
| 450 |
|
=item B<register_data> |
| 451 |
|
|
| 455 |
– |
Not more supported. |
| 456 |
– |
|
| 457 |
– |
=item B<use_central_bossDB> |
| 458 |
– |
|
| 459 |
– |
Use central BOSS DB instead of one for each task: the DB must be already been setup. See installation istruction for more details. |
| 460 |
– |
|
| 461 |
– |
=item B<use_boss_rt> |
| 462 |
– |
|
| 463 |
– |
Use BOSS real time monitoring. |
| 464 |
– |
|
| 452 |
|
=back |
| 453 |
|
|
| 454 |
|
B<[EDG]> |
| 483 |
|
|
| 484 |
|
=item B<additional_jdl_parameters:> |
| 485 |
|
|
| 486 |
< |
Any other parameters you want to add to jdl file: comma separated list, each |
| 486 |
> |
Any other parameters you want to add to jdl file:semicolon separated list, each |
| 487 |
|
item B<must> be complete, including the closing ";". |
| 488 |
< |
With this field it\'s also possible to specify which WMS you want to use, adding the parameter "additional_jdl_parameters = WMProxyEndpoints ={"https://hostname:port/pathcode"};" where "hostname" is WMS\' name, the "port" generally is 7443 and the "pathcode" should be something like "glite_wms_wmproxy_server". |
| 488 |
> |
|
| 489 |
> |
=item B<wms_service> |
| 490 |
> |
|
| 491 |
> |
With this field it\'s also possible to specify which WMS you want to use (https://hostname:port/pathcode) where "hostname" is WMS\' name, the "port" generally is 7443 and the "pathcode" should be something like "glite_wms_wmproxy_server". |
| 492 |
|
|
| 493 |
|
=item B<max_cpu_time> |
| 494 |
|
|
