 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 |
|
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 |
|
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:
>
> WAIT ODBvalue, /Equipment/HV/Variables/Measured[3], <, 100, timeout, 60
|
|
29 May 2026, Stefan Ritt, Info, ODBvalue timeout
|
> >
> > How can the MSL code figure out if the wait succeeded or timed out?
> >
|
|
29 May 2026, Stefan Ritt, Info, ODBvalue timeout
|
> > > >
> > > > How can the MSL code figure out if the wait succeeded or timed out?
> > > >
|
 19 Nov 2025, Stefan Mathis, Forum, Control external process from inside MIDAS
|
Dear all,
I want to control (start / stop / monitor its stdout and stderr) an external process (systemd / EPICS IOC shell script) from within MIDAS.
|
|
20 Nov 2025, Stefan Mathis, Forum, Control external process from inside MIDAS
|
Thanks a lot,
Nick. Regarding the messages: Zaher showed me that it is possible to simply place a custom log file generated by the systemd next to midas.log - then it |
|
20 Nov 2025, Stefan Mathis, Forum, Control external process from inside MIDAS
|
Hi,
unfortunately I don't have a documentation link to the feature, I just know that it works on my machine ;-) The general idea is that you place a custom |
|
13 Oct 2020, Soichiro Kuribayashi, Info, About remote control of front end part of MIDAS on chip
|
Hello!
My name is Soichiro Kuribayashi and I am a Ph.D. student at Kyoto University.
|
|
13 Oct 2020, Soichiro Kuribayashi, Info, About remote control of front end part of MIDAS on chip
|
Dear Konstantin,
Thank you very much for your reply and detailed information.
|
|
21 Oct 2020, Soichiro Kuribayashi, Info, About remote control of front end part of MIDAS on chip
|
Dear Stefan,
Thank you very much for your help.
|
|
27 Jul 2006, Shawn Bishop, Bug Report, MIDAS revision 3184 bombs on FC5
|
Hi All,
I just did a fresh download of midas (revision 3184) onto a newly setup FC5 box. Compilation bombs. Printout of compiler output as follows:
|
|
28 Jul 2006, Shawn Bishop, Bug Report, Latest FC5 Compilation attempt
|
Perhaps some progess? Problem for compilation on FC5 now seems to be in odb.c for revision 3189. Compilation output as follows: --Shawn
[COLOR=red][midas@daruma ~/midas]$ make
|
|
02 Aug 2006, Shawn Bishop, Bug Report, MIDAS packaged examples: compilation bug?
|
Hi All,
I switched to Sci. Linux 4.3, from FC5, and was able to get the guts of MIDAS to compile without any difficulties. Now, I have followed the "Quick Start" |
|
03 Aug 2006, Shawn Bishop, Bug Report, MIDAS packaged examples: compilation bug?
|
[quote="Stefan Ritt"][quote="Shawn Bishop"]Anyone have an idea what's going on here?[/quote]
The Makefile contained the outdated target [B]fal[/B], which is a combined frontend/analyzer/logger. You don't need that, so I removed it from the makefile. |
|
03 Aug 2006, Shawn Bishop, Bug Report, MIDAS packaged examples: compilation bug?
|
[quote="Stefan Ritt"][quote="Shawn Bishop"]Anyone have an idea what's going on here?[/quote]
The Makefile contained the outdated target [B]fal[/B], which is a combined frontend/analyzer/logger. You don't need that, so I removed it from the makefile. |