Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  30 May 2020, Gennaro Tortone, Bug Report, wrong run number 
    Reply  30 May 2020, Thomas Lindner, Bug Report, wrong run number 
       Reply  30 May 2020, Gennaro Tortone, Bug Report, wrong run number 
       Reply  03 Jun 2020, Konstantin Olchanski, Bug Report, wrong run number 
    Reply  03 Jun 2020, Konstantin Olchanski, Bug Report, wrong run number 
       Reply  03 Jun 2020, Gennaro Tortone, Bug Report, wrong run number 
          Reply  04 Jun 2020, Konstantin Olchanski, Bug Report, wrong run number 
Message ID: 1928     Entry time: 03 Jun 2020     In reply to: 1925
Author: Konstantin Olchanski 
Topic: Bug Report 
Subject: wrong run number 
> 
> But Konstantin will need to explain how this class is supposed to be used more generally.
>

MVOdb is a replacement for VirtualOdb. It has many functions that were missing in VirtualOdb
and it implements access to both XML and JSON ODB dumps.

>  The example programs have a mix with sometimes needing leading slashes and other times not:
> 
> libAnalyzer/TRootanaEventLoop.cxx:   fODB->RI("runinfo/Run number", &fCurrentRunNumber);
> old_analyzer/analyzer.cxx:   gOdb->RI("runinfo/Run number", &gRunNumber);

RI() is MVOdb, no absolute paths, leading "/" not permitted.

> manalyzer/manalyzer.cxx:   int run_number = midas->odbReadInt("/runinfo/Run number");
> manalyzer/manalyzer_v0.cxx:   int run_number = midas->odbReadInt("/runinfo/Run number");

Hmmm... good catch. these are VirtualOdb calls, but they bypass the VirtualOdb interface (which was removed)
and call the odb access methods directly from the TMidasOnline class. They should be replaced
with MVOdb RI() calls (and leading "/" removed).

I was going to look at the TMidasOnline class next - many things need to be updated,
but it will have to wait until I update the MVOdb and the tmfe documentation and until
I update midasio to read and write the new bank32a data files.

K.O.
ELOG V3.1.4-2e1708b5