Difference: LHCComputingGrid (8 vs. 9)

Revision 92006-03-17 - AndrasLaszlo

Line: 1 to 1
 Getting access to LHC Computing Grid. One can find a brief introductory material at the RMKI's getting started page, where you can find information on how to get access to LCG. There are also simple examples on that page.

Some more practical information on running a typical job.

Line: 47 to 47
  Now you can refer to files with their logical file names, which are site-independent. The logical file names have to be unique. A very convenient way to generate them is to imitate the UNIX type file naming scheme. With the command lfc-mkdir one can make logical directories, like
Changed:
<
<
> lfc-mkdir -m 755 /grid/cms/user_name/some_directory (Here, the -m xxx option is optional, this sets the permissions of the directory. All logical file names begin with /grid/virtual_organization. If you are a new user, the directory /grid/virtual_organization/user_name will not exist initially: you have to create it first, if you want an own directory. It is recommended to restrict write permissions like in the example.)
>
>
> lfc-mkdir /grid/cms/user_name/some_directory (All logical file names begin with /grid/virtual_organization. If you are a new user, the directory /grid/virtual_organization/user_name will not exist initially: you have to create it first, if you want an own directory.)
  There are various commands to manage logical file names, all beginning with lfc-, like lfc-chmod, lfc-getacl, lfc-setacl, lfc-chown, lfc-ln, lfc-rename, lfc-ls, lfc-rm, lfc-mkdir etc. Refer to the man pages of these commands, but the usage of these should be self-explanatory.
Line: 67 to 67
  > lcgcr.sh source_directory destination_directory_lfn (You can find this here: lcgcr.sh.)
Changed:
<
<
Note: unfortunately, I encountered that the lcg-cr action often fails (this should be remedied in future). Therefore, it is convenient to put an lcg-cr command into a checker loop:
>
>
Note1: unfortunately, I encountered that the lcg-cr action often fails (this should be remedied in future). Therefore, it is convenient to put an lcg-cr command into a checker loop:
 
RESULT = 1
Line: 80 to 80
 done
Changed:
<
<
This precaution may also be recommended for lcg-cp.
>
>
This precaution may also be recommended for lcg-cp or other lcg- commands.
 
Added:
>
>
Note2: NEVER RESTRICT THE PERMISSIONS OF A FILE OR DIRECTORY IN SUCH A WAY, THAT THE GROUP DOES NOT HAVE WRITE PERMISSIONS. There is a very simple reason for it. It is not really you, who does the actual copying onto a storage element: some program copies it, which is assigned to some more or less random userid, which is mapped to your userid TEMPORARYLY. This is a rather questionable way of manging userid-s, but that is the way how it is implemented in the current version. This fact has rahter dangerous implications. If you restrict the permissions, such that the group does not have write permissions, then at an other occasion (when your userid is mapped to another actual userid), you cannot write your files. :)) Meanwhile, an other user (who is accidentally given that particular userid) may still have write permission to your file, despite of your precaution. :)) Funny, isn't it? As a consequence, noone should restrict the right permissions in such a way that the group does not have write permissions. But this also has a consequence: practically anyone has write permissions to your data, plus you have write permissions for the Nobel prize winner CMS Higgs DST files... Let's hope this conceptional mistake will be corrected soon.
 
Deleted:
<
<
-- AndrasLaszlo - 06 Mar 2006
 
Added:
>
>
  • Read/write C++ streams to storage elements of the LCG:
 
Changed:
<
<
META FILEATTACHMENT attr="" autoattached="1" comment="Framework for a simple job" date="1141665617" name="skeleton.tar.gz" path="skeleton.tar.gz" size="4071" user="Main.AndrasLaszlo" version="1"
>
>
As one does generally not want to always stage out the data files to a local disk by hand, and then process it, it is recommended to have read/write streams. Unfortunately, such official streams are not available, yet. Therefore I wrote grid storage i/o stream C++ classes (gstream, igstream, ogstream, like the usual C++ STL fstream, ifstream, ofstream file input/output stream classes; the letter 'g' standing for 'grid'). It does nothing else, but treats the file as a normal file, unless its name begins with the string /grid/. In this case, it stages out the datafile in question onto a local (or AFS) area, and then treats the local file as a normal file. One commonly faces the problem that the file not only has to be processed, but it also has to be passed through a filter programme. Therefore I also wrote pipe streams for grid storage (gpstream, igpstream, ogpstream), which are based on the ipstream and opstream classes of the library at http://pstreams.sourceforge.net (note the LGPL license!). Some practical examples:

