| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
3174
|
08 Dec 2025 |
Konstantin Olchanski | Suggestion | Get manalyzer to configure midas::odb when running offline | > > #include "manalyzer.h"
> > #include "midasio.h"
> > +#include "odbxx.h"
|
|
|
3175
|
08 Dec 2025 |
Konstantin Olchanski | Suggestion | manalyzer root output file with custom filename including run number | I updated the root helper constructor to give
the user more control over ROOT output file
names.
|
|
|
3178
|
09 Dec 2025 |
Konstantin Olchanski | Bug Report | manalyzer fails to compile on some systems because of missing #include <cmath> | > /code/midas/manalyzer/manalyzer.cxx:799:27:
error: ‘pow’ was not declared in this scope
> 799 | bins[i] = TimeRange*pow(1.1,i)/pow(1.1,Nbins);
|
|
|
3179
|
09 Dec 2025 |
Konstantin Olchanski | Bug Report | odbxx memory leak with JSON ODB dump | > Thanks for reporting this. It was caused
by a
>
|
|
|
3182
|
11 Dec 2025 |
Konstantin Olchanski | Bug Report | odbxx memory leak with JSON ODB dump | > > BTW, it looks like we are parsing the
whole JSON ODB dump (200k+) on every odbxx
access. Can you parse it just once?
|
|
|
3183
|
11 Dec 2025 |
Konstantin Olchanski | Bug Report | manalyzer fails to compile on some systems because of missing #include <cmath> | > TFile.h -> TDirectoryFile.h -> TDirectory.h
-> TNamed.h -> TString.h -> TMathBase.h ->
cmath -> math.h
|
|
|
3185
|
12 Dec 2025 |
Konstantin Olchanski | Bug Report | odbxx memory leak with JSON ODB dump | > > Confirmed fixed, thanks! There are 2 small
changes I made in odbxx.h, please pull.
> There was one missing enable_jsroot in |
|
|
3200
|
05 Feb 2026 |
Konstantin Olchanski | Bug Report | omnibus bugs from running DarkLight | We finished running the DarkLight experiment
and I am reporting accumulated bugs that
we have run into.
|
|
|
3208
|
16 Apr 2026 |
Konstantin Olchanski | Forum | Migrate Legacy code to current Midas version | > I am migrating the full CRIPT muon tomography
detector from MIDAS (SVN Rev.
> 5238, circa 2012) to a more modern release.
|
|
|
3209
|
16 Apr 2026 |
Konstantin Olchanski | Suggestion | mhttpd user permissions | We had our periodic discussion on MIDAS web
page user permissions. (I cannot
find the link to the previous discussions, |
|
|
3212
|
24 Apr 2026 |
Konstantin Olchanski | Bug Report | increasing the max number of hot links in ODB | > when I attempted to increase the max number
of hotlinks in ODB , defined as
> #define MAX_OPEN_RECORDS 256 |
|
|
3215
|
27 Apr 2026 |
Konstantin Olchanski | Bug Report | increasing the max number of hot links in ODB | > Indeed, updating MIDAS clients on each and
every RPI etc in a running experiment may
be a real challenge.
|
|
|
3216
|
27 Apr 2026 |
Konstantin Olchanski | Bug Report | increasing the max number of hot links in ODB | > I wonder why one needs more than 256 hotlinks
at all.
|
|
|
3223
|
21 May 2026 |
Konstantin Olchanski | Info | manalyzer --save-odb | Due my oversight, the code for extracting
ODB dumps from MIDAS data files from rootana/old_analyzer/event_dump.cxx
was missing in
|
|
|
3224
|
21 May 2026 |
Konstantin Olchanski | Bug Report | incompatible ODB XML dumps | While testing manalyzer, I found that it dies
from an exception on odbxx, error message
is "/home/olchansk/packages/midas/include/odbxx.h:1231: |
|
|
3234
|
25 Jun 2026 |
Konstantin Olchanski | Forum | midas forum elog updated | I updated the midas forum elog to the latest
version from git: 083448f7
|
|
|
3235
|
25 Jun 2026 |
Konstantin Olchanski | Bug Report | incompatible ODB XML dumps | > I fixed that by not requiring the handle
explicitly ...
>
|
|
|
3236
|
25 Jun 2026 |
Konstantin Olchanski | Suggestion | Multithreaded deferred transitions | > Multithreaded transitions were introduced
by KO in 2019. Please ask him to make deferred
transitions work
|
|
|
3242
|
08 Jul 2026 |
Konstantin Olchanski | Suggestion | mlogger MySQL improved connection | you can also copy the reconnect code from
history_schema.cxx.
|
|
|
3243
|
08 Jul 2026 |
Konstantin Olchanski | Suggestion | Multithreaded PySequencer | > I was wondering if one can use multiple
pysequencers at the same time and if not
> if this feature is planned in the future? |
|