ID |
Date |
Author |
Topic |
Subject |
Text |
|
2911
|
01 Dec 2024 |
Pavel Murat | Bug Report | EQ_PERIODIC-only equipment ? | > There is no requirement that you pair an
EQ_PERIODIC with an EQ_TRIGGER. Take for
exmaple
|
|
2926
|
29 Dec 2024 |
Pavel Murat | Forum | time ordering of run transition calls to TMFeEquipment things | Dear MIDAS experts,
I have a question about "tmfe approach" to |
|
2928
|
02 Jan 2025 |
Pavel Murat | Forum | time ordering of run transition calls to TMFeEquipment things | Hi K.O., your clarification is much appreciated!
"
|
|
80
|
09 Dec 2003 |
Paul Knowles | | db_close_record non-local/non-return |
Hi All,
|
|
75
|
18 Dec 2003 |
Paul Knowles | | Poll about default indent style | Hi Stefan,
> once and forever, I am considering using |
|
1645
|
07 Aug 2019 |
Paolo Baesso | Bug Report | ROOTANA bug? | Hi,
I posted on the ROOTANA elog but there seems |
|
2775
|
21 May 2024 |
Nikolay | Bug Report | experiment from midas/examples | There are 2 bugs in midas/examples/experiment:
1) In fronted bank named "PRDC" is created |
|
2500
|
02 May 2023 |
Niklaus Berger | Forum | Problem with running midas odbxx frontends on a remote machine using the -h option | Thanks for all the helpful hints. When finally
managing to evade all timeouts and attach
the debugger in just the right moment, we |
|
2501
|
02 May 2023 |
Niklaus Berger | Forum | Problem with running midas odbxx frontends on a remote machine using the -h option | And now we also fixed the client segfault,
odb.cxx L8992 also needs to know about the
header:
|
|
1634
|
26 Jul 2019 |
Nik Berger | Bug Report | History/Endianness | Hi,
I have a bank of floats with slow control
values that I store to the history and
|
|
1719
|
06 Oct 2019 |
Nik Berger | Bug Report | History data size mismatch | Logging a list of variables to the history
via links in the history ODB subtree,
we get messages as follows at every run start:
|
|
1722
|
10 Oct 2019 |
Nik Berger | Bug Report | History data size mismatch | >I wonder why do you this via ODB links. The
"standard" way of writing to the history
should be to create events for an equipment |
|
1665
|
28 Aug 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hello experts,
I have been writing a SC frontend for a powersupply. |
|
1667
|
28 Aug 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Stefan,
thanks for you quick reply.
|
|
Draft
|
29 Aug 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi LCP,
thanks for the suggestion and link. Unfortunatly |
|
Draft
|
29 Aug 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Ben,
thanks for your reply. I can confirm that |
|
1672
|
01 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Ben,
thanks for your reply. I can confirm that |
|
1693
|
16 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Konstantin,
thanks for your reply.
|
|
Draft
|
18 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | > > [local:e666:S]History>ls -l /History/Events
> > Key name Type
#Val Size Last Opn Mode Value |
|
1699
|
18 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Konstantin,
> > [local:e666:S]History>ls -l /History/Events
|
|