|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
07 Sep 2016, Wes Gohn, Forum, ODB as JSON file
|
07 Sep 2016, Stefan Ritt, Forum, ODB as JSON file
|
08 Sep 2016, Pierre-Andre Amaudruz, Forum, ODB as JSON file
|
30 Sep 2016, Konstantin Olchanski, Forum, ODB as JSON file
|
|
Message ID: 1195
Entry time: 08 Sep 2016
In reply to: 1194
|
Author: |
Pierre-Andre Amaudruz |
Topic: |
Forum |
Subject: |
ODB as JSON file |
|
|
Hi,
We do generate a .json odb at the end of run in order to extract some of its info for our CouchDB.
This is done using the "/program/Execute on stop run" script command. This method decouples the necessity
to describe completely the info extraction within the ODB/Logger/"CouchDB" and provides possibly better
flexibility. But including a CouchDB support in the logger as well (like SQL) would be nice too.
Pierre-André
> > Hi. Is it currently possible to automatically save the MIDAS ODB as a JSON file?
> > I can do it manually in odbedit, but it looks like the only option for the
> > automatic ODB save for each run is the standard .ODB format. Is there a way to
> > change this?
>
> You mean you like an ODB dump at the end of every run in JSON format?
>
> Sure this can be implemented. But I wonder for what purpose you need that. Can you elaborate a
> bit, maybe it's a useful feature also other people should be aware of. I'm also thinking if we should
> offer a CouchDB interface, so ODB data is written directly to that database.
>
> Stefan |