| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2729
|
19 Mar 2024 |
Konstantin Olchanski | Bug Report | Midas (manalyzer) + ROOT 6.31/01 - compilation error | > ok, thank you for your information. I cannot
reproduce this problem, I use vanilla Ubuntu
|
|
|
2730
|
28 Mar 2024 |
Grzegorz Nieradka | Bug Report | Midas (manalyzer) + ROOT 6.31/01 - compilation error |
I found solution for my trouble. With MIDAS
and ROOT everything is OK,
|
|
|
2734
|
02 Apr 2024 |
Konstantin Olchanski | Bug Report | Midas (manalyzer) + ROOT 6.31/01 - compilation error | > I found solution for my trouble. With MIDAS
and ROOT everything is OK,
> the trobule was with my Ubuntu enviroment.
|
|
|
2736
|
15 Apr 2024 |
Konstantin Olchanski | Bug Report | open MIDAS RPC ports | we had a bit of trouble with open network
ports recently and I now think security of
MIDAS RPC
|
|
|
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
|
|
|
2742
|
30 Apr 2024 |
Luigi Vigani | Bug Report | Params not initialized when starting sequencer | Good afternoon,
After updating Midas to the latest develop |
|
|
2750
|
03 May 2024 |
Zaher Salman | Bug Report | Params not initialized when starting sequencer | Could you please export and send me the /Sequencer
ODB tree (or just /Sequencer/Param and /Sequencer/Variables)
in both cases while the sequence is running. |
|
|
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 |
|
|
2752
|
03 May 2024 |
Luigi Vigani | Bug Report | Params not initialized when starting sequencer | It is pretty much the same as Stefan, I attach
here the screenshots. Also in my case it
works sometimes, and sometimes partially |
|
|
2755
|
03 May 2024 |
Zaher Salman | Bug Report | Params not initialized when starting sequencer | I have been able to reproduce the problem
only once. From what I see, it seems that
the Variables ODB tree is not initialized |
|
|
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
|
|
|
2757
|
03 May 2024 |
Zaher Salman | Bug Report | Params not initialized when starting sequencer | Thanks for the hint Stefan. I pushed a possible
fix but I cannot test it since I cannot reproduce
the issue.
|
|
|
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 |
|
|
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 |
|
|
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 |
|
|
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 |
|
|
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:
|
|
|
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 |
|
|
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 |
|
|
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"
|
|