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: 1927     Entry time: 03 Jun 2020     In reply to: 1923     Reply to this: 1929
Author: Konstantin Olchanski 
Topic: Bug Report 
Subject: wrong run number 
> I build MIDAS and ROOTANA using same tag (midas-2020-03-a, rootana-2020-03-a):
>
> MVOdb::SetMidasStatus: Error: MIDAS db_get_value() at ODB path "//runinfo/Run 
> number" returned status 312
>
> it seems that some function try to get "//runinfo/Run number" (double slash) 
> instead of "/runinfo/Run number"...
> 

You made a mistake somewhere.

rootana release rootana-2020-03 uses VirtualOdb, not MVOdb, so there should be no 
messages from "MVOdb". ODB path "/runinfo/run number" is correct for the 
VirtualOdb classes. MVOdb classes use relative paths, absolute path starting from 
"/" is not permitted, hence the error.

You most likely are using the master branch of rootana.

Commit switching rootana from VirtualOdb to mvodb was made after the release 2020-
03, in May:
https://bitbucket.org/tmidas/rootana/commits/522cd07181c59f557e9ef13a70223ec44be44
bc9

(I confirm the incorrect call to RI("/runinfo/..."), Thomas already fixed it in 
the repository, big thanks!).

The dust is not fully settled yet on the refactoring of rootana, until then, I 
recommend that people use the release version(s).

K.O.
ELOG V3.1.4-2e1708b5