| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2028
|
27 Nov 2020 |
Konstantin Olchanski | Forum | History plot consuming too much memory | >
> Tested with midas-2020-08-a up until the
HEAD of develop
|
|
|
2027
|
27 Nov 2020 |
Konstantin Olchanski | Forum | Invalid name "Analyzer/Tests" | > I've recently took the analyzer template
from $MIDASSYS/examples/experiment and
> modified it to be able to use Roody on |
|
|
2026
|
27 Nov 2020 |
Konstantin Olchanski | Suggestion | ODBSET wildcards with array keys in Sequencer files | > The following all fail with "Cannot find
ODB key "<key>""
>
|
|
|
2025
|
25 Nov 2020 |
Amy Roberts | Suggestion | ODBSET wildcards with array keys in Sequencer files | I think the issue may be the version of MIDAS
I'm using. Mine is current as of February
4, 2020.
|
|
|
2024
|
25 Nov 2020 |
Marco Francesconi | Suggestion | ODBSET wildcards with array keys in Sequencer files | I created some keys in my ODB to try to match
yours.
The ODBSET commands you wrote are all working |
|
|
2023
|
25 Nov 2020 |
Amy Roberts | Suggestion | ODBSET wildcards with array keys in Sequencer files | The following all fail with "Cannot find ODB
key "<key>""
|
|
|
2022
|
25 Nov 2020 |
Marco Francesconi | Suggestion | ODBSET wildcards with array keys in Sequencer files | Hi,
I guess the issue is in the "[?]" part of
the command, the indexing is handled differently |
|
|
2021
|
24 Nov 2020 |
Amy Roberts | Suggestion | ODBSET wildcards with array keys in Sequencer files | I'm interested in using the matching feature
for ODBSET explained on
https://midas.triumf.ca/MidasWiki/index.php/Sequencer |
|
|
2020
|
24 Nov 2020 |
Isaac Labrie Boulay | Forum | Invalid name "Analyzer/Tests" | Hi everyone,
I've recently took the analyzer template |
|
|
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 |
|