ID |
Date |
Author |
Topic |
Subject |
Text |
|
41
|
15 Sep 2004 |
Konstantin Olchanski | | midas odb locking |
After some discussion with Stefan-
|
|
42
|
16 Sep 2004 |
Stefan Ritt | | midas odb locking | > I will add a timeout of 10 minutes, then
shutdown the ODB client with an error message.
|
|
175
|
24 Nov 2004 |
chris pearson | Info | midas on 64bit opteron | Midas, version 1.9.5 of 7th October, was
installed, with a few changes, on a
64 bit opteron computer, running linux. |
|
1758
|
12 Jan 2020 |
Konstantin Olchanski | Info | midas on centos-8 status | I now have a centos-8 computer and I tried
midas on it:
|
|
2420
|
08 Aug 2022 |
Konstantin Olchanski | Info | midas on ubuntu LTS 22.04 | reporting that as of commit 78f707c0686d22f8329c7a1f1c46d7dccf35ceff,
midas builds
without errors or warnings on Ubuntu LTS |
|
919
|
22 Oct 2013 |
Konstantin Olchanski | Info | midas programs "auto start", etc | MIDAS "programs" settings include: /programs/xxx/"auto
start", "auto restart" and "auto stop". What
do
|
|
926
|
06 Nov 2013 |
Stefan Ritt | Info | midas programs "auto start", etc | > "programs auto start" : works but has strange
interactions and side effects, do not use
it.
|
|
771
|
27 Jun 2011 |
Konstantin Olchanski | Info | midas shared memory changes | A number of changes were made to the midas
shared memory implementation for
Linux and MacOS:
|
|
773
|
05 Jul 2011 |
Konstantin Olchanski | Info | midas shared memory changes | > 2) the shared memory type used by an experiment
is recorded in the file .SHM_TYPE.TXT.
|
|
775
|
10 Jul 2011 |
Konstantin Olchanski | Bug Fix | midas shared memory changes | > > 2) the shared memory type used by an experiment
is recorded in the file .SHM_TYPE.TXT.
> > 3) the hostname of the computer where |
|
776
|
11 Jul 2011 |
Konstantin Olchanski | Bug Fix | midas shared memory changes | > > > 2) the shared memory type used by an
experiment is recorded in the file .SHM_TYPE.TXT.
> > > 3) the hostname of the computer where |
|
91
|
20 Nov 2003 |
Konstantin Olchanski | | midas timeout wraparound | While reviving midas on midtig01 after it
was not used for a while, we see
this. Notice negative "last called" numbers. |
|
805
|
20 Jun 2012 |
Konstantin Olchanski | Info | midas vme benchmarks | I am recording here the results from a test
VME system using two VF48 waveform digitizers
and a 64-bit
|
|
806
|
20 Jun 2012 |
Konstantin Olchanski | Info | midas vme benchmarks | > I am recording here the results from a test
VME system using two VF48 waveform digitizers
|
|
807
|
21 Jun 2012 |
Stefan Ritt | Info | midas vme benchmarks | Just for completeness: Attached is the VME
transfer speed I get with the SIS3100/SIS1100
interface using
|
|
809
|
21 Jun 2012 |
Konstantin Olchanski | Info | midas vme benchmarks | > Just for completeness: Attached is the VME
transfer speed I get with the SIS3100/SIS1100
interface using
|
|
810
|
22 Jun 2012 |
Stefan Ritt | Info | midas vme benchmarks | > > Just for completeness: Attached is the
VME transfer speed I get with the SIS3100/SIS1100
interface using
|
|
812
|
24 Jun 2012 |
Konstantin Olchanski | Info | midas vme benchmarks | > > > Just for completeness: Attached is the
VME transfer speed I get with the SIS3100/SIS1100
interface using
|
|
813
|
24 Jun 2012 |
Konstantin Olchanski | Info | midas vme benchmarks | > > I am recording here the results from a
test VME system using two VF48 waveform digitizers
|
|
814
|
25 Jun 2012 |
Stefan Ritt | Info | midas vme benchmarks | > P.S. Observe the ever present unexplained
event rate fluctuations between 130-140 event/sec.
|
|