| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2777
|
21 May 2024 |
Zaher Salman | Bug Report | Params not initialized when starting sequencer | I traced the problem to a mjsonrpc_db_ls call
where I read /Sequencer/Param... . It seems
that this sometimes returns a status 312 |
|
|
2776
|
21 May 2024 |
Thomas Senger | Bug Report | Params not initialized when starting sequencer | Hi all,
On develop, the issue seems to be still there
and is not fixed.
|
|
|
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 |
|
|
2774
|
18 May 2024 |
Stefan Ritt | Bug Report | odbedit load into the wrong place | Taht's strange. I always was under the impression
that .odb files are loaded relatively to
the current location in
|
|
|
2773
|
18 May 2024 |
Stefan Ritt | Bug Report | midas alarm borked condition evaluation | For everybody using EPICS: There is now a
new system called MSetPoint (Midas Set Point)
to control whole beamlines via EPICS.
|
|
|
Draft
|
18 May 2024 |
Stefan Ritt | Bug Report | midas alarm borked condition evaluation | For everybody using EPICS: There is now a
new system called MSetPoint (Midas Set Point)
to control whole beamlines via EPICS.
|
|
|
2771
|
17 May 2024 |
Konstantin Olchanski | Bug Report | midas alarm borked condition evaluation | >
> And I think I know what caused the original
problem in IRIS experiment, I think the list |
|
|
2770
|
17 May 2024 |
Konstantin Olchanski | Bug Report | odbedit load into the wrong place | Trying to restore IRIS ODB was a nasty surprise,
old save files are in .odb format and odbedit
"load xxx.odb"
|
|
|
2769
|
17 May 2024 |
Konstantin Olchanski | 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 |
|
|
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 |
|
|
2767
|
16 May 2024 |
Konstantin Olchanski | Bug Report | midas alarm borked condition evaluation | I am updating the TRIUMF IRIS experiment to
the latest version of MIDAS. I see following
error messages in midas.log:
|
|
|
2766
|
14 May 2024 |
Konstantin Olchanski | Info | ROOT v6.30.6 requires libtbb-dev | root_v6.30.06.Linux-ubuntu22.04-x86_64-gcc11.4
the libtbb-dev package.
|
|
|
2765
|
13 May 2024 |
Luigi Vigani | Bug Report | Params not initialized when starting sequencer | [quote="Zaher Salman"]I think that I finally
managed to fix the problem. The default values
of the parameters are now written first in |
|
|
Draft
|
13 May 2024 |
Luigi Vigani | Bug Report | Params not initialized when starting sequencer | [quote="Zaher Salman"]I think
that I finally managed to fix the problem.
The default values of the parameters are |
|
|
2763
|
10 May 2024 |
Zaher Salman | Bug Report | Params not initialized when starting sequencer | I think that I finally managed to fix the
problem. The default values of the parameters
are now written first in one go, then the |
|
|
2762
|
07 May 2024 |
Musaab Al-Bakry | Forum | Midas Sequencer with less than 1 second wait | > Actually I realized that a 1ms wait still
works, so I reduced it to that.
>
|
|
|
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.
|
|
|
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
|
|
|
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.
|
|
|
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 |
|