|
|
|
Back
Midas
Rome
Roody
Rootana
|
| Midas DAQ System |
Not logged in |
 |
|
|
 01 May 2020, Joseph McKenna, Forum, Taking MIDAS beyond 64 clients
|
 01 May 2020, Stefan Ritt, Forum, Taking MIDAS beyond 64 clients
| |
01 May 2020, Pierre Gorel, Forum, Taking MIDAS beyond 64 clients
| |
02 May 2020, Stefan Ritt, Forum, Taking MIDAS beyond 64 clients
| |
02 May 2020, Joseph McKenna, Forum, Taking MIDAS beyond 64 clients
| |
02 May 2020, Stefan Ritt, Forum, Taking MIDAS beyond 64 clients
| |
02 May 2020, Konstantin Olchanski, Forum, Taking MIDAS beyond 64 clients
| |
02 May 2020, Konstantin Olchanski, Forum, Taking MIDAS beyond 64 clients
| |
02 May 2020, Konstantin Olchanski, Forum, Taking MIDAS beyond 64 clients
|
|
|
Message ID: 1896
Entry time: 02 May 2020
In reply to: 1895
|
| Author: |
Stefan Ritt |
| Topic: |
Forum |
| Subject: |
Taking MIDAS beyond 64 clients |
|
|
> Perhaps a item for future discussion would be for the odbinit program to be able to 'upgrade' the ODB and enable some backwards
> compatibility.
We had this discussion already a few times. There is an ODB version number (DATABSE_VERSION 3 in midas.h) which is intended for that. If we break teh
binary compatibility, programs should complain "ODB version has changed, please run ...", then odbinit (written by KO) should have a well-defined
procedure to upgrade existing ODBs by re-creating them, but keeping all old contents. This should be tested on a few systems.
Stefan |