ID |
Date |
Author |
Topic |
Subject |
Text |
|
1564
|
19 Jun 2019 |
Konstantin Olchanski | Release | midas-2019-06 with cmake and c++ | We are happy to the midas release "midas-2019-06"
with the build system implemented in cmake
and the midas, mxml and mscb
|
|
1578
|
27 Jun 2019 |
Stefan Ritt | Release | midas-2019-06 with cmake and c++ | Please note that
"make cmake" / "make cmake3"
|
|
1706
|
27 Sep 2019 |
Konstantin Olchanski | Release | midas-2019-09 | I created the release branch for midas-2019-09
and tag midas-2019-09-a.
|
|
1747
|
04 Dec 2019 |
Konstantin Olchanski | Release | midas-2019-09-e | > I created the release branch for midas-2019-09
and tag midas-2019-09-a.
> Since the previous release midas-2019-06, |
|
1749
|
11 Dec 2019 |
Konstantin Olchanski | Release | midas-2019-09-g | midas-2019-09-g is here.
- the last bug in the new history plots is |
|
1750
|
22 Dec 2019 |
Konstantin Olchanski | Release | midas-2019-09-i | midas-2019-09-i is here.
- the new sequencer web pages written in |
|
1854
|
16 Mar 2020 |
Konstantin Olchanski | Release | midas-2020-03-a | midas-2020-03-a is here.
Accumulated changes and bug fixes since last |
|
1917
|
22 May 2020 |
Konstantin Olchanski | Release | midas-2020-03-a | > midas-2020-03-a is here.
> checkout the top of branch release/midas-2020-03
(recommended) or
|
|
Draft
|
24 Aug 2020 |
Konstantin Olchanski | Release | midas-2020-12 | midas-2020-12-a is here.
new features and notable updates since midas-2020-03: |
|
2089
|
10 Feb 2021 |
Konstantin Olchanski | Release | midas-2020-12-a | midas-2020-12-a is here, see https://midas.triumf.ca/MidasWiki/index.php/Changelog#2020-12
notable change from previous midas releases:
|
|
2416
|
18 Jul 2022 |
Konstantin Olchanski | Release | midas-2022-05 | There is a release branch for midas-2022-05
and corresponding git tag midas-2022-
05-b. This branch is known to be stable and |
|
160
|
13 Oct 2004 |
Konstantin Olchanski | Suggestion | No al_clear_alarm()? | We have al_trigger_alarm(), but no matching
al_clear_alarm(), and I need it to
clear my alarm once the alarm condition no |
|
161
|
13 Oct 2004 |
Stefan Ritt | Suggestion | No al_clear_alarm()? | > We have al_trigger_alarm(), but no matching
al_clear_alarm(), and I need it to
> clear my alarm once the alarm condition |
|
162
|
13 Oct 2004 |
Konstantin Olchanski | Suggestion | No al_clear_alarm()? | > > We have al_trigger_alarm(), but no matching
al_clear_alarm(), and I need it to
> > clear my alarm once the alarm condition |
|
189
|
22 Dec 2004 |
Stefan Ritt | Suggestion | What to do with invalid data in the history system? | Dealing with the NaN's in the history system
in the past week, a question came
up at PSI about how to deal with invalid |
|
190
|
23 Dec 2004 |
Stefan Ritt | Suggestion | What to do with invalid data in the history system? | I preliminary implemented NaNs into the history
system. It works such that if a
device driver returns a read error status, |
|
191
|
20 Jan 2005 |
Konstantin Olchanski | Suggestion | HOWTO create ROOT objects in the MIDAS analyzer |
With recent changes to mana.c, creation of
user ROOT objects in the MIDAS
|
|
197
|
25 Jan 2005 |
John M O'Donnell | Suggestion | HOWTO create ROOT objects in the MIDAS analyzer | > (preliminary, untested. I will keep this
updated as I get testing feedback)
>
|
|
208
|
21 Apr 2005 |
Konstantin Olchanski | Suggestion | Correct MIDASSYS setting? | Current MIDAS versions nag me about setting
the env.variable MIDASSYS to the
"midas installation directory", but I do |
|
209
|
22 Apr 2005 |
Stefan Ritt | Suggestion | Correct MIDASSYS setting? | > Current MIDAS versions nag me about setting
the env.variable MIDASSYS to the
> "midas installation directory", but I do |
|