| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2032
|
27 Nov 2020 |
Konstantin Olchanski | Info | Equipment "common" settings in ODB | > Today I addressed a topic which bugged me
since long time.
|
|
|
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 |
|
|
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 |
|
|
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", |
|
|
2041
|
30 Nov 2020 |
Stefan Ritt | Info | Equipment "common" settings in ODB | One more change:
After using the new code for some hours, |
|
|
2042
|
30 Nov 2020 |
Konstantin Olchanski | Info | Equipment "common" settings in ODB | > One more change:
>
> After using the new code for some hours, |
|
|
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
|
|
|
2069
|
06 Jan 2021 |
Isaac Labrie Boulay | Info | Recovering a corrupted ODB using odbinit. | Hi all,
I am currently trying to recover my corrupted |
|
|
2078
|
21 Jan 2021 |
Thomas Lindner | Info | Using external ELOG with newer mhttpd | A warning, in case others have the same problem
I had.
|
|
|
2115
|
02 Mar 2021 |
Konstantin Olchanski | Info | shortest possible sleep | since I am implementing a polled equipment,
I was curious what is the smallest possible
sleep time on current computers.
|
|
|
2116
|
02 Mar 2021 |
Stefan Ritt | Info | shortest possible sleep | Why do you need that? Periodic equipment typically
runs ever ten seconds or so, meaning one
can do this easily in a scheduler.
|
|
|
2117
|
03 Mar 2021 |
Konstantin Olchanski | Info | shortest possible sleep | > Why do you need that?
UNIX/POSIX advertises functions for sleeping |
|
|
2138
|
30 Mar 2021 |
Konstantin Olchanski | Info | INT64/UINT64/QWORD not permitted in ODB and history... Change of TID_xxx data types | > We have to request of a 64-bit integer data
type to be included in MIDAS banks.
> Since 64-bit integers are on some systems |
|
|
2140
|
04 Apr 2021 |
Konstantin Olchanski | Info | bk_init32a data format | In April 4th 2020 Stefan added a new data
format that fixes the well known problem
with alternating banks being
|
|
|
2141
|
04 Apr 2021 |
Konstantin Olchanski | Info | Change of TID_xxx data types | >
> To be consistent, I renamed the old types:
>
|
|
|
2142
|
05 Apr 2021 |
Konstantin Olchanski | Info | blog - convert mfe frontend to tmfe c++ framework | notes from converting ALPHA-g chronobox frontend
fechrono to tmfe c++ framework.
|
|
|
2143
|
05 Apr 2021 |
Konstantin Olchanski | Info | blog - convert mfe frontend to tmfe c++ framework | Result is here:
https://bitbucket.org/expalpha/chronobox_software/src/master/fechrono_tmfe.cxx
|
|
|
2150
|
13 Apr 2021 |
Konstantin Olchanski | Info | bk_init32a data format | Until commit a4043ceacdf241a2a98aeca5edf40613a6c0f575
today, mdump mostly did not work with bank32a
data.
|
|
|
2153
|
14 Apr 2021 |
Stefan Ritt | Info | INT64/UINT64/QWORD not permitted in ODB and history... Change of TID_xxx data types | > These 64-bit data types do not work with
ODB and they do not work with the MIDAS history.
|
|
|
2160
|
06 May 2021 |
Ben Smith | Info | New feature in odbxx that works like db_check_record() | For those unfamiliar, odbxx is the interface
that looks like a C++ map, but automatically
syncs with the ODB - https://midas.triumf.ca/MidasWiki/index.php/Odbxx.
|
|