Back Midas Rome Roody Rootana

Midas DAQ System  Not logged in

Back  |  Find  |  Login  |  Help

24 Apr 2020, Pintaudi Giorgio, Forum, API to read MIDAS format file        24 Apr 2020, Stefan Ritt, Forum, API to read MIDAS format file           24 Apr 2020, Pintaudi Giorgio, Forum, API to read MIDAS format file              24 Apr 2020, Stefan Ritt, Forum, API to read MIDAS format file        25 Apr 2020, Konstantin Olchanski, Forum, API to read MIDAS format file           03 May 2020, Pintaudi Giorgio, Forum, API to read MIDAS format file              03 May 2020, Konstantin Olchanski, Forum, API to read MIDAS format file                 04 May 2020, Pintaudi Giorgio, Forum, API to read MIDAS format file              03 May 2020, Stefan Ritt, Forum, API to read MIDAS format file                 26 May 2020, Pintaudi Giorgio, Forum, API to read MIDAS format file

This is a draft message, edit and submit it to make it permanent   Message ID: 1881     Entry time: 24 Apr 2020     In reply to: 1880 Author: Pintaudi Giorgio  Topic: Forum  Subject: API to read MIDAS format file

Stefan Ritt wrote: I guess all three options would work. I just tried mhist and it still works with the "FILE" historymhist -e <equipment name> -v <variable name> -h 10for dumping a variable for the last 10 hours.I could not get mhdump to work with current history files, maybe it only works with "MIDAS" history and not "FILE" history (see https://midas.triumf.ca/MidasWiki/index.php/History_System#History_drivers). Maybe Konstantin who wrote mhdump has some idea.Writing your own parser is certainly possible (even in Python), but of course more work.Stefan Thank you for the quick reply. Do notice that we have "MIDAS" history files and not "FILE", so both mhist and mhdump should be fine (however I have only tested mhist). Hipotetically, which one between mhist and mhdump do you think is better suited to be "batched"? I mean to be controlled and read by a routine?

ELOG V3.1.4-2e1708b5