| 24 |
|
-getoutput|-get [range] -- get back the output of all jobs: if range is defined, only of selected jobs. |
| 25 |
|
-extend -- Extend an existing task to run on new fileblocks if there. |
| 26 |
|
-publish -- after the getouput, publish the data user in a local DBS instance. |
| 27 |
< |
-checkPublication [dbs_url datasetpath] -- checks if a dataset is published in a DBS. |
| 27 |
> |
-checkPublication [dbs_url datasetpath] -- checks if a dataset is published in a DBS. |
| 28 |
|
-kill [range] -- kill submitted jobs. |
| 29 |
|
-resubmit [range] -- resubmit killed/aborted/retrieved jobs. |
| 30 |
|
-copyData [range] -- copy locally the output stored on remote SE. |
| 459 |
|
=item B<generator> |
| 460 |
|
|
| 461 |
|
Name of the generator your MC job is using. Some generators require CRAB to skip events, others do not. |
| 462 |
< |
Possible values are pythia, comphep, and madgraph. This will skip events in your generator input file. |
| 462 |
> |
Possible values are pythia (default), comphep, lhe, and madgraph. This will skip events in your generator input file. |
| 463 |
|
|
| 464 |
|
=item B<executable> |
| 465 |
|
|
| 531 |
|
=item B<user_remote_dir> |
| 532 |
|
|
| 533 |
|
To be used with <copy_data>=1 and <storage_element> official CMS sites. |
| 534 |
< |
This is the directory or tree of directories where your output will be stored. This directory will be created under the mountpoint ( which will be discover by CRAB if an official CMS storage Element has been used, or taken from the crab.cfg as specified by the user). B<NOTE> This part of the path will be used as logical file name of your files in the case of publication without using an official CMS storage Element. Generally it should start with "/store". |
| 534 |
> |
This is the directory or tree of directories where your output will be stored. This directory will be created under the mountpoint ( which will be discover by CRAB if an official CMS storage Element has been used, or taken from the crab.cfg as specified by the user). B<NOTE> This part of the path will be used as logical file name of your files in the case of publication without using an official CMS storage Element. Generally it should start with "/store". |
| 535 |
|
|
| 536 |
|
=item B<storage_path> |
| 537 |
|
|
| 550 |
|
|
| 551 |
|
=item B<local_stage_out *> |
| 552 |
|
|
| 553 |
< |
This option enables the local stage out of produced output to the "close storage element" where the job is running, in case of failure of the remote copy to the Storage element decided by the user in che crab.cfg. It has to be used with the copy_data option. In the case of backup copy, the publication of data is forbidden. Set I<local_stage_out> = 1 |
| 553 |
> |
This option enables the local stage out of produced output to the "close storage element" where the job is running, in case of failure of the remote copy to the Storage element decided by the user in che crab.cfg. It has to be used with the copy_data option. In the case of backup copy, the publication of data is forbidden. Set I<local_stage_out> = 1 |
| 554 |
|
|
| 555 |
|
=item B<publish_data*> |
| 556 |
|
|
