| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2924
|
19 Dec 2024 |
Stefan Ritt | Bug Report | [History plots] "Jump to current time" resets x range to 7d | I had put in a check which limits the range
to 7d into the past if you press the "play"
button, but now I'm not sure why this was |
|
|
2936
|
01 Feb 2025 |
Pavel Murat | Bug Report | MIDAS history system not using the event timestamps ? | > I have a time series of slow control measurements
in an ASCII format -
> data records in a format (run_number, time, |
|
|
2943
|
19 Feb 2025 |
Lukas Gerritzen | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | We have a frontend for slow control with a
lot of legacy code. I wanted to add a new
equipment using the
|
|
|
2944
|
24 Feb 2025 |
Stefan Ritt | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | The commit that introduced the write cache
size check is https://bitbucket.org/tmidas/midas/commits/3619ecc6ba1d29d74c16aa6571e40920018184c0
|
|
|
2947
|
11 Mar 2025 |
Federico Rezzonico | Bug Report | python hist_get_events not returning events, but javascript does | After starting midas (mhttpd &, and mlogger
-D) and running the `fetest` frontend I went
into the midas/python/examples directory |
|
|
2948
|
11 Mar 2025 |
Ben Smith | Bug Report | python hist_get_events not returning events, but javascript does | > Valid events are:
> Enter event name:
>
|
|
|
2949
|
14 Mar 2025 |
Konstantin Olchanski | Bug Report | python hist_get_events not returning events, but javascript does | > After starting midas (mhttpd &, and mlogger
-D) and running the `fetest` frontend I went
into the midas/python/examples directory |
|
|
2951
|
16 Mar 2025 |
Federico Rezzonico | Bug Report | python hist_get_events not returning events, but javascript does | > After starting midas (mhttpd &, and mlogger
-D) and running the `fetest` frontend I went
into the midas/python/examples directory |
|
|
2952
|
17 Mar 2025 |
Federico Rezzonico | Bug Report | python hist_get_recent_data returns no historical data | Setup:
setting up midas, starting mhttpd and mlogger
and running fetest.
|
|
|
2953
|
17 Mar 2025 |
Ben Smith | Bug Report | python hist_get_recent_data returns no historical data | Unfortunately I again cannot reproduce this:
$ python ~/DAQ/midas_latest/python/examples/basic_hist_script.py
|
|
|
Draft
|
17 Mar 2025 |
Federico Rezzonico | Bug Report | python hist_get_recent_data returns no historical data | > Unfortunately I again cannot reproduce this:
>
> $ python ~/DAQ/midas_latest/python/examples/basic_hist_script.py
|
|
|
2955
|
18 Mar 2025 |
Federico Rezzonico | Bug Report | python hist_get_recent_data returns no historical data | > Unfortunately I again cannot reproduce this:
>
> $ python ~/DAQ/midas_latest/python/examples/basic_hist_script.py
|
|
|
2956
|
18 Mar 2025 |
Konstantin Olchanski | Bug Report | python hist_get_recent_data returns no historical data | >
> However right after running these commands
I removed a .SHM_HOST.TXT file
|
|
|
2960
|
19 Mar 2025 |
Konstantin Olchanski | Bug Report | python hist_get_events not returning events, but javascript does | > beta version of macOS: Switching beta updates
off fixed the issue.
|
|
|
2963
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | midas equipment "format" | we are migrating the dragon experiment from
an old mac to a new mac studio and we ran
into a problem
|
|
|
2965
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | please fix compiler warning | Unnamed person who added this clever bit of
c++ coding, please fix this compiler warning.
Stock g++ on Ubuntu LTS 24.04. Thanks in |
|
|
2966
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | please fix mscb compiler warning | I am getting a scary compiler warning from
MSCB code. I generally avoid touching MSCB
code because I have no MSCB hardware to test |
|
|
2972
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | I think I added the cache size correctly:
{"Trigger", /* equipment |
|
|
2973
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | the main purpose of the event buffer write
cache is to prevent high contention for the
|
|
|
2974
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | > the main purpose of the event buffer write
cache
|
|