#include "gstream.h"

int main(int argc, char *argv[])
{
    // Open the datafile for reading.
    igstream ifile("/grid/cms/alaszlo/some_datafile.dat");
        // Extract data from your datafile with 'igstream::operator>>' or with 'igstream::read(char*, int)'.
    // Close the datafile.
    ifile.close();

    // Open the datafile for writing.
    ogstream ofile("/grid/cms/alaszlo/some_datafile.dat");
        // Write data to your datafile with 'ogstream::operator<<' or with 'ogstream::write(char*, int)'.
    // Close the datafile.
    ofile.close();

    // Open the datafile for reading, through a filter program.
    igpstream ipfile("/grid/cms/alaszlo/some_datafile.gz", "gunzip --stdout %f");
        // Extract data from your datafile with 'igpstream::operator>>' or with 'igpstream::read(char*, int)'.
    // Close the datafile.
    ipfile.close();

    // Open the datafile for writing.
    ogpstream opfile("/grid/cms/alaszlo/some_datafile.dat.gz", "gzip - > %f");
        // Write data to your datafile with 'ogpstream::operator<<' or with 'ogpstream::write(char*, int)'.
    // Close the datafile.
    opfile.close();

    return 0;
}

You can get the library files here: pstream.h, gstream.h, gstream.cc. Before you can use it you have to export the following environmental variables:

export VO = your_vo (for bash), or setenv VO your_vo (for tcsh), and

export DEST = your_favourite_storage_element (for bash), or setenv DEST your_favourite_storage_element (for tcsh).

Setting the environmental variable TMPDIR is optional. This specifies the local (or AFS) directory, where the datafiles are staged out (therefore, it has to have large disk space!). E.g.:

export TMPDIR = /tmp (for bash), or setenv TMPDIR /tmp (for tcsh).

If not specified, the current working directory ($PWD) is used, as this is recommended for grid jobs (the working nodes have large disk spaces).

-- AndrasLaszlo - 17 Mar 2006

META FILEATTACHMENT attr="" autoattached="1" comment="Framework for a simple job" date="1142615719" name="skeleton.tar.gz" path="skeleton.tar.gz" size="18566" user="Main.AndrasLaszlo" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="Pipe stream library (consists of a single header file)" date="1142615864" name="pstream.h" path="pstream.h" size="62228" user="Main.AndrasLaszlo" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Grid i/o stream library (header file)" date="1142615914" name="gstream.h" path="gstream.h" size="3508" user="Main.AndrasLaszlo" version="1"
 
META FILEATTACHMENT attr="" autoattached="1" comment="Framework for a simple job" date="1141385472" name="skeleton.tar" path="skeleton.tar" size="30720" user="Main.AndrasLaszlo" version="1"
Changed:
<
<
META FILEATTACHMENT attr="" autoattached="1" comment="A simple LCG mass submitter framework" date="1141665685" name="submit.tar.gz" path="submit.tar.gz" size="7791" user="Main.AndrasLaszlo" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Copy and register complete directory trees into Logical File Catalogue" date="1141665733" name="lcgcr.sh" path="lcgcr.sh" size="3866" user="Main.AndrasLaszlo" version="1"
>
>
META FILEATTACHMENT attr="" autoattached="1" comment="Grid i/o stream library (source code)" date="1142615960" name="gstream.cc" path="gstream.cc" size="10390" user="Main.AndrasLaszlo" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="A simple LCG mass submitter framework" date="1142615756" name="submit.tar.gz" path="submit.tar.gz" size="22353" user="Main.AndrasLaszlo" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="Copy and register complete directory trees into Logical File Catalogue" date="1142615800" name="lcgcr.sh" path="lcgcr.sh" size="3866" user="Main.AndrasLaszlo" version="2"
 
META FILEATTACHMENT attr="" autoattached="1" comment="A simple LCG mass submitter framework" date="1141385536" name="submit.tar" path="submit.tar" size="61440" user="Main.AndrasLaszlo" version="1"
META TOPICMOVED by="AndrasLaszlo" date="1141225754" from="CMS.WebTopicCreator" to="CMS.LHCComputingGrid"
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback