| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1964
|
15 Jul 2020 |
Stefan Ritt | Info | Minimal CMakeLists.txt for your midas front-end | Since a few people asked me, here is a "minimal"
CMakeLists.txt file for a user-written front-end
|
|
|
1967
|
10 Aug 2020 |
Stefan Ritt | Bug Report | data missing in runXXXXXX.mid | > Dear all
>
> We just started our beam time at ILL and |
|
|
1969
|
10 Aug 2020 |
Stefan Ritt | Bug Report | data missing in runXXXXXX.mid | > Both set to -1. We only have one logging
channel. If we run a sequence with a few
runs and the
|
|
|
1971
|
10 Aug 2020 |
Stefan Ritt | Bug Report | data missing in runXXXXXX.mid | > So I did a quick check. The file size is
about the same (322K and 329K). When I dump
the .mid I don't see
|
|
|
1973
|
10 Aug 2020 |
Stefan Ritt | Bug Report | data missing in runXXXXXX.mid | Have you tried longer files? Maybe a few 100
MB or so. Maybe a buffer is not flushed correctly
at the end of a run. |
|
|
1978
|
10 Aug 2020 |
Stefan Ritt | Bug Report | data missing in runXXXXXX.mid | I have to reproduce the problem to fix it.
Why don't you go and modify midas/examples/experiment/frontend.cxx
in such a way that
|
|
|
1982
|
13 Aug 2020 |
Stefan Ritt | Suggestion | adding db_get_mode ti check access mode for keys | > Hello,
>
> I am wondering if there is a function that |
|
|
1985
|
24 Aug 2020 |
Stefan Ritt | Forum | time information |
> 1. Is it possible to get "Running time"
using, for example, jsonrpc? (please see |
|
|
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:
|
|
|
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 |
|
|
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 |
|
|
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 |
|
|
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 |
|
|
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", |
|
|
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 |
|
|
2041
|
30 Nov 2020 |
Stefan Ritt | Info | Equipment "common" settings in ODB | One more change:
After using the new code for some hours, |
|
|
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 |
|
|
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,
|
|
|
2059
|
16 Dec 2020 |
Stefan Ritt | Forum | Issues building banks. | > This is very hard to do using the mfe.c
frontend. (the main reason I wrote the TMFE
C++ frontend class).
|
|
|
2062
|
18 Dec 2020 |
Stefan Ritt | Suggestion | Code formatting | May I ask for your quick opinion on code formatting.
MIDAS had a coding style
which pretty much followed the ROOT coding |
|