![]() The crab checkwrite command can be used by a user to check if he/she has write permission in a given LFN directory path (by default /store/user//) in a given site. The crab checkusername command tries to retrieve the users' CERN (primary account) username from CRIC starting from the user VOMS proxy.īelow it is shown the crab checkusername screen output for the case of successful retrieval of my CERN (primary account) usernameĭN is: /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=atanasi/CN=710186/CN=Andres Jorge Tanasijczuk crab3 cache file the name of the file can not be changed. Note: The CRAB3_CACHE_FILE environment variable can only be used to set the location of the. crab3 files (by means of setting the corresponding CRAB3_CACHE_FILE variables to different directories), and execute in each shell CRAB commands referring to two different tasks without mixing the. Since environment variables are specific to the shell session, this feature allows the user to have two different shell sessions, with different locations of the. crab3 file by means of the environment variable CRAB3_CACHE_FILE: The user can change the location for the. For example, if CRAB commands are being executed by a script in this short form, and while the script is running the user executes another CRAB command for a different task, then this other CRAB project directory name will be cached, with an obvious effect in the script. ![]() This is a nice feature to save some typing, but should be used with care. crab3 located by default in the user's home directory.Ĭaching the CRAB project directory name allows the user to not have to explicitly specify it repeatedly in consecutive CRAB commands if the user doesn't specify a CRAB project directory, then the cached one is used (this is true for all commands, except for crab kill). Thus, a CRAB command that requires a task name would always be run passing the CRAB project directory name:Įvery time such a CRAB command is executed, the CRAB project directory name (in full path format) to which the command refers to is saved in a file named. requestcache file present in the CRAB project directory. CRAB will extract the task name from the. Relative paths and full paths can be used. To pass the task name, one has to actually run the command passing the CRAB project directory name in the -dir/-d option. Most of the CRAB commands refer to a task and therefore require to provide the corresponding task name as an input. To see the help menu for a specific command, just add the -h option: Individual commands also provide a help menu showing the options available for the command. d, -debug print extra messages to stdoutįor more information on how to run CRAB-3 please follow this link: q, -quiet don't print any messages to stdout h, -help show this help message and exit version show program's version number and exit ![]() The screen output is something similar to this: One can also get a list of available commands invoking the crab help menu: Uploads the crab log file to the CRAB cache in the server. Report the states of jobs in a task (and more). ![]() Get a task final report with the number of analyzed files, events and luminosity sections. Submit a task that was uploaded with crab submit -dryrun. Prepare a directory and the relative scripts to execute a job locally. The next sections give a more detailed description of the commands and usage examples. The following table provides a list of the currently available CRAB commands (ordered alphabetically) with a short description.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |