| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2182
|
28 May 2021 |
Joseph McKenna | Suggestion | Have a list of 'users responsible' in Alarms and Programs odb entries | > I think this is a good idea and I support
it. We have a similar problem in MEG and
|
|
|
2184
|
28 May 2021 |
Joseph McKenna | Suggestion | Have a list of 'users responsible' in Alarms and Programs odb entries | > > I can still make this an array and pass
a std::vector<std::string> into
> > al_trigger_class function?
|
|
|
2189
|
28 May 2021 |
Joseph McKenna | Suggestion | Have a list of 'users responsible' in Alarms and Programs odb entries |
I've updated the branch / pull request to |
|
|
2191
|
31 May 2021 |
Joseph McKenna | Suggestion | Have a list of 'users responsible' in Alarms and Programs odb entries | This list of responsible being attached to
alarm message strings will be great for the
|
|
|
Draft
|
08 Jun 2021 |
Joseph McKenna | Suggestion | Have a list of 'users responsible' in Alarms and Programs odb entries | > > This list of responsible being attached
to alarm message strings ...
> |
|
|
2212
|
09 Jun 2021 |
Joseph McKenna | Suggestion | Have a list of 'users responsible' in Alarms and Programs odb entries | > > This list of responsible being attached
to alarm message strings ...
>
|
|
|
Draft
|
16 Jun 2021 |
Joseph McKenna | Suggestion | Have a list of 'users responsible' in Alarms and Programs odb entries | > > > This list of responsible being attached
to alarm message strings ...
> > |
|
|
2220
|
17 Jun 2021 |
Joseph McKenna | Info | Add support for rtsp camera streams in mlogger (history_image.cxx) | mlogger (history_image) now supports rtsp
cameras, in ALPHA we have
acquisitioned several new network connected |
|
|
2414
|
25 Jun 2022 |
Joseph McKenna | Bug Report | RPC timeout for manalyzer over network |
In ALPHA, I get RPC timeouts running a (reasonably |
|
|
2434
|
21 Aug 2022 |
Joseph McKenna | Suggestion | mvodb functionality to get the 'LastWritten' property of a key |
|
|
|
2783
|
22 Jun 2024 |
Joseph McKenna | Suggestion | manalyzer thread safety and custom http IP binding | Hi all, I hope this is the right place to
post two pull requests, if not, please let
me know where I should be submitting them
|
|
|
2790
|
05 Jul 2024 |
Joseph McKenna | Suggestion | shared pointers for more flexible memory managment of the analysis 'flow' and TMEvent | > Hi all, I hope this is the right place to
post two pull requests, if not, please let
me know where I should be submitting them
|
|
|
2791
|
05 Jul 2024 |
Joseph McKenna | Suggestion | Clean up compiler warning in manalyzer | This is a super small pull request, simple
replace deprecated sprintf with snprintf
|
|
|
2854
|
20 Sep 2024 |
Joseph McKenna | Suggestion | Clean up compiler warning in manalyzer | > > This is a super small pull request, simple
replace deprecated sprintf with snprintf
> > https://bitbucket.org/tmidas/manalyzer/pull-requests/9
|
|
|
756
|
15 Apr 2011 |
Jonathan Toebbe | Forum | Can't get example frontend to talk to khyt1331 kernel driver | I'm brand new to MIDAS, and C system programming
in general, so please be
gentle. I've compiled and installed MIDAS |
|
|
248
|
03 Jan 2006 |
John O'Donnell | Info | How do I do custom event building? | At DANCE we have a similar issue. We are
still doing "software
handshaking" between multiple frontends (15 |
|
|
779
|
05 Sep 2011 |
John McMillan | Forum | khyt1331 under scientific linux 5.5? | Hello,
I'm trying to build khyt1331 under
scientific linux 5.5, kernel
|
|
|
21
|
09 Jul 2004 |
John M O'Donnell | | Introduction of environment variable MIDASSYS | For a long time the "de facto" standard was
to spread a package around in many
directories under /usr/local. This proved |
|
|
193
|
21 Jan 2005 |
John M O'Donnell | Bug Report | Persistency problem with h1_book() & co | > The current h1_book() macros (and the previous
example analyzer code) have an
> odd persistency problem: for example, the |
|
|
196
|
25 Jan 2005 |
John M O'Donnell | Bug Report | Persistency problem with h1_book() & co | So now that cvs is reachable again I have
confirmed that
the code segment
|
|