| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2019
|
20 Nov 2020 |
Pierre-Andre Amaudruz | Info | Equipment "common" settings in ODB | Indeed this "mirror" of the ODB in settings
option can cause frustration in
particular when we think the ODB is empty |
|
|
2018
|
20 Nov 2020 |
Stefan Ritt | Forum | History plot consuming too much memory | > Taking this down a tangent, I have a mild
concern that a user could temporarily
> flood our gigabit network if we do have |
|
|
2017
|
20 Nov 2020 |
Joseph McKenna | Forum | History plot consuming too much memory | Poking at the behavior of this, its fairly
clear the slow response is from the data
|
|
|
2016
|
19 Nov 2020 |
Stefan Ritt | Forum | History plot consuming too much memory | The history code is right now programmes in
such a way that when you request
an old time window, then all data from that |
|
|
2015
|
19 Nov 2020 |
Joseph McKenna | Forum | History plot consuming too much memory |
A user reported an issue that if they were |
|
|
2014
|
17 Nov 2020 |
Stefan Ritt | Info | Equipment "common" settings in ODB | Today I addressed a topic which bugged me
since long time. The ODB contains
settings under /Equipment/<name>/Common which |
|
|
2013
|
06 Nov 2020 |
Isaac Labrie Boulay | Forum | Building an experiment using CAEN VME interface - unknown type name 'VARIANT_BOOL' | Yes, you are right. That fixed it and my frontend
is compiling.
|
|
|
Draft
|
06 Nov 2020 |
Isaac Labrie Boulay | Forum | Building an experiment using CAEN VME interface - unknown type name 'VARIANT_BOOL' |
|
|
|
2011
|
06 Nov 2020 |
Alexandr Kozlinskiy | Suggestion | cmake build fixes | hi,
there are several problems with current cmake |
|
|
2010
|
05 Nov 2020 |
Pierre-Andre Amaudruz | Forum | Building an experiment using CAEN VME interface - unknown type name 'VARIANT_BOOL' | Hi,
You're building under Linux like. You want |
|
|
2009
|
05 Nov 2020 |
Isaac Labrie Boulay | Forum | Building an experiment using CAEN VME interface - unknown type name 'VARIANT_BOOL' | Hi everyone,
I have been building an experiment using |
|
|
2008
|
21 Oct 2020 |
Soichiro Kuribayashi | Info | About remote control of front end part of MIDAS on chip | Dear Stefan,
Thank you very much for your help.
|
|
|
2007
|
20 Oct 2020 |
Stefan Ritt | Info | About remote control of front end part of MIDAS on chip | We also use a Zynq chip and boot in the following
order:
|
|
|
2006
|
13 Oct 2020 |
Soichiro Kuribayashi | Info | About remote control of front end part of MIDAS on chip | Dear Konstantin,
Thank you very much for your reply and detailed |
|
|
2005
|
13 Oct 2020 |
Konstantin Olchanski | Info | About remote control of front end part of MIDAS on chip | > My name is Soichiro Kuribayashi and I am
a Ph.D. student at Kyoto University.
> I'm a T2K collaborator and working for |
|
|
2004
|
13 Oct 2020 |
Soichiro Kuribayashi | Info | About remote control of front end part of MIDAS on chip | Hello!
My name is Soichiro Kuribayashi and I am |
|
|
2002
|
06 Oct 2020 |
Konstantin Olchanski | Forum | using python client to start and stop run | > The ODB variable "/Runinfo/State" is a symptom
of starting/stopping a run, rather than the
cause.
|
|
|
2001
|
29 Sep 2020 |
Ben Smith | Forum | using python client to start and stop run | The ODB variable "/Runinfo/State" is a symptom
of starting/stopping a run, rather than the
cause.
|
|
|
2000
|
29 Sep 2020 |
Amy Roberts | Forum | using python client to start and stop run | I'm using a python client to start and stop
runs, and the following code *appears*
to set the MIDAS state to "Run"
|
|
|
1999
|
24 Sep 2020 |
Gennaro Tortone | Forum | subrun | Hi,
I was wondering if there is a "mechanism" |
|