Difference: LHCComputingGrid (10 vs. 11)
Revision 112006-03-19 - 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: 87 to 87 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < | 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: | |||||||
| > > | 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 (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" | ||||||||
| Line: 107 to 107 | ||||||||
| ofile.close(); // Open the datafile for reading, through a filter program. | ||||||||
| Changed: | ||||||||
| < < | igpstream ipfile("/grid/cms/alaszlo/some_datafile.gz", "gunzip --stdout %f"); | |||||||
| > > | igpstream ipfile("/grid/cms/alaszlo/some_datafile.dat.gz", "gunzip --stdout %f"); | |||||||
| // Extract data from your datafile with 'igpstream::operator>>' or with 'igpstream::read(char*, int)'. // Close the datafile. ipfile.close(); | ||||||||
| Line: 136 to 136 | ||||||||
If not specified, the current working directory ($PWD) is used, as this is recommended for grid jobs (the working nodes have large disk spaces). | ||||||||
| Changed: | ||||||||
| < < | -- AndrasLaszlo - 17 Mar 2006 | |||||||
| > > | -- AndrasLaszlo - 19 Mar 2006 | |||||||
| ||||||||
View topic | History: r16 < r15 < r14 < r13 | More topic actions...
Copyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback