EJTermPreWorkshopOnlineWork < Sandbox

---+ !!Extended JTerm Pre-Workshop Exercises - First Set - 15 Oct 2009 

%TOC{title="Contents:"}%


---++ Introduction
The purpose of the pre-workshop exercises is for prospective workshop attendees to become familiar with the basic software tools required to perform physics analysis at CMS.  Please run and complete these exercises and post the results in the online form provided.The exercises are standalone. A large amount of additional  information about these exercises is available in the twikis that we reference. Please remember that  twikis evolve but aim to provide the best information at any time. 

<BIG>%RED%To perform the first set of exercises an LPC account is required.%ENDCOLOR% </BIG>

---++ How to obtain an LPC computer account 
   * [[https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookRemoteSiteSpecifics#FermiLab][cmslpc account]]
      * Exercises will be performed on =cmslpc.fnal.gov= cluster.
  
%BR%

<BIG> *When logging in to =cmslpc= from a windows machine, the following links might be helpful:* </BIG>

   * [[http://www-cdf.fnal.gov/~cplager/cygwin/kerberos.html][Windows Kerberos at FNAL]]
   * [[http://www-cdf.fnal.gov/~cplager/cygwin/][Hints for setting up Cygwin]]

<BIG>%RED% AFTER the above you are ready for the exercises below %ENDCOLOR% </BIG>
<BIG>%RED% We assume that you are familiar with basic unix commands like =ls=, =ls -altrh=, =cp= etc. and can edit a file using any of the editors like =pico=, =emacs=, =nedit= etc. %ENDCOLOR% </BIG>

---++ Exercise 1 - Cut and Paste
Login to *cmslpc.fnal.gov*
<p>
To verify if cut and paste from one window to another works, cut and paste the following and then hit return

<pre>
~cplager/runThisCommand.py "asdf;klasdjf;kakjsdf;akjf;aksdljf;a"\
"sldjfqewradsfafaw4efaefawefzdxffasdfw4ffawefawe4fawasdffadsfef"
</pre>
The response should be  your username followed by alphabets unique to your username, for example like this:
<pre>success: malik znyvx </pre>
%RED% QUESTION - Post this unique alphanumeric characters.%ENDCOLOR%
<p>If you only run the command without any cut and paste, like the following:
<pre>
somebody@cmslpc11> ~cplager/runThisCommand.py
</pre>
you should get 
<pre>
Error: You must provide the secret key
</pre>
If you paste incorrectly, you should get
<pre>
Error: You didn't paste the correct input string
</pre>
If you run it from a wrong computer ( not cmslpc, say from your laptop locally), you should get
<pre>
bash: ~cplager/runThisCommand.py: No such file or directory
</pre>
OR
<pre>
Unknown user: cplager.
</pre>

---++ Exercise 2 - Simple Edit Exercise  

This is to test and make sure that the user can edit files on cmslpc.
<p>
Log into cmslpc, run this command:

<pre>cp ~cplager/editThisCommand.py . </pre>

Then open <tt>editThisCommand.py</tt> in your editor and edit the 11th line adding a <tt> # </tt>(hash character) to the front of the line. So the lines should start of looking like this:
<p>
<pre>
# Please comment the line below out by adding a '#' to the front of
# the line.
raise RuntimeError, "You need to comment out this line with a #"
</pre>

and be changed to:
<pre>
# Please comment the line below out by adding a '#' to the front of
# the line.
#raise RuntimeError, "You need to comment out this line with a #"
</pre>

Save the file and run the command:
<pre>
user@cmslpc12> ./editThisCommand.py
</pre>

If this is successful, you will see this

<pre>
cplager@cmslpc12> ./editThisCommand.py
success:  cplager 0x1851DCBA
</pre>

%RED% QUESTION - Paste the bottom line into the window. %ENDCOLOR%
<p>
If you did not successfully edit the file, you'll see an error message such as this:
<pre>
cplager@cmslpc12> ./editThisCommand.py
Traceback (most recent call last):
  File "./editThisCommand.py", line 11, in ?
    raise RuntimeError, "You need to comment out this line with a #"
RuntimeError: You need to comment out this line with a #
</pre>

---++ Exercise 3 - Setup a release area CMSSW_3_1_4
<verbatim>
source /uscmst1/prod/sw/cms/cshrc uaf 
cmscvsroot CMSSW
mkdir YOURWORKINGAREA
cd YOURWORKINGAREA
scram p CMSSW CMSSW_3_1_4
cd CMSSW_3_1_4/src
cmsenv
</verbatim>

Run the following command:
<pre> echo $CMSSW_BASE</pre>
%RED% QUESTION - Paste the output of the above command %ENDCOLOR%



---++ Exercise 4 - Find data in DBS ( Database Bookkeeping Service)
Go to the url [[https://cmsweb.cern.ch/dbs_discovery/][DBS discovery]] and in the menu driven interface, choose the info from the pull down menu,
so that your choices look like this:

%TWISTY{mode="div" showlink="Show result..." hidelink="Hide result..." remember="on" 
                showimgleft="%ICONURLPATH{toggleopen-small}%" 
                hideimgleft="%ICONURLPATH{toggleclose-small}%"}%

<img src="%ATTACHURLPATH%/DBS_snapshot.png" alt="DBS_snapshot.png" width='594' />

%ENDTWISTY%

then click on "Find" and after few seconds it brings another page. On this page there are two data sets. Look for the one that says:
=/RelValTTbar/CMSSW_3_1_4-STARTUP31X_V2-v1/GEN-SIM-RECO=. 

%RED% QUESTIONS - What is the size of this data? Click on "plain" to see the number of files it contains. How many files does it have?
Is this data at FNAL? %ENDCOLOR%

The files it contains should look like this
<verbatim>
       '/store/relval/CMSSW_3_1_4/RelValTTbar/GEN-SIM-RECO/STARTUP31X_V2-v1/0006/AC0641BB-73B1-DE11-A138-001D09F291D2.root',
       ...................................................
</verbatim>

More information about on accessing data in DBS can be found in [[https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookDataSamples][WorkBookDataSamples]]

---++ Exercise 5 - EDM ( Event Data Model framework) standalone utilities - =edmDumpEventContent=, =edmProvDump=, =edmEventSize= 

The overall collection of CMS software, referred to as [[https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookCMSSWFramework][CMSSW]], is built around a Framework, an Event Data Model ([[https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookCMSSWFramework#EdM][EDM]]), and Services needed by the simulation, calibration and alignment, and reconstruction modules that process event data so that physicists can perform analysis. The primary goal of the Framework and EDM is to facilitate the development and deployment of reconstruction and analysis software. The CMS Event Data Model (EDM) is centered around the concept of an Event. An Event is a C++ object container for all RAW and reconstructed data related to a particular collision.To understand what is in a datafile  and more,  several EDM utilities are available. In this exercise, one will use three of the several EDM utilities available. 
They would very useful throughout one's physics analysis beyond this workshop. More on these EDM utilities can be found at [[https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookEdmUtilities][WorkBookEdmUtilities]]. These together with [[http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/][CMSSW]] and [[http://cmslxr.fnal.gov/lxr/source/][CMS LXR Cross Referencer]] can help you understand the CMS code and also write your own analysis specific code.

   * Use =edmDumpEventContent= to see what class names etc. to use in order to access the objects in the RECO data file you located above
      * To do this do <verbatim> edmDumpEventContent --all --regex caloJet dcap:///pnfs/cms/WAX/11/store/relval/CMSSW_3_1_4/RelValTTbar/GEN-SIM-RECO/STARTUP31X_V2-v1/0006/AC0641BB-73B1-DE11-A138-001D09F291D2.root > EdmDumpEventContent.txt </verbatim>
      * Note how =/pnfs/cms/WAX/11/= has been prefixed to the file name. Adding this gives you the [[https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookDataSamples#DlS][physical location]] of the file at Fermilab.
      * Open and look at the file =EdmDumpEventContent.txt=. It has information divided into four columns (roughly).  The first column is C++ class =type of the data=, second is =module label=, third is =product instance label= and fourth is =process name=. You can read more at  [[https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookCMSSWFramework#ModularEvtContent][Identifying Data in the Event]].
      * %RED% QUESTION - How many types of CaloJet module labels are there? What are there names %ENDCOLOR%
      * NOTE: Instead of the above you can also try above without options =--all --regex caloJet= . This will dump the entire event content as follows:
         * To do this do <verbatim> edmDumpEventContent dcap:///pnfs/cms/WAX/11/store/relval/CMSSW_3_1_4/RelValTTbar/GEN-SIM-RECO/STARTUP31X_V2-v1/0006/AC0641BB-73B1-DE11-A138-001D09F291D2.root > EdmDumpEventContent.txt </verbatim>
         * This is a file with many more lines than the one with option =--all --regex caloJet= .

   * To aid in understanding the full history of an analysis, the framework accumulates provenance for all data stored in the standard ROOT output files.  Using =edmProvDump= one can print out all the tracked parameters which were used to create the data file. One can see what modules were run, CMSSW version etc. used when the RECO file was made. To use it do
      * To do this do <verbatim> edmProvDump    dcap:///pnfs/cms/WAX/11/store/relval/CMSSW_3_1_4/RelValTTbar/GEN-SIM-RECO/STARTUP31X_V2-v1/0006/AC0641BB-73B1-DE11-A138-001D09F291D2.root > EdmProvDump.txt </verbatim>
      * NOTE: =EdmProvDump.txt= is a huge file. Open and look at this file and locate  =Processing History= ( about 20 lines from the top). 
      * %RED% QUESTION - Which version of CMSSW_?_?_? does the processing history say that was used for processing the data? %ENDCOLOR%

   * You can use =edmEventSize= to know the size of different branches in your data file. The details about are here [[https://twiki.cern.ch/twiki/bin/view/CMS/SWGuideEdmEventSize][SWGuideEdmEventSize]]
      * To do this do <verbatim>edmEventSize -v dcap:///pnfs/cms/WAX/11/store/relval/CMSSW_3_1_4/RelValTTbar/GEN-SIM-RECO/STARTUP31X_V2-v1/0006/AC0641BB-73B1-DE11-A138-001D09F291D2.root > EdmEventSize.txt </verbatim>
      * Open and look at file =EdmEventSize.txt= and locate the line =recoCaloJets_antikt5CaloJets__RECO.=. There are two numbers next to it that measure plain and the compressed size of this branch.
      * %RED% QUESTION - What are two numbers next to above line? Write them.%ENDCOLOR%
    
---++ Exercise 6 - Make a PATtuple  where PAT means Physics Analysis ToolKit
What is a PATuple and all about it can be found at [[https://twiki.cern.ch/twiki/bin/view/CMS/SWGuidePAT][SWGuidePAT]] and the latest [[http://indico.cern.ch/conferenceOtherViews.py?view=standard&confId=63293][PAT tutorial]].

<p>Using the [[https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookPATSimpleExample][WorkBookPATSimpleExample]] in Module 1 of [[http://indico.cern.ch/conferenceOtherViews.py?view=standard&confId=63293][PAT tutorial]], we will plot the =Pt= distribution of the PAT muons. Note that we will use the datafile ( which is a RECO file) that you found above in the DBS instead of the default data file used in Module 1 ( you can dig out the default file later) but for now we will simply make a PAT tuple called =simplePAT.root=. 

Make sure at this point your are in the directory =YOURWORKINGAREA/CMSSW_3_1_4/src=
To complete this exercise follow these steps:

<p>
1. Open your favorite editor and cut paste the contents of the file [[%ATTACHURL%/simplePAT314_cfg.py.txt][simplePAT_cfg.py]]. Save this file as =simplePAT_cfg.py=.
<p>
2. Now run the following command
<pre>cmsRun simplePAT_cfg.py</pre>
While this command is executed you will see an output like [[%ATTACHURL%/simplePAT314.log][this]].
<p>
3. Now open the root file you just created. Note that this file is created in the =YOURWORKINGAREA/CMSSW_3_1_4/src= directory where you should always be for this tutorial. To open the root file do:
<pre> root -l simplePAT.root</pre>
<p>
On root prompt type =root [1] gStyle->SetOptStat(111111);= and then =TBrowser b;= like this
<pre>root [1] gStyle->SetOptStat(111111);</pre>
<pre>root [1] TBrowser b;</pre>
This opens a window that looks like this:

%TWISTY{mode="div" showlink="Show result..." hidelink="Hide result..." remember="on" 
                showimgleft="%ICONURLPATH{toggleopen-small}%" 
                hideimgleft="%ICONURLPATH{toggleclose-small}%"}%

<img src="%ATTACHURLPATH%/root1.png" alt="root1.png" width='594' />

%ENDTWISTY%

On this window click on =ROOT Files= on the left menu and now the window looks like this:
%TWISTY{mode="div" showlink="Show result..." hidelink="Hide result..." remember="on" 
                showimgleft="%ICONURLPATH{toggleopen-small}%" 
                hideimgleft="%ICONURLPATH{toggleclose-small}%"}%

<img src="%ATTACHURLPATH%/root2.png" alt="root2.png" width='594' />
%ENDTWISTY%

Click =simplePAT.root=, then on =Events=, then on  =patMuons_cleanLayer1Muons__PAT= and  then on =patMuons_cleanLayer1Muons__PAT.obj=.
You should now see a window that looks like this:

%TWISTY{mode="div" showlink="Show result..." hidelink="Hide result..." remember="on" 
                showimgleft="%ICONURLPATH{toggleopen-small}%" 
                hideimgleft="%ICONURLPATH{toggleclose-small}%"}%

<img src="%ATTACHURLPATH%/root6.png" alt="root6.png" width='594' />
%ENDTWISTY%

Scroll way down ( not too fast) and click on =pt()=. You should now see PAT Muon Pt distribution. 
%BR%
%RED% QUESTION - What is the mean value of the muon pt()? %ENDCOLOR%

---++ Get Grid Certificate  and CMS VO registration
Use the following link for this: [[https://twiki.cern.ch/twiki/bin/view/Main/CRABPrerequisitesGRIDCredentials][Get Your Grid Certificate and CMSVO]]

---++ Get CERN account

 * Use the following link for CMS CERN account: [[https://cernaccount.web.cern.ch/cernaccount/Externals.aspx][CMS CERN account]]
      * CERN acount is needed to login in to any elearning web-site ( later used in the final tutorial), to get a file from afs area or any future need you may have beyond the tutorial.
      * *To keep the information flow going for CERN account, please ask your team leader do the necessary "signing" after the online form has been treated by the secretariat.*


---++ Exercise 7 - Fireworks - CMS Event Display
Fireworks is CMS' graphical tool to display events for physics. We have renamed the file =/pnfs/cms/WAX/11/store/relval/CMSSW_3_1_4/RelValTTbar/GEN-SIM-RECO/STARTUP31X_V2-v1/0006/AC0641BB-73B1-DE11-A138-001D09F291D2.root= that you have been working with to EJTermDataForEventDisplay.root for simplicity. 
<p>
There are the following two ways that one can star event display. Please be a little patient as few messages would pop up on the screen and it will take few seconds to open ( may be up to a minute).
<p>
*******************************************************************************************************************
<p> 1. From cmslpc account ( slow but easy)
   * To run it from your cmslpc account, run the following command from your =YOURWORKINGAREA/CMSSW_3_1_4/src= working area
<pre>cmsShow /uscms_data/d2/malik/EJTERM/CMSSW_3_1_4/src/EJTermDataForEventDisplay.root </pre> 

You can also run directly as follows by using the data file's  url location as follows:
<pre>cmsShow http://www-d0.fnal.gov/~malik/EJTermDataForEventDisplay.root</pre>
<p>
*******************************************************************************************************************
<p> 2. Running it locally on your desktop ( fast BUT one has to download the fireworks distribution locally on one's desktop)
   * Using the recipe at [[https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookFireworks][WorkBookFireworks]] download the 31X distribution locally on your laptop
   * Then change to the directory to =cmsShow31= by doing 
<verbatim>
cd cmsShow31
</verbatim>
   * Then download the data file as follows
      * For LINUX laptop
<pre>wget http://www-d0.fnal.gov/~malik/EJTermDataForEventDisplay.root</pre>
      * For Macintosh laptop
<pre>curl http://www-d0.fnal.gov/~malik/EJTermDataForEventDisplay.root > EJTermDataForEventDisplay.root  </pre>
<p>
 After you download the fireworks distribution run the following commands from your desktop's local command prompt to display fireworks ( you must be in the directory called =cmsShow31=.
<p>
<verbatim>
./cmsShow EJTermDataForEventDisplay.root
</verbatim>

<p> In case you do not want to download the file locally, you can run it directly from its url location as follows:
<pre>./cmsShow http://www-d0.fnal.gov/~malik/EJTermDataForEventDisplay.root</pre></pre>
<p>
*******************************************************************************************************************

Following either of the above method, the event display should start.  You may =UNCEHCK= all the objects in the =summary view= on the left  EXCEPT =tracks=. You should now be seeing the following type of graphics ( with just green tracks)

%TWISTY{mode="div" showlink="Show result..." hidelink="Hide result..." remember="on" 
                showimgleft="%ICONURLPATH{toggleopen-small}%" 
                hideimgleft="%ICONURLPATH{toggleclose-small}%"}%

<img src="%ATTACHURLPATH%/Event5300.png" alt="Event5300.png" width='594' />
%ENDTWISTY%

Once you have event display started three windows will open. We ignore the two small ones. The event display will display the first event. You can use the arrows on the top to go to next event or play/pause through all events.

To do the exercise do the following  steps:
<ol>
<li>Write event number =8550= where you see event displayed as =8501=, press enter.</li>
<li>Now you should see the green tracks displayed for event 8550.  Not all the tracks are displayed though.</li>
<li>Click on the little arrow button on the left of the =Tracks= in the  =summary view= </li>
<li>This will pull a display of all the tracks, showing pt, eta, phi etc.,  like this:</li>
%TWISTY{mode="div" showlink="Show result..." hidelink="Hide result..." remember="on" 
                showimgleft="%ICONURLPATH{toggleopen-small}%" 
                hideimgleft="%ICONURLPATH{toggleclose-small}%"}%
<img src="%ATTACHURLPATH%/Menu.png" alt="Menu.png" width='594' />
%ENDTWISTY%
<li>Scroll down and see how many tracks this event has.</li>
<li> %RED% QUESTION - What are the number of tracks in this event 8550? %ENDCOLOR% </li>
<li>You can of course play with other buttons and menu.</li>
</ol>


---++ Exercise 8 - Grid/Crab exercises  ( A valid Grid Certificate and CMS VORMS membership is a pre-requisite for this) - to be completed by ERIC VAANDERING

   * a. Exercise on having a grid certificate
   * b. Getting a /store/user area from your assigned Tier2
   * c. Running a Grid Job 

---++ Exercise 9 - Run EDAnalyzer to make your PATtuple

If you want to manipulate, analyze, draw histograms etc.  from the data in the PATtuple, you need can do it using EDAnalyzer or in FWLite.
More on these can be found on [[https://twiki.cern.ch/twiki/bin/view/CMS/WorkBookWriteFrameworkModule][WorkBookWriteFrameworkModule]] and [[https://twiki.cern.ch/twiki/bin/view/CMS/PhysicsToolsFWLiteExecutable][FWLiteExecutable]]. While EDAnalyzer needs full framwork to run, FWLite can be run on your laptop by downloading the appropriate FWLite distribution. 

<p>
In the =/YOURWORKINGAREA/CMSSW_3_1_4/src= directory cut and paste the following commands ( you can select all and paste all together and commands will be executed sequentially)
<verbatim>
cvs co -r patTutorial_sept09_module1 PhysicsTools/PatExamples/src  
cvs co -r patTutorial_sept09_module1 PhysicsTools/PatExamples/interface  
cvs co -r patTutorial_sept09_module1 PhysicsTools/PatExamples/BuildFile  
cvs co -r patTutorial_sept09_module1 PhysicsTools/PatExamples/plugins/BuildFile  
cvs co -r patTutorial_sept09_module1 PhysicsTools/PatExamples/plugins/PatBasicAnalyzer.cc  
cvs co -r patTutorial_sept09_module1 PhysicsTools/PatExamples/test/analyzePatBasics_cfg.py
</verbatim>

To run, you need to compile the code by doing the following
<pre>scram b </pre>

Now you open the file (using your favourite editor), like this
<pre>pico  PhysicsTools/PatExamples/test/analyzePatBasics_cfg.py</pre>
and change the input file to "simplePAT.root you created in Exercise 4. This is done like below in the config file =analyzePatBasics_cfg.py=

<pre>
process.source = cms.Source("PoolSource",
  fileNames = cms.untracked.vstring(
    'file:simplePAT.root'
  )
)

</pre>

To run the code do ( assuming you are still in the =src= directory)
<pre>
cmsRun PhysicsTools/PatExamples/test/analyzePatBasics_cfg.py
</pre>
After the config file runs, you should see a file called =analyzePatBasics.root= . Browse through different histograms. 
%BR%
%RED% QUESTIONS - How many histograms are there? Which histogram is empty? %ENDCOLOR%


---++ Exercise 10  - FWLite exercises

Go through the twiki  - [[https://twiki.cern.ch/twiki/bin/view/CMS/PhysicsToolsFWLiteExecutable][FWLiteExecutable]]

Note that FWLite twiki tells you to be in a working area by saying =cd $CMSSW_BASE/src=. You are already working in that area called =YOURWORKINGAREA/CMSSW_3_1_4/src=. Even if you execute the command =cd $CMSSW_BASE/src= you stay in the same working area where you already are.

AFTER completing the exercises on the twiki:
%BR%
Open the root file =myZPeakModified.root= and draw the modified Z-peak as follows:
<verbatim>
root -l myZPeakModified.root
root [0] Zmass->Draw();
</verbatim>

%RED% QUESTION - Report the mean of the MODIFIED Z Mass. %ENDCOLOR%



Questions/Problems/Suggestion -  mailto: malik@fnal.gov , Phone - 630-840-6441

-- Main.SudhirMalik - 2009-10-06
Attachments
Topic attachments
I	Attachment	History	Action	Size	Date	Who
ext	CondorJob_samplePAT	r1	manage	0.6 K	2009-10-09 - 03:49	SudhirMalik
png	DBS.png	r1	manage	69.3 K	2009-10-13 - 05:20	SudhirMalik
png	DBS_snapshot.png	r1	manage	100.2 K	2009-10-16 - 03:26	SudhirMalik
txt	EdmDumpEventContent.txt	r1	manage	31.3 K	2009-10-13 - 06:02	SudhirMalik
txt	EdmEventSize.txt	r1	manage	19.2 K	2009-10-13 - 06:04	SudhirMalik
txt	EdmProvDump.txt	r1	manage	643.2 K	2009-10-13 - 06:03	SudhirMalik
png	Event5300.png	r1	manage	194.4 K	2009-10-09 - 03:54	SudhirMalik
pdf	GridTaskMonitoring.pdf	r1	manage	119.5 K	2009-10-09 - 03:53	SudhirMalik
png	Menu.png	r1	manage	22.9 K	2009-10-09 - 03:54	SudhirMalik
png	MuonMultDist.png	r1	manage	22.5 K	2009-10-07 - 22:54	SudhirMalik
png	Muon_pt.png	r1	manage	22.4 K	2009-10-13 - 06:26	SudhirMalik
png	Tracks.png	r1	manage	74.0 K	2009-10-09 - 03:53	SudhirMalik
txt	condorjob.txt	r1	manage	0.8 K	2009-10-09 - 07:58	SudhirMalik
cfg	crab.cfg	r1	manage	0.6 K	2009-10-09 - 03:49	SudhirMalik
png	root1.png	r1	manage	17.0 K	2009-10-09 - 06:03	SudhirMalik
png	root2.png	r1	manage	18.4 K	2009-10-09 - 06:03	SudhirMalik
png	root3.png	r1	manage	21.1 K	2009-10-09 - 06:04	SudhirMalik
png	root4.png	r1	manage	23.5 K	2009-10-09 - 06:04	SudhirMalik
png	root5.png	r1	manage	26.8 K	2009-10-09 - 06:04	SudhirMalik
png	root6.png	r1	manage	33.9 K	2009-10-09 - 06:04	SudhirMalik
png	root7.png	r1	manage	21.3 K	2009-10-09 - 06:05	SudhirMalik
csh	simplePAT.csh	r1	manage	0.3 K	2009-10-09 - 03:50	SudhirMalik
txt	simplePAT.csh.txt	r1	manage	0.3 K	2009-10-09 - 07:42	SudhirMalik
log	simplePAT.log	r1	manage	29.9 K	2009-10-13 - 07:56	SudhirMalik
log	simplePAT314.log	r1	manage	29.9 K	2009-10-13 - 08:01	SudhirMalik
txt	simplePAT314_cfg.py.txt	r1	manage	0.6 K	2009-10-13 - 08:57	SudhirMalik
condorlog	simplePAT_313451.condorlog	r1	manage	1.0 K	2009-10-09 - 03:48	SudhirMalik
stdout	simplePAT_313451.stdout	r1	manage	0.1 K	2009-10-09 - 03:49	SudhirMalik
txt	simplePAT_cfg.py.txt	r1	manage	0.5 K	2009-10-13 - 06:32	SudhirMalik
Topic revision: r24 - 2009-10-18 - SudhirMalik
Account
- Log In
- Cern Search
- TWiki Search
- Google Search
Sandbox All webs
Edit
Attach
Copyright &© 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback