| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2709
|
13 Feb 2024 |
Konstantin Olchanski | Forum | forbidden equipment names ? | > equipment names are 'mu2edaq09:DTC0' and
'mu2edaq09:DTC1'
|
|
|
2713
|
15 Feb 2024 |
Konstantin Olchanski | Forum | number of entries in a given ODB subdirectory ? | > > > For ODB keys of type TID_KEY, the value
num_values IS the number of subkeys.
> >
|
|
|
2714
|
15 Feb 2024 |
Konstantin Olchanski | Forum | number of entries in a given ODB subdirectory ? | > > You are right, num_values is always 1
for TID_KEYS. The number of subkeys is stored
in
|
|
|
2715
|
15 Feb 2024 |
Stefan Ritt | Forum | number of entries in a given ODB subdirectory ? | > Hmm... is there any use case where you want
to know the number of directory entries,
but you will not iterate
|
|
|
2716
|
18 Feb 2024 |
Frederik Wauters | Forum | dump history FILE files | > $ cat mhf_1697445335_20231016_run_transitions.dat
> event name: [Run transitions], time [1697445335]
> tag: tag: /DWORD 1 4 /timestamp
|
|
|
2717
|
19 Feb 2024 |
Pavel Murat | Forum | number of entries in a given ODB subdirectory ? | > > Hmm... is there any use case where you
want to know the number of directory entries,
but you will not iterate
|
|
|
2718
|
26 Feb 2024 |
Maia Henriksson-Ward | Forum | mserver ERR message saying data area 100% full, though it is free | > Hi,
>
> I have just installed Midas and set-up |
|
|
2719
|
27 Feb 2024 |
Pavel Murat | Forum | displaying integers in hex format ? | Dear MIDAS Experts,
I'm having an odd problem when trying to |
|
|
2720
|
27 Feb 2024 |
Stefan Ritt | Forum | displaying integers in hex format ? | Thanks for reporting that bug. I fixed it
and committed the change to the develop branch.
|
|
|
2721
|
27 Feb 2024 |
Pavel Murat | Forum | displaying integers in hex format ? | Hi Stefan (and Ben),
thanks for reacting so promptly - your commits |
|
|
2740
|
29 Apr 2024 |
Musaab Al-Bakry | Forum | Midas Sequencer with less than 1 second wait | Hello there,
I am working on a task that involves some |
|
|
2741
|
29 Apr 2024 |
Stefan Ritt | Forum | Midas Sequencer with less than 1 second wait | I guess the simplest way to do that without
breaking with existing code is to change
the
|
|
|
2743
|
30 Apr 2024 |
Scott Oser | Forum | Midas Sequencer with less than 1 second wait | > I guess the simplest way to do that without
breaking with existing code is to change
the
|
|
|
2744
|
30 Apr 2024 |
Stefan Ritt | Forum | Midas Sequencer with less than 1 second wait | > This would work fine in principle, but isn't
implemented in the current MIDAS sequencer
as we understand it. (We tried!) Is your |
|
|
2745
|
30 Apr 2024 |
Scott Oser | Forum | Midas Sequencer with less than 1 second wait | > > This would work fine in principle, but
isn't implemented in the current MIDAS sequencer
as we understand it. (We tried!) Is your |
|
|
2746
|
30 Apr 2024 |
Stefan Ritt | Forum | Midas Sequencer with less than 1 second wait | While I will do it, i'm not sure if this is
what you want. If I understand correctly,
some process gets triggered and then writes |
|
|
2747
|
30 Apr 2024 |
Scott Oser | Forum | Midas Sequencer with less than 1 second wait | > While I will do it, i'm not sure if this
is what you want. If I understand correctly,
some process gets triggered and then writes |
|
|
2748
|
02 May 2024 |
Stefan Ritt | Forum | Midas Sequencer with less than 1 second wait | Ok, I implemented the float second wait function.
Internally it works in ms, so the maximum
resolution is 0.001 s.
|
|
|
2749
|
02 May 2024 |
Scott Oser | Forum | Midas Sequencer with less than 1 second wait | > Ok, I implemented the float second wait
function. Internally it works in ms, so the
maximum resolution is 0.001 s.
|
|
|
2759
|
05 May 2024 |
Musaab Al-Bakry | Forum | Midas Sequencer with less than 1 second wait | > > Ok, I implemented the float second wait
function. Internally it works in ms, so the
maximum resolution is 0.001 s.
|
|