| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2722
|
08 Mar 2024 |
Konstantin Olchanski | Info | MIDAS frontend for WIENER L.V. P.S. and VME crates | Our MIDAS frontend for WIENER power supplies
is now available as a standalone git repository.
|
|
|
2724
|
11 Mar 2024 |
Konstantin Olchanski | Bug Report | Autostart program | > It seems that if a frontend is started automatically
by using Program->Auto start then the status
page does not show it as started. This is |
|
|
2726
|
18 Mar 2024 |
Konstantin Olchanski | Bug Report | Midas (manalyzer) + ROOT 6.31/01 - compilation error | > [ 34%] Linking CXX executable manalyzer_test.exe
> /usr/bin/ld: /home/astrocent/workspace/root/root_install/lib/libRIO.so:
undefined
|
|
|
2728
|
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
|
|
|
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
|
|
|
2731
|
01 Apr 2024 |
Konstantin Olchanski | Info | xz-utils bomb out, compression benchmarks | you may have heard the news of a major problem
with the xz-utils project, authors of the
popular "xz" file compression,
|
|
|
2733
|
02 Apr 2024 |
Konstantin Olchanski | Info | Sequencer editor | > Stefan and I have been working on improving
the sequencer editor ...
|
|
|
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.
|
|
|
2735
|
04 Apr 2024 |
Konstantin Olchanski | Info | MIDAS RPC data format | I am not sure I have seen this documented
before. MIDAS RPC data format.
|
|
|
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
|
|
|
2738
|
24 Apr 2024 |
Konstantin Olchanski | Info | MIDAS RPC data format | > 4.5) TID_IN32|RPC_VARARRAY does not work,
corrupts following parameters. MIDAS only
uses TID_ARRAY|RPC_VARARRAY
|
|
|
2739
|
24 Apr 2024 |
Konstantin Olchanski | Info | MIDAS RPC add support for std::string and std::vector<char> | I now fully understand the MIDAS RPC code,
had to add some debugging printfs,
write some test code (odbedit test_rpc), |
|
|
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.
|
|
|
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:
|
|
|
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"
|
|
|
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 |
|
|
2780
|
24 May 2024 |
Konstantin Olchanski | Info | added ubuntu 22 arm64 cross-compilation | Ubuntu 22 has almost everything necessary
to cross-build arm64 MIDAS frontends:
|
|
|
2781
|
29 May 2024 |
Konstantin Olchanski | Info | MIDAS RPC add support for std::string and std::vector<char> | This is moving slowly. I now have RPC caller
side support for std::string and
std::vector<char>. RPC server side is next. |
|
|
2782
|
02 Jun 2024 |
Konstantin Olchanski | Info | MIDAS RPC data format | > MIDAS RPC data format.
> 3) RPC reply
> 3.1) header:
|
|