 14 Jan 2026, Derek Fujimoto, Bug Report, DEBUG messages not showing and related
|
I have an application where I want to (optionally) send my own debugging messages to the midas.log file, but am having some problems with this:
* Messages with type MT_DEBUG don't show up in midas.log or on the messages page (calling cm_msg from python)
|
 14 Jan 2026, Stefan Ritt, Bug Report, DEBUG messages not showing and related
|
MT_DEBUG messages are there for debugging, not logging. They only go into the SYSMSG buffer and NOT to the log file. If you want anything logged, just use
MT_INFO.
|
|
14 Jan 2026, Derek Fujimoto, Bug Report, DEBUG messages not showing and related
|
Ok thanks for the quick and clear response!
Derek
|
|
05 Feb 2026, Konstantin Olchanski, Bug Report, omnibus bugs from running DarkLight
|
We finished running the DarkLight experiment and I am reporting accumulated bugs that we have run into.
1) history plots on 12 hrs, 24 hrs tend to hang with "page not responsive". most plots have 16-20 variables,
|
06 Feb 2026, Stefan Ritt, Bug Report, omnibus bugs from running DarkLight 
|
Thanks for the detailed report. Let me reply one-by-one.
> 1) history plots on 12 hrs, 24 hrs tend to hang with "page not responsive". most plots have 16-20 variables,
|
|
06 Feb 2026, Stefan Ritt, Bug Report, omnibus bugs from running DarkLight
|
> 3) ODB editor clicking on hex number versus decimal number no longer allows editing in hex, Stefan implemented
> this useful feature and it worked for a while, but now seems broken.
|
|
06 Feb 2026, Stefan Ritt, Bug Report, omnibus bugs from running DarkLight
|
> 4) ODB editor "right click" to "delete" or "rename" key does not work, the right-click menu disappears
> immediately before I can use it (dl-server-2), click on item (it is now blue), right-click menu disappears
> before I can use it (daq17). it looks like a timing or race condition.
|
|
06 Feb 2026, Stefan Ritt, Bug Report, omnibus bugs from running DarkLight
|
> 5) ODB editor "create link" link target name is limited to 32 bytes, links cannot be created (dl-server-2), ok
> on daq17 with current MIDAS.
|
|
12 Feb 2026, Stefan Ritt, Bug Report, omnibus bugs from running DarkLight
|
Now I had a similar case that the browser froze when showing 24h of data. Tuned out that 80k points are a bit much. I changed the code so that it starts
binning when showing 8h or more. This is not a perfect solution. The code should check at which interval data is written, then
automatically start binning when approaching 4000 points or more. That would however require more complicated code, so I leave it as it is right now. Feedback |
|
23 Apr 2026, Pavel Murat, Bug Report, increasing the max number of hot links in ODB
|
Dear MIDAS experts,
when I attempted to increase the max number of hotlinks in ODB , defined as
|
|
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 of hotlinks in ODB , defined as
|
|
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 /**< number of open DB records */
> assert(sizeof(DATABASE_CLIENT) == 2112);
|
|
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 every RPI etc in a running experiment may be a real challenge.
|
|
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, and get notified
if ANY of the
underlying values or subdirectories change. In principle, one could have one hotlink to "/" and see all changes in the ODB (although that does not make |
|
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.
actually, only local clients must be rebuilt, remote clients connecting to the mserver do not care about ODB
|
|
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.
I confirm that ALPHA is running with MAX_OPEN_RECORDS changed from 256 to 2048,
|
|
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 = 128.
|
|
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, and get notified
if ANY of the
> underlying values or subdirectories change. In principle, one could have one hotlink to "/" and see all changes in the ODB (although that does not make |
|
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.
>
> I confirm that ALPHA is running with MAX_OPEN_RECORDS changed from 256 to 2048,
|
|
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.
>
> actually, only local clients must be rebuilt, remote clients connecting to the mserver do not care about ODB
|