| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
271
|
23 Jul 2006 |
Art Olin | Forum | File output for histories | The ALPHA experiment at CERN has recently
adopted MIDAS, and the history data in numerical
form is needed by the collaboration. Furthermore |
|
|
272
|
23 Jul 2006 |
Stefan Ritt | Forum | File output for histories | [quote="Art Olin"]Basically we need the output
from the mhist code. The most convenient,
and possibly easiest implementation would |
|
|
273
|
23 Jul 2006 |
Art Olin | Forum | File output for histories | Hi, Stefan,
Using mhist is how I'll start, but I'm getting |
|
|
274
|
24 Jul 2006 |
Sergio Ballestrero | Forum | File output for histories | Hi Art,
you can make the process somewhat less painful
by using the Plink (from PuTTY) to run mhist |
|
|
2798
|
07 Aug 2024 |
Lukas Gerritzen | Bug Report | File name bug in csv export | When I export data from a history plot, I
get nonsensical filenames. For example, for
data from today, I got "Xenon-Vacuum-20247107-152815-20247107-160032.csv".
|
|
|
2799
|
07 Aug 2024 |
Stefan Ritt | Bug Report | File name bug in csv export | Thanks. Fixed. Committed. Pulled on megon02.
Stefan |
|
|
2800
|
07 Aug 2024 |
Lukas Gerritzen | Bug Report | File name bug in csv export | Thanks. I think, mplot.js:1844 should be changed
as well, but I haven't tried it with mplot. |
|
|
2801
|
07 Aug 2024 |
Stefan Ritt | Bug Report | File name bug in csv export | Fixed as well. |
|
|
1625
|
22 Jul 2019 |
Hassan | Bug Report | Fetest History Plot | Hi,
We've been trying to run Fetest in the attempt |
|
|
1631
|
24 Jul 2019 |
Pierre-Andre Amaudruz | Bug Report | Fetest History Plot | > Hi,
>
> We've been trying to run Fetest in the |
|
|
Draft
|
25 Jul 2019 |
Hassan | Bug Report | Fetest History Plot |
=================================================================
|
|
|
Draft
|
26 Jul 2019 |
Hassan | Bug Report | Fetest History Plot |
===================================================================================
[lm17773@it038146 ~]$ cd /opt/midas_software/midas/bin/
|
|
|
1636
|
26 Jul 2019 |
Hassan | Bug Report | Fetest History Plot | Hi, our logger was running. I have tried restarting
mlogger (even though we haven't
changed variable names). We ran the following |
|
|
1657
|
09 Aug 2019 |
Konstantin Olchanski | Bug Report | Fetest History Plot | > Hi, our logger was running.
|
|
|
1658
|
09 Aug 2019 |
Konstantin Olchanski | Bug Report | Fetest History Plot | > Hi, our logger was running.
Please do these simple tests:
|
|
|
1321
|
15 Nov 2017 |
Andreas Knecht | Suggestion | Feature request: Separate ODB flag to show programs on "Programs page" | Currently one has to set the required flag
in the ODB (e.g., /Programs/Logger/Required)
to "y" for the program
|
|
|
1322
|
17 Nov 2017 |
Konstantin Olchanski | Suggestion | Feature request: Separate ODB flag to show programs on "Programs page" | > Currently one has to set the required flag
in the ODB (e.g., /Programs/Logger/Required)
to "y" for the program
|
|
|
1326
|
21 Nov 2017 |
Stefan Ritt | Suggestion | Feature request: Separate ODB flag to show programs on "Programs page" | > > Currently one has to set the required
flag in the ODB (e.g., /Programs/Logger/Required)
to "y" for the program
|
|
|
1119
|
28 Sep 2015 |
Anthony Villano | Suggestion | Feature Request: MIDAS sequencer abort. |
I am working for the SuperCDMS collaboration
on some DAQ issues for our upcoming
|
|
|
1123
|
22 Oct 2015 |
Konstantin Olchanski | Suggestion | Feature Request: MIDAS sequencer abort. | > it would be useful to have a kind of scripted
"abort" for when something goes wrong ...
|
|