Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  30 Jan 2025, Pavel Murat, Forum, converting non-MIDAS slow control data into MIDAS history format ? 
    Reply  31 Jan 2025, Pavel Murat, Forum, converting non-MIDAS slow control data into MIDAS history format ? 
    Reply  01 Feb 2025, Pavel Murat, Bug Report, MIDAS history system not using the event timestamps ? test_frontend.pyval_nightly.csv
       Reply  01 Apr 2025, Pavel Murat, Bug Report, MIDAS history system not using the event timestamps ? 
          Reply  01 Apr 2025, Konstantin Olchanski, Bug Report, MIDAS history system not using the event timestamps ? 
             Reply  02 Apr 2025, Pavel Murat, Bug Report, MIDAS history system not using the event timestamps ? 
                Reply  02 Apr 2025, Konstantin Olchanski, Bug Report, MIDAS history system not using the event timestamps ? 
Message ID: 3022     Entry time: 02 Apr 2025     In reply to: 3020     Reply to this: 3023
Author: Pavel Murat 
Topic: Bug Report 
Subject: MIDAS history system not using the event timestamps ? 
> You can always include your "true" data timestamp as the first value in your data.

Are you saying that if the first data word of a history event were a timestamp, 
the MIDAS history system, when plotting the time dependencies, would use that timestamp 
instead of the mlogger timestamp?  

if that is true, what tells MIDAS that the first data word is the timestamp? 

I couldn't find a discussion of that on the page describing the history system - 

 https://daq00.triumf.ca/MidasWiki/index.php/History_System#Frontend_history_event

- perhaps I should be looking at a different page?

-- thanks again, regards, Pasha 
ELOG V3.1.4-2e1708b5