| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2053
|
15 Dec 2020 |
Konstantin Olchanski | Forum | history and variables confusion | I think you are facing several problems:
a) mlogger does not clearly explain what |
|
|
2052
|
11 Dec 2020 |
Frederik Wauters | Forum | history and variables confusion | 1. ok, so calling the same readout functions
from different equipments is just a bad idea,
my bad, no blame for Midas to write data |
|
|
2051
|
10 Dec 2020 |
Frederik Wauters | Forum | history and variables confusion | I wanted to have a c++ style driver, e.g.
a instance of a "PowerSupply" class. This
was not compatible with the list of DEVICE_DRIVER |
|
|
2050
|
09 Dec 2020 |
Stefan Ritt | Forum | history and variables confusion | First, the writing of banks is completely
independent of the history system. Banks
go to the log file only,
|
|
|
2049
|
09 Dec 2020 |
Frederik Wauters | Forum | history and variables confusion | I have a fe, with 2 "equipments" (2 different
types of LV supplies).
|
|
|
2048
|
07 Dec 2020 |
Isaac Labrie Boulay | Forum | Invalid name "Analyzer/Tests" | > https://bitbucket.org/tmidas/midas/issues/298/invalid-odb-names-in-example-midas
> K.O.
|
|
|
2047
|
01 Dec 2020 |
Ben Smith | Forum | subrun | We use the lazylogger for something similar
to this. You can specify the path to a custom
script, and it will be run for each midas |
|
|
2046
|
01 Dec 2020 |
Stefan Ritt | Forum | subrun | There is no "mechanism" foreseen to be executed
after each subrun. But you could
run a shell script after each run which loops |
|
|
2045
|
30 Nov 2020 |
Konstantin Olchanski | Info | more wisdom from linux kernel people | As you may know, I am a big fan of two software
projects - the linux kernel and ROOT. The
linux kernel is one of
|
|
|
2044
|
30 Nov 2020 |
Konstantin Olchanski | Suggestion | ODBSET wildcards with array keys in Sequencer files | >
> we are considering to make the range selection
uniform among json, sequencer and
|
|
|
2043
|
30 Nov 2020 |
Konstantin Olchanski | Suggestion | ODBSET wildcards with array keys in Sequencer files | > I totally agree that we should have a consistent
formatting for array index expansion.
> I had a look to the mjsonrpc code and I |
|
|
2042
|
30 Nov 2020 |
Konstantin Olchanski | Info | Equipment "common" settings in ODB | > One more change:
>
> After using the new code for some hours, |
|
|
2041
|
30 Nov 2020 |
Stefan Ritt | Info | Equipment "common" settings in ODB | One more change:
After using the new code for some hours, |
|
|
2040
|
30 Nov 2020 |
Stefan Ritt | Suggestion | ODBSET wildcards with array keys in Sequencer files | Hi Konstantin,
we are considering to make the range selection |
|
|
2039
|
30 Nov 2020 |
Stefan Ritt | Info | Equipment "common" settings in ODB | Ok, I implemented it the following way:
- Added a boolean flag "equipment_common_overwrite", |
|
|
2038
|
30 Nov 2020 |
Marco Francesconi | Suggestion | ODBSET wildcards with array keys in Sequencer files | I totally agree that we should have a consistent
formatting for array index expansion.
I had a look to the mjsonrpc code and I found |
|
|
2037
|
27 Nov 2020 |
Konstantin Olchanski | Info | Equipment "common" settings in ODB | Yes, I think this will work.
For old mfe.c frontends, global variable |
|
|
2036
|
27 Nov 2020 |
Stefan Ritt | Info | Equipment "common" settings in ODB | Ok, so what about the following proposal:
- I change back the mfe.cxx code to behave |
|
|
2035
|
27 Nov 2020 |
Konstantin Olchanski | Forum | Invalid name "Analyzer/Tests" | https://bitbucket.org/tmidas/midas/issues/298/invalid-odb-names-in-example-midas
K.O. |
|
|
2034
|
27 Nov 2020 |
Konstantin Olchanski | Suggestion | cmake build fixes |
Hi, Alexandr, thank you for making improvements
to MIDAS. I have some question
|
|