| ID | 
Date | 
Author  | 
Topic | 
Subject | 
Text | 
  | 
| 
  1622  
 | 
16 Jul 2019 | 
Konstantin Olchanski | Bug Report | a3818 and signals, Frontend killed at stop of run | Message from John M O'Donnell <odonnell@lanl.gov>
 
 
Folks,
 | 
   | 
| 
  1623  
 | 
16 Jul 2019 | 
Konstantin Olchanski | Bug Report | a3818 and signals, Frontend killed at stop of run | > Message from John M O'Donnell <odonnell@lanl.gov>
 
>
 
> the A3818 and MIDAS both used unix alarm | 
   | 
| 
  1624  
 | 
21 Jul 2019 | 
Konstantin Olchanski | Info | error handling is hard | Happy summer to everybody.
 
 
When programming in general, and when programming | 
   | 
| 
  1649  
 | 
08 Aug 2019 | 
Konstantin Olchanski | Info | c++11 for RHEL/SL/CentOS-6 | The default el6 (RHEL/SL/CentOS-6) compiler 
is gcc-4.4.7, it does not support c++11, 
not even a little bit.
 | 
   | 
| 
  1650  
 | 
08 Aug 2019 | 
Konstantin Olchanski | Info | MIDAS will use C++11 | After much discussion, and following the MIDAS 
workshop at TRIUMF, we made the decision 
to use C++11 in MIDAS.
 | 
   | 
| 
  1653  
 | 
08 Aug 2019 | 
Konstantin Olchanski | Suggestion | midas cmake migration | > Each CMakeLists.txt should specify which 
version of CMake it requires. The MIDAS CMakeLists.txt 
requires CMake 3.1 or later. 
 | 
   | 
| 
  1654  
 | 
08 Aug 2019 | 
Konstantin Olchanski | Bug Report | ROOTANA bug? | > indnerlt:rootana lindner$ git diff libMidasInterface/TMidasOnline.cxx
 
> diff --git a/libMidasInterface/TMidasOnline.cxx 
b/libMidasInterface/TMidasOnline.cxx
 | 
   | 
| 
  1656  
 | 
09 Aug 2019 | 
Konstantin Olchanski | Info | Precedence of equipment/common structure | > Today I fixed a long-annoying problem. ...
 
> /Equipment/<name>/Common
 
> In the past, the ODB setting took precedence | 
   | 
| 
  1657  
 | 
09 Aug 2019 | 
Konstantin Olchanski | Bug Report | Fetest History Plot | > Hi, our logger was running.
 
 
 | 
   | 
| 
  1658  
 | 
09 Aug 2019 | 
Konstantin Olchanski | Bug Report | Fetest History Plot | > Hi, our logger was running.
 
 
Please do these simple tests:
 | 
   | 
| 
  1659  
 | 
09 Aug 2019 | 
Konstantin Olchanski | Forum | How to convert C midas frontends to C++ | > How do I solve mismatched declarations in 
the mfe (or other places in the midas code)?
 
 | 
   | 
| 
  1663  
 | 
14 Aug 2019 | 
Konstantin Olchanski | Bug Fix | incorrect recursion in ss_suspend() via the user event handler | The ROOTANA midas analyzer uncovered a problem 
with recursive use of ss_suspend().
 
 | 
   | 
| 
  1664  
 | 
14 Aug 2019 | 
Konstantin Olchanski | Bug Report | ROOTANA bug? | > -  ss_suspend_set_dispatch_ipc(NULL);
 
> +  //  ss_suspend_set_dispatch_ipc(NULL);
 
> 
 | 
   | 
| 
  1685  
 | 
16 Sep 2019 | 
Konstantin Olchanski | Forum | Open a hotlink to a single element in an ODB array | > Is it possible to open a hotlink to a single 
element in an ODB array?
 
 | 
   | 
| 
  1686  
 | 
16 Sep 2019 | 
Konstantin Olchanski | Bug Report | https redirect and ODB access | > I'm not sure if these issues are related 
or not, but I'm getting an error
 
> message when I want to access the root | 
   | 
| 
  1687  
 | 
16 Sep 2019 | 
Konstantin Olchanski | Info | New history plot facility | > I see currently quite often is the error 
hs_read_arraybuffer (see the 
 
attachement).
 | 
   | 
| 
  1688  
 | 
16 Sep 2019 | 
Konstantin Olchanski | Info | New history plot facility | > During my visit at TRIUMF we rewrote the 
history plotting functionality of midas.
 
 | 
   | 
| 
  1689  
 | 
16 Sep 2019 | 
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | > My first question would be why are you using 
several font-ends at all? That makes things 
more 
 | 
   | 
| 
  1691  
 | 
16 Sep 2019 | 
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | > it's probably better to run a multi-threaded 
setup, than individual frontends.
 
 | 
   | 
| 
  1692  
 | 
16 Sep 2019 | 
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | > thanks for your reply. I can confirm that 
your suggested workaround does indeed
 
> make the problem dissapear.
 | 
   |