| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
3230
|
29 May 2026 |
Stefan Ritt | Info | ODBvalue timeout | > > > >
> > > > How can the MSL code figure out if
the wait succeeded or timed out?
|
|
|
3229
|
29 May 2026 |
Zaher Salman | Info | ODBvalue timeout | > > >
> > > How can the MSL code figure out if
the wait succeeded or timed out?
|
|
|
3228
|
29 May 2026 |
Stefan Ritt | Info | ODBvalue timeout | > >
> > How can the MSL code figure out if the
wait succeeded or timed out?
|
|
|
3227
|
29 May 2026 |
Zaher Salman | Info | ODBvalue timeout | >
> How can the MSL code figure out if the
wait succeeded or timed out?
|
|
|
3226
|
29 May 2026 |
Stefan Ritt | Info | ODBvalue timeout | > Dear all, I implemented an optional timeout
for the wait ODBvalue command. The way it
works is similar to the standard wait command:
|
|
|
3225
|
29 May 2026 |
Zaher Salman | Info | ODBvalue timeout | Dear all, I implemented an optional timeout
for the wait ODBvalue command. The way it
works is similar to the standard wait command:
|
|
|
3224
|
21 May 2026 |
Konstantin Olchanski | Bug Report | incompatible ODB XML dumps | While testing manalyzer, I found that it dies
from an exception on odbxx, error message
is "/home/olchansk/packages/midas/include/odbxx.h:1231: |
|
|
3223
|
21 May 2026 |
Konstantin Olchanski | Info | manalyzer --save-odb | Due my oversight, the code for extracting
ODB dumps from MIDAS data files from rootana/old_analyzer/event_dump.cxx
was missing in
|
|
|
3222
|
06 May 2026 |
Ben Smith | Bug Fix | numpy version compatibility | > There seems to be a version dependency with
the numpy.bool
|
|
|
3221
|
06 May 2026 |
Jonas A. Krieger | Suggestion | numpy version compatibility | There seems to be a version dependency with
the numpy.bool , e.g. used here
https://bitbucket.org/tmidas/midas/src/c6ef4aff5e7e652df79160141e570bed5f4d6a3b/python/midas/sequencer.py?at=develop#sequencer.py-1714 |
|
|
3220
|
27 Apr 2026 |
Pavel Murat | Bug Report | increasing the max number of hot links in ODB | > > Indeed, updating MIDAS clients on each
and every RPI etc in a running experiment
may be a real challenge.
|
|
|
3219
|
27 Apr 2026 |
Pavel Murat | Bug Report | increasing the max number of hot links in ODB | > > I wonder why one needs more than 256 hotlinks
at all.
>
|
|
|
3218
|
27 Apr 2026 |
Pavel Murat | Bug Report | increasing the max number of hot links in ODB | > I wonder why one needs more than 256 hotlinks
at all. Please note that with the odbxx "watch"
API, you can hotline a whole subdirectory, |
|
|
3217
|
27 Apr 2026 |
Nick Hastings | Bug Report | increasing the max number of hot links in ODB | For the record, the ND280 (T2K near detector)
MIDAS GSC was initially set up
with MAX_OPEN_RECORDS = 2560 and MAX_CLIENTS |
|
|
3216
|
27 Apr 2026 |
Konstantin Olchanski | Bug Report | increasing the max number of hot links in ODB | > I wonder why one needs more than 256 hotlinks
at all.
|
|
|
3215
|
27 Apr 2026 |
Konstantin Olchanski | Bug Report | increasing the max number of hot links in ODB | > Indeed, updating MIDAS clients on each and
every RPI etc in a running experiment may
be a real challenge.
|
|
|
3214
|
26 Apr 2026 |
Stefan Ritt | Bug Report | increasing the max number of hot links in ODB | I wonder why one needs more than 256 hotlinks
at all. Please note that with the odbxx "watch"
API, you can hotline a whole subdirectory, |
|
|
3213
|
25 Apr 2026 |
Pavel Murat | Bug Report | increasing the max number of hot links in ODB | I see - thank you for the explanation!
Indeed, updating MIDAS clients on each and |
|
|
3212
|
24 Apr 2026 |
Konstantin Olchanski | Bug Report | increasing the max number of hot links in ODB | > when I attempted to increase the max number
of hotlinks in ODB , defined as
> #define MAX_OPEN_RECORDS 256 |
|
|
Draft
|
23 Apr 2026 |
Nick Hastings | Bug Report | increasing the max number of hot links in ODB | > Dear MIDAS experts,
>
> when I attempted to increase the max number |
|