| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
Draft
|
05 Sep 2024 |
Jack Carlton | Forum | Python frontend rate limitations? |
Thank you, this was very helpful.
|
|
|
2828
|
05 Sep 2024 |
Stefan Ritt | Forum | Python frontend rate limitations? | > First the general advice: if you reduce
the "period" of your equipment, then your
function will get called more frequently. |
|
|
2829
|
06 Sep 2024 |
Jack Carlton | Forum | Python frontend rate limitations? | Thanks for the responses, they were very helpful.
>First the general advice: if you reduce |
|
|
2831
|
11 Sep 2024 |
Konstantin Olchanski | Forum | Python frontend rate limitations? | > I'm trying to get a sense of the rate limitations
of a python frontend.
|
|
|
2832
|
11 Sep 2024 |
Konstantin Olchanski | Forum | Python frontend rate limitations? | >
> poll(INT count) {
> for (i=0 ; i<count ; i++)
|
|
|
2833
|
11 Sep 2024 |
Konstantin Olchanski | Forum | Python frontend rate limitations? | > > I'm trying to get a sense of the rate
limitations of a python frontend.
|
|
|
2838
|
11 Sep 2024 |
Konstantin Olchanski | Forum | "Safe" abort of sequencer scripts | > We often use the MIDAS sequencer to temporarily
control detector settings, such as:
>
|
|
|
2860
|
27 Sep 2024 |
Ben Smith | Forum | Python frontend rate limitations? | > in your case the limitation is likely that
you're sending 1.25MB per event and we have
a lot of data marshalling to do between the |
|
|
2885
|
05 Nov 2024 |
Jack Carlton | Forum | How to properly write a client listens for events on a given buffer? | If there's some template for writing a client
to access event data, that would be
very useful (and you can probably just ignore |
|
|
2886
|
05 Nov 2024 |
Maia Henriksson-Ward | Forum | How to properly write a client listens for events on a given buffer? | > If there's some template for writing a client
to access event data, that would be
> very useful (and you can probably just |
|
|
2914
|
02 Dec 2024 |
Stefan Ritt | Forum | "Safe" abort of sequencer scripts | The atexit() function has been implemented
in the current develop branch of midas, see
|
|
|
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 |
|
|
2927
|
01 Jan 2025 |
Konstantin Olchanski | Forum | time ordering of run transition calls to TMFeEquipment things | > I have a question about "tmfe approach"
to implementing MIDAS frontends. If I read
the code correctly,
|
|
|
2928
|
02 Jan 2025 |
Pavel Murat | Forum | time ordering of run transition calls to TMFeEquipment things | Hi K.O., your clarification is much appreciated!
"
|
|
|
2929
|
05 Jan 2025 |
Stefan Ritt | Forum | time ordering of run transition calls to TMFeEquipment things | Hi Pavel,
have you looked into
|
|
|
156
|
13 Oct 2004 |
Konstantin Olchanski | Bug Report | db_paste: found string exceeding MAX_STRING_LENGTH | I am updating TWIST to the latest MIDAS and
when I load a saved .odb file, I get
these messages. Their text ought to say where |
|
|
157
|
13 Oct 2004 |
Stefan Ritt | Bug Report | db_paste: found string exceeding MAX_STRING_LENGTH | Can you attach
/twist/data_onl/current/run17548.odb
|
|
|
158
|
13 Oct 2004 |
Konstantin Olchanski | Bug Report | silly odbedit "rename Display xxx/yyy" | odbedit command "rename Display xxx/yyy" creates
a key named "xxx/yyy" (yes,
with a slash in the name) and this key cannot |
|
|
159
|
13 Oct 2004 |
Stefan Ritt | Bug Report | silly odbedit "rename Display xxx/yyy" | > odbedit command "rename Display xxx/yyy"
creates a key named "xxx/yyy" (yes,
> with a slash in the name) and this key |
|
|
163
|
13 Oct 2004 |
Konstantin Olchanski | Bug Report | TWIST upgrade bombed... | The upgrade of TWIST to the latest midas has
bombed- we see mevb and mlogger
crashes during shared memory data buffer |
|