| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
256
|
18 May 2006 |
Konstantin Olchanski | Bug Fix | removed a few "//" comments to fix compilation on VxWorks | Our VxWorks C compiler (gcc-2.8-something)
does not like the "//" comments. Luckily,
on VxWorks, we
|
|
|
1435
|
10 Jan 2019 |
Konstantin Olchanski | Info | removal of cm_watchdog() | cm_watchdog() has been removed from the latest
midas sources. The watchdog functions performed
by cm_watchdog() were
|
|
|
1439
|
21 Jan 2019 |
Konstantin Olchanski | Info | removal of cm_watchdog() | > cm_watchdog() has been removed from the
latest midas sources
> Removal of cm_watchdog() solves many problems |
|
|
1442
|
24 Jan 2019 |
Konstantin Olchanski | Info | removal of cm_watchdog() | > > cm_watchdog() has been removed from the
latest midas sources
> > Removal of cm_watchdog() solves many |
|
|
1159
|
05 Feb 2016 |
Thomas Lindner | Suggestion | reducing sleep time in mhttpd main loop (for sequencer) | There were some complaints that the MIDAS
sequencer was slow. Specifically, the
complaint was that even lines in the sequence |
|
|
1160
|
05 Feb 2016 |
Thomas Lindner | Suggestion | reducing sleep time in mhttpd main loop (for sequencer) | > There were some complaints that the MIDAS
sequencer was slow. Specifically, the
> complaint was that even lines in the sequence |
|
|
1161
|
06 Feb 2016 |
Stefan Ritt | Suggestion | reducing sleep time in mhttpd main loop (for sequencer) | > There were some complaints that the MIDAS
sequencer was slow. Specifically, the
> complaint was that even lines in the sequence |
|
|
1162
|
15 Feb 2016 |
Thomas Lindner | Suggestion | reducing sleep time in mhttpd main loop (for sequencer) |
> > I checked how much extra CPU was used
if the sleep was reduced from 100ms to
|
|
|
1163
|
15 Feb 2016 |
Stefan Ritt | Suggestion | reducing sleep time in mhttpd main loop (for sequencer) | > Hmm, yeah, I'm not sure about how to handle
reducing the wait time to zero after ODB
set commands.
|
|
|
1701
|
23 Sep 2019 |
Frederik Wauters | Suggestion | recover daq and hardware safety. | We have encountered a safety issue with
our HPGe HV and it's midas frontend.
Turning off or changing HV unknowingly has |
|
|
1708
|
27 Sep 2019 |
Konstantin Olchanski | Suggestion | recover daq and hardware safety. | > We have encountered a safety issue with
our HPGe HV and it's midas frontend.
|
|
|
1712
|
28 Sep 2019 |
Frederik Wauters | Suggestion | recover daq and hardware safety. | Dear Konstantin,
So let me retract the term "safety issue" |
|
|
1715
|
29 Sep 2019 |
Konstantin Olchanski | Suggestion | recover daq and hardware safety. | >
> The issue occurs when e.g. one channel
can not be turned on and ramp for some temp/specific |
|
|
1726
|
15 Oct 2019 |
Stefan Ritt | Suggestion | recover daq and hardware safety. | There is a not-so-well-known function in the
ODB to write protect some keys. You can do
|
|
|
2441
|
22 Oct 2022 |
Lars Martin | Suggestion | read_only odbxx? | I really like the concept of the odbxx interface.
I think it would be a nice feature if one
could have a read_only connection, e.g. by |
|
|
2443
|
24 Oct 2022 |
Stefan Ritt | Suggestion | read_only odbxx? | > I really like the concept of the odbxx interface.
> I think it would be a nice feature if one
could have a read_only connection, e.g. by |
|
|
2444
|
26 Oct 2022 |
Lars Martin | Suggestion | read_only odbxx? | > Having a "const midas::odb" probably does
not work (at least I would not know how to
implement that).
|
|
|
2445
|
29 Oct 2022 |
Stefan Ritt | Suggestion | read_only odbxx? | Ok, I implemented and committed that. Just
call
|
|
|
737
|
26 Dec 2010 |
Konstantin Olchanski | Bug Report | race condition and deadlock between ODB lock and SYSMSG lock in cm_msg() | >
> The only remaining problem when running
my script is some kind of deadlock between |
|
|
2493
|
01 May 2023 |
Giovanni Mazzitelli | Bug Report | python issue with mathplot lib vs odb query | Ciao,
we have a very strange issue with python
lib with client.odb_get("/") function
|
|