| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2681
|
18 Jan 2024 |
Stefan Ritt | Forum | mhttpd eqtable | I fixed both in the current version, so please
give it a try.
|
|
|
2683
|
22 Jan 2024 |
Stefan Ritt | Bug Report | Warnings about ODB keys that haven't been touched for 10+ years | > What's the best way to make these messages
go away?
> - Change the logic in db_validate_and_repair_key_wlocked() |
|
|
2694
|
28 Jan 2024 |
Stefan Ritt | Forum | number of entries in a given ODB subdirectory ? | I guess you won't change your FPGA configuration
just when you start a run, so I don't consider
the race
|
|
|
2695
|
28 Jan 2024 |
Stefan Ritt | Bug Report | Warnings about ODB keys that haven't been touched for 10+ years | > Please run "git blame" to find out who added
that check.
|
|
|
2705
|
08 Feb 2024 |
Stefan Ritt | Forum | number of entries in a given ODB subdirectory ? | > Konstantin is right: KEY.num_values is not
the same as the number of subkeys (should
it be ?)
|
|
|
2708
|
13 Feb 2024 |
Stefan Ritt | 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.
>
|
|
|
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
|
|
|
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.
|
|
|
2737
|
15 Apr 2024 |
Stefan Ritt | Bug Report | open MIDAS RPC ports | One thing coming to my mind is the interface
binding. If you have a midas host with two
networks
|
|
|
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
|
|
|
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 |
|
|
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 |
|
|
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.
|
|
|
2751
|
03 May 2024 |
Stefan Ritt | Bug Report | Params not initialized when starting sequencer | Ok, here is the complete code to reproduce
the problem. Load parameter_test.msl which
includes functions.msl. From the screenshot |
|
|
2754
|
03 May 2024 |
Stefan Ritt | Suggestion | Possible addition to IF Statements | The tinyexpr library I use to evaluate expressions
does not support boolean operations. I would
have to switch to the newer
|
|
|
2756
|
03 May 2024 |
Stefan Ritt | Bug Report | Params not initialized when starting sequencer | Ahh, that rings a bell:
1) JS opens start dialog box
|
|
|
2758
|
03 May 2024 |
Stefan Ritt | Bug Report | Params not initialized when starting sequencer | Seems to me like the problem happens less
frequently, but I still see it (1 out of
5 or so). The fact that /Sequencer/Params/Value |
|
|
2760
|
06 May 2024 |
Stefan Ritt | Forum | Midas Sequencer with less than 1 second wait | Indeed there was a sleep(100ms) in the sequencer
in each loop. I reduced it now to 10ms. I
need at least 10ms since otherwise
|
|
|
2761
|
06 May 2024 |
Stefan Ritt | Forum | Midas Sequencer with less than 1 second wait | Actually I realized that a 1ms wait still
works, so I reduced it to that.
|
|
|
2768
|
17 May 2024 |
Stefan Ritt | Bug Report | midas alarm borked condition evaluation | This is a common problem I also encountered
in the past. You get a low-level ODB access
error (could also be a read of a non-existing |
|