Extacting the OCDB in a separate module. The detectors have write permission in the...

[u/mrichter/AliRoot.git] / MUON / READMEcalib.txt

diff --git a/MUON/READMEcalib.txt b/MUON/READMEcalib.txt
index f72b2901fc584c30dceaea82e77d9f65766cfb75..6875d3afa970f5212049d714c8c34f764d57bb23 100644 (file)
--- a/MUON/READMEcalib.txt
+++ b/MUON/READMEcalib.txt
@@ -48,11 +48,14 @@ One very important notion is that of the DefaultStorage (which you might set wit
  AliCDBManager::Instance()->SetDefaultStorage(path)), which tells the CDB library where
  the CDB is sitting (either locally on disk, or on the grid).
 
-For local tests, path will be most likely = local://$ALICE_ROOT/MUON 
+For local tests, path will be most likely = <code> "local://$ALICE_ROOT/OCDB"</code>
 (i.e. there is, in CVS a slim version of the calibration objects needed
-  for running the MUON code), or local://$ALICE_ROOT/SHUTTLE/TestShuttle/TestCDB for Shuttle testing.
- 
+for running the MUON code), or <code> "local://$ALICE_ROOT/OCDB/SHUTTLE/TestShuttle/TestCDB </code>
+for Shuttle testing.
 
+When using alien, the path definition can be eg.
+<code> "alien://folder=/alice/data/2007/LHC07w/OCDB" </code>. 
+ 
 \section calib_s3 Writing to CDB
  
 AliMUONCDB class is used to populate the CDB with fake calibration objects for testing purposes.
@@ -65,11 +68,13 @@ the Root prompt (from within the $ALICE_ROOT/MUON directory to get the correct
 list of libraries loaded by the loadlibs.C macro)
 
 <pre>
-root[0] AliMUONCDB cdb;
-root[1] Int_t startRun = 0;
-root[2] Bool_t defaultValues = kTRUE;
-root[3] cdb.WriteTrigger(startRun);
-root[4] cdb.WriteTracker(defaultValues,startRun);
+root[0] AliMpCDB::LoadDDLStore2(); 
+root[1] AliMpCDB::LoadManuStore2(); 
+root[2] AliMUONCDB cdb;
+root[3] Int_t startRun = 0;
+root[4] Bool_t defaultValues = kTRUE;
+root[5] cdb.WriteTrigger(startRun);
+root[6] cdb.WriteTracker(defaultValues,startRun);
 </pre>