| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1655
|
08 Aug 2019 |
Stefan Ritt | Suggestion | midas cmake migration | I just tried CMake 3.1.0 and it worked with
midas. So I believe all versions between
3.1.0 and 3.6.1 are ok.
|
|
|
1742
|
28 Nov 2019 |
Konstantin Olchanski | Bug Report | midas alarm sound unreliable in google-chrome | I accidentally discovered a problem with the
alarm sounds played by midas.
|
|
|
1743
|
28 Nov 2019 |
Stefan Ritt | Bug Report | midas alarm sound unreliable in google-chrome | The document
https://docs.google.com/document/d/1_278v_plodvgtXSgnEJ0yjZJLg14Ogf-ekAFNymAJoU/edit
|
|
|
2767
|
16 May 2024 |
Konstantin Olchanski | Bug Report | midas alarm borked condition evaluation | I am updating the TRIUMF IRIS experiment to
the latest version of MIDAS. I see following
error messages in midas.log:
|
|
|
2768
|
17 May 2024 |
Stefan Ritt | Bug Report | midas alarm borked condition evaluation | This is a common problem I also encountered
in the past. You get a low-level ODB access
error (could also be a read of a non-existing |
|
|
2769
|
17 May 2024 |
Konstantin Olchanski | Bug Report | midas alarm borked condition evaluation | > This is a common problem I also encountered
in the past. You get a low-level ODB access
error (could also be a read of a non-existing |
|
|
2771
|
17 May 2024 |
Konstantin Olchanski | Bug Report | midas alarm borked condition evaluation | >
> And I think I know what caused the original
problem in IRIS experiment, I think the list |
|
|
Draft
|
18 May 2024 |
Stefan Ritt | Bug Report | midas alarm borked condition evaluation | For everybody using EPICS: There is now a
new system called MSetPoint (Midas Set Point)
to control whole beamlines via EPICS.
|
|
|
2773
|
18 May 2024 |
Stefan Ritt | Bug Report | midas alarm borked condition evaluation | For everybody using EPICS: There is now a
new system called MSetPoint (Midas Set Point)
to control whole beamlines via EPICS.
|
|
|
213
|
18 Aug 2005 |
Konstantin Olchanski | Info | midas Makefile changes | Minor Makefile changes:
- add "-m32" gcc flag to force 32-bit compilation
on 64-bit Linux.
|
|
|
1122
|
16 Oct 2015 |
Konstantin Olchanski | Info | midas JSON-RPC interface | To improve on the existing HTTP "GET" based
AJAX interface to MIDAS, I have been looking
at other possible RPCs.
|
|
|
1126
|
29 Oct 2015 |
Konstantin Olchanski | Info | midas JSON-RPC interface | >
> My implementation follows these internet
standards:
|
|
|
1132
|
02 Nov 2015 |
Konstantin Olchanski | Info | midas JSON-RPC interface | > >
> > JSON-RPC My implementation follows these
internet standards:
|
|
|
281
|
28 Jul 2006 |
Konstantin Olchanski | Bug Fix | mhttpd: use more strlcpy(), fix a few bugs | While investigating the mhttpd password error
with the MacOS Safari browser, I
found that it was caused by an strcpy() buffer |
|
|
372
|
10 May 2007 |
Konstantin Olchanski | Bug Fix | mhttpd: fix broken boolean arrays in "edit on start" | For some time now, boolean arrays did not
work correctly in "/experiment/edit on start".
This is now fixed
|
|
|
448
|
27 Feb 2008 |
Konstantin Olchanski | Bug Report | mhttpd: cannot attach history to elog | From "history" pages, the "create elog" button
stopped working - it takes us to the elog
entry form, but
|
|
|
449
|
28 Feb 2008 |
Konstantin Olchanski | Bug Report | mhttpd: cannot attach history to elog | > From "history" pages, the "create elog"
button stopped working - it takes us to the
elog entry form, but
|
|
|
125
|
12 Oct 2003 |
Konstantin Olchanski | | mhttpd: add Elog text to outgoing email. | This commit adds the elog message text to
the outgoing email message. This
functionality has been requested a logn time |
|
|
126
|
13 Oct 2003 |
Stefan Ritt | | mhttpd: add Elog text to outgoing email. | > around to implement it, until now. I also
added assert() traps for the most
> common array overruns in the Elog code.
|
|
|
127
|
13 Oct 2003 |
Konstantin Olchanski | | mhttpd: add Elog text to outgoing email. | > > around to implement it, until now. I also
added assert() traps for the most
> > common array overruns in the Elog code.
|
|