ELOG Midas

Back Midas Rome Roody Rootana

Midas DAQ System, Page 9 of 154

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

3071 Entries

Goto page Previous 1, 2, 3 ... 8, 9, 10 ... 152, 153, 154 Next

ID	Date	Author	Topic	Subject
2940	06 Feb 2025	Konstantin Olchanski	Forum	Transition from mana -> manalyzer
> > Is there a clear migration docu somewhere? I can also give you links to the alpha-g analyzer (very complex) and the DarkLight trigger TDC analyzer (very simple), there is also analyzer examples of in-between complexity. K.O.
2939	06 Feb 2025	Konstantin Olchanski	Forum	Transition from mana -> manalyzer
> Could somebody please give me a boost? no need to shout into the void, it is pretty easy to identify the author of manalyzer and ask me directly. > we are planning to migrate from mana to manalyzer. I started to have a look into it and realized that I have some lose ends. > Is there a clear migration docu somewhere? README.md and examples in the manalyzer git repository. If something is missing, or unclear, please ask. > Currently I understand it the following way (which might be wrong): > The class TARunObject is used to write analyzer modules which are registered by TAFactory. I hope this is right? Please read the README file. It explains what is going on there. Design of manalyzer had 2 main goals: a) lifetime of all c++ objects (and ROOT objects) is well defined (to fix a design defect in rootana) b) event flow and data flow are documentable (problem in mfe.c frontends, etc) > However, in mana there is an analyzer implemented by the user which binds the modules and has additional routines: > analyzer_init(), analyzer_exit(), analyzer_loop() > ana_begin_of_run(), ana_end_of_run(), ana_pause_run(), ana_resume_run() > which we are using. I have never used the mana analyzer, I wrote the c++ rootana analyzer very early on (first commit in 2006). But the basic steps should all be there for you: - initialization (create histograms, open files) can be done in the module constructor or in BeginRun() - finalization (fit histograms, close files) should be done in EndRun() - event processing (obviously) in Analyze() - pause run, resume run and switch to next subrun file have corresponding methods - all the "flow" and multithreading stuff you can ignore to first order. To start the migration, I recommend you take manalyzer_example_root.cxx and start stuffing it with your code. If you run into any problems, I am happy to help with them. Ask here or contact me directly. > This part I somehow miss in manalyzer, most probably due to lack of understanding, and missing documentation. True, I wrote a migration guide for the frontend mfe.c to c++ tmfe, because we do this migration quite often. But I never wrote a migration guide from mana.c analyzer, because we never did such migration. Most experiments at TRIUMF are post-2006 and use rootana in it's different incarnations. P.S. I designed the C++ TMFe frontend after manalyzer and I think it came out quite better, I especially value the design input from Stefan, Thomas, Pierre, Joseph and Ben. P.P.S. Be free to ignore all this manalyzer business and write your own analyzer based on the midasio library: int main() { TMReaderInteraface* f = TMNewReader(file.mid.gz"); while (1) { TMEvent* e = TMReadEvent(f); dwim(e); delete e; } delete f; } For online processing I use the TMFe class, it has enough bits to be a frontend and an analyzer, or you can use the older TMidasOnline from rootana. Access to ODB is via the mvodb library, which is new in midas, but has been part of rootana and my frontend toolkit since at least 2011 or earlier, inspired by Peter Green's even older "myload" ODB access library. K.O.
2938	05 Feb 2025	Andrea Capra	Forum	Transition from mana -> manalyzer
Hi Andreas, please find in elog:2938/1 a short introduction that I wrote sometime ago. I'm glad to offer additional support, if needed. > Hi, > > we are planning to migrate from mana to manalyzer. I started to have a look into it and realized that I have some lose ends. > Is there a clear migration docu somewhere? > > Currently I understand it the following way (which might be wrong): > The class TARunObject is used to write analyzer modules which are registered by TAFactory. I hope this is right? > > However, in mana there is an analyzer implemented by the user which binds the modules and has additional routines: > analyzer_init(), analyzer_exit(), analyzer_loop() > ana_begin_of_run(), ana_end_of_run(), ana_pause_run(), ana_resume_run() > which we are using. > > This part I somehow miss in manalyzer, most probably due to lack of understanding, and missing documentation. > > Could somebody please give me a boost?
Attachment 1: dsadc_analyzer_midas_elog.pdf

2937	05 Feb 2025	Andreas Suter	Forum	Transition from mana -> manalyzer
Hi, we are planning to migrate from mana to manalyzer. I started to have a look into it and realized that I have some lose ends. Is there a clear migration docu somewhere? Currently I understand it the following way (which might be wrong): The class TARunObject is used to write analyzer modules which are registered by TAFactory. I hope this is right? However, in mana there is an analyzer implemented by the user which binds the modules and has additional routines: analyzer_init(), analyzer_exit(), analyzer_loop() ana_begin_of_run(), ana_end_of_run(), ana_pause_run(), ana_resume_run() which we are using. This part I somehow miss in manalyzer, most probably due to lack of understanding, and missing documentation. Could somebody please give me a boost?
2936	01 Feb 2025	Pavel Murat	Bug Report	MIDAS history system not using the event timestamps ?
> I have a time series of slow control measurements in an ASCII format - > data records in a format (run_number, time, temperature, voltage1, ..., voltageN), > and, if possible, would like to convert them into a MIDAS history format. > > Making MIDAS events out of that data is easy, but is it possible to preserve > the time stamps? - Logically, this boils down to whether it is possible to have > the event time set by a user frontend It looks that the original question was not as naive as I expected and may be pointing to a subtle bug. I have implemented a python frontend - essentially a clone of https://bitbucket.org/tmidas/midas/src/develop/python/midas/frontend.py reading the old slow control data and setting the event.header.timestamp's to some dates from the year of 2022. When I run MIDAS and read the "old slow control events", one event in 10 seconds, the MIDAS Event Dump utility shows the data with the correct event timestamps, from the year of 2022. However the history plots show the event parameters with the timestamps from Feb 01 2025 and the adjacent data points separated by 10 sec. Is it possible that the history system uses its own timestamp setting instead of using timestamps from the event headers? - Under normal circumstances, the two should be very close, and that could've kept the issue hidden... -- thanks, regards, Pasha UPDATE: I attached the frontend code and the input data file it is reading. The data file should reside in the local directory - the frontend code doesn't have everything fully automated for the test, -- an integer field "/Mu2e/Offline/Ops/LastTime" would need to be created manually -- the history plots would need to be declared manually
Attachment 1: test_frontend.py
#!/usr/bin/env python """ Example of a basic midas frontend that has one periodic equipment. See `examples/multi_frontend.py` for an example that uses more features (frontend index, polled equipment, ODB settings etc). """ import midas import midas.frontend import midas.event import time, os, sys from datetime import datetime #import TRACE #TRACE_NAME = 'test_frontend.py' class MyPeriodicEquipment(midas.frontend.EquipmentBase): """ We define an "equipment" for each logically distinct task that this frontend performs. For example, you may have one equipment for reading data from a device and sending it to a midas buffer, and another equipment that updates summary statistics every 10s. Each equipment class you define should inherit from `midas.frontend.EquipmentBase`, and should define a `readout_func` function. If you're creating a "polled" equipment (rather than a periodic one), you should also define a `poll_func` function in addition to `readout_func`. """ def __init__(self, client): # The name of our equipment. This name will be used on the midas status # page, and our info will appear in /Equipment/MyPeriodicEquipment in # the ODB. equip_name = "MyPeriodicEquipment" # Define the "common" settings of a frontend. These will appear in # /Equipment/MyPeriodicEquipment/Common. The values you set here are # only used the very first time this frontend/equipment runs; after # that the ODB settings are used. default_common = midas.frontend.InitialEquipmentCommon() default_common.equip_type = midas.EQ_PERIODIC default_common.buffer_name = "SYSTEM" default_common.trigger_mask = 0 default_common.event_id = 1 default_common.period_ms = 100 default_common.read_when = midas.RO_ALWAYS default_common.log_history = 1 # You MUST call midas.frontend.EquipmentBase.__init__ in your equipment's __init__ method! midas.frontend.EquipmentBase.__init__(self, client, equip_name, default_common) # You can set the status of the equipment (appears in the midas status page) self.set_status("Initialized") self._verbose = 1; # --------------------------------------------------------------------- def Print(self,Name,level,Message): if(level>self._verbose): return 0; now = time.strftime('%Y/%m/%d %H:%M:%S',time.localtime(time.time())) message = now+' [ GridSubmit::'+Name+' ] '+Message print(message) def readout_func(self): """ For a periodic equipment, this function will be called periodically (every 100ms in this case). It should return either a `cdms.event.Event` or None (if we shouldn't write an event). """ last_time = self.client.odb_get('/Mu2e/Offline/Ops/LastTime') self.Print('readout_func',1,f'last_time:{last_time}') # cmd = 'dqmTool print-numbers --source 5 --value 6 --expand' cmd = 'cat val_nightly.csv' self.Print('readout_func',1,'executing cmd:%s'%cmd) out=os.popen(cmd).readlines() event = None; for line in out: # print(line) words = line.strip().split(',') #------------------------------------------------------------------------------ # ['91', '5228', '0.0', '0 5', 'valNightly', 'reco', 'day', '0 6', 'ops', 'stats', 'CPU 11', '4', '0', '0', '0', '0', '2022-01-11 00:01:00-06:00', '2022-01-11 00:01:00-06:00'] #------------------------------------------------------------------------------ # In this example, we just make a simple event with one bank. dt = datetime.strptime(words[17], "%Y-%m-%d %H:%M:%S%z"); ts = dt.timestamp(); if (ts > last_time) : data = [] print(words); event = midas.event.Event() data.append(float(words[0])); data.append(float(words[1])); data.append(float(words[2])); event.create_bank("OFLN", midas.TID_FLOAT, data) event.header.timestamp = int(ts); self.client.odb_set('/Mu2e/Offline/Ops/LastTime',ts) print(f'SET_NEW last_time:{ts} dt:{dt}') # self.Print('readout_func',1,f'SET_NEW last_time:{ts} dt:{dt}') break; return event class MyFrontend(midas.frontend.FrontendBase): """ A frontend contains a collection of equipment. You can access self.client to access the ODB etc (see `midas.client.MidasClient`). """ def __init__(self): # You must call __init__ from the base class. midas.frontend.FrontendBase.__init__(self, "myfe_name") # You can add equipment at any time before you call `run()`, but doing # it in __init__() seems logical. self.add_equipment(MyPeriodicEquipment(self.client)) self._verbose = 1 def begin_of_run(self, run_number): """ This function will be called at the beginning of the run. You don't have to define it, but you probably should. You can access individual equipment classes through the `self.equipment` dict if needed. """ self.set_all_equipment_status("Running", "greenLight") self.client.msg("Frontend has seen start of run number %d" % run_number) return midas.status_codes["SUCCESS"] def end_of_run(self, run_number): self.set_all_equipment_status("Finished", "greenLight") self.client.msg("Frontend has seen end of run number %d" % run_number) return midas.status_codes["SUCCESS"] def frontend_exit(self): """ Most people won't need to define this function, but you can use it for final cleanup if needed. """ print("Goodbye from user code!") if __name__ == "__main__": # The main executable is very simple - just create the frontend object, # and call run() on it. print("EMOE"); # TRACE.TRACE(7,'EMOEM',TRACE_NAME) with MyFrontend() as my_fe: my_fe.run()
Attachment 2: val_nightly.csv
21,4219,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 6,4,0,0,0,0,2022-01-06 00:01:00-06:00,2022-01-06 00:01:00-06:00 35,4999,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 7,4,0,0,0,0,2022-01-07 00:01:00-06:00,2022-01-07 00:01:00-06:00 49,4187,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 8,4,0,0,0,0,2022-01-08 00:01:00-06:00,2022-01-08 00:01:00-06:00 63,3875,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 9,4,0,0,0,0,2022-01-09 00:01:00-06:00,2022-01-09 00:01:00-06:00 77,4498,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 10,4,0,0,0,0,2022-01-10 00:01:00-06:00,2022-01-10 00:01:00-06:00 91,5228,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 11,4,0,0,0,0,2022-01-11 00:01:00-06:00,2022-01-11 00:01:00-06:00 105,4682,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 12,4,0,0,0,0,2022-01-12 00:01:00-06:00,2022-01-12 00:01:00-06:00 119,4364,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 13,4,0,0,0,0,2022-01-13 00:01:00-06:00,2022-01-13 00:01:00-06:00 133,5069,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 14,4,0,0,0,0,2022-01-14 00:01:00-06:00,2022-01-14 00:01:00-06:00 147,3848,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 15,4,0,0,0,0,2022-01-15 00:01:00-06:00,2022-01-15 00:01:00-06:00 161,5248,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 16,4,0,0,0,0,2022-01-16 00:01:00-06:00,2022-01-16 00:01:00-06:00 175,5276,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 17,4,0,0,0,0,2022-01-17 00:01:00-06:00,2022-01-17 00:01:00-06:00 189,5089,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 18,4,0,0,0,0,2022-01-18 00:01:00-06:00,2022-01-18 00:01:00-06:00 203,4789,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 19,4,0,0,0,0,2022-01-19 00:01:00-06:00,2022-01-19 00:01:00-06:00 217,4652,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 20,4,0,0,0,0,2022-01-20 00:01:00-06:00,2022-01-20 00:01:00-06:00 232,5343,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 23,5,0,0,0,0,2022-01-21 00:01:00-06:00,2022-01-21 00:01:00-06:00 246,4896,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 30,5,0,0,0,0,2022-01-22 00:01:00-06:00,2022-01-22 00:01:00-06:00 296,4812,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 46,5,0,0,0,0,2022-01-23 00:01:00-06:00,2022-01-23 00:01:00-06:00 310,4994,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 53,5,0,0,0,0,2022-01-24 00:01:00-06:00,2022-01-24 00:01:00-06:00 324,4397,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 60,5,0,0,0,0,2022-01-25 00:01:00-06:00,2022-01-25 00:01:00-06:00 338,5242,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 67,5,0,0,0,0,2022-01-26 00:01:00-06:00,2022-01-26 00:01:00-06:00 352,4915,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 74,5,0,0,0,0,2022-01-27 00:01:00-06:00,2022-01-27 00:01:00-06:00 366,4937,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 81,5,0,0,0,0,2022-01-28 00:01:00-06:00,2022-01-28 00:01:00-06:00 380,5096,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 88,5,0,0,0,0,2022-01-29 00:01:00-06:00,2022-01-29 00:01:00-06:00 394,5139,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 95,5,0,0,0,0,2022-01-30 00:01:00-06:00,2022-01-30 00:01:00-06:00 408,5434,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 102,5,0,0,0,0,2022-01-31 00:01:00-06:00,2022-01-31 00:01:00-06:00 422,5212,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 109,5,0,0,0,0,2022-02-01 00:01:00-06:00,2022-02-01 00:01:00-06:00 436,5144,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 116,5,0,0,0,0,2022-02-02 00:01:00-06:00,2022-02-02 00:01:00-06:00 450,4229,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 123,5,0,0,0,0,2022-02-03 00:01:00-06:00,2022-02-03 00:01:00-06:00 464,4760,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 130,5,0,0,0,0,2022-02-04 00:01:00-06:00,2022-02-04 00:01:00-06:00 478,4770,0.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 137,5,0,0,0,0,2022-02-05 00:01:00-06:00,2022-02-05 00:01:00-06:00 492,5171,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 144,5,0,0,0,0,2022-02-06 00:01:00-06:00,2022-02-06 00:01:00-06:00 650,4740,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 153,5,0,0,0,0,2022-02-10 00:01:00-06:00,2022-02-10 00:01:00-06:00 700,4923,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 160,5,0,0,0,0,2022-02-11 00:01:00-06:00,2022-02-11 00:01:00-06:00 750,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 167,5,0,0,0,0,2022-02-12 00:01:00-06:00,2022-02-12 00:01:00-06:00 800,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 174,5,0,0,0,0,2022-02-13 00:01:00-06:00,2022-02-13 00:01:00-06:00 850,4250,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 181,5,0,0,0,0,2022-02-14 00:01:00-06:00,2022-02-14 00:01:00-06:00 900,4668,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 188,5,0,0,0,0,2022-02-15 00:01:00-06:00,2022-02-15 00:01:00-06:00 950,4638,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 195,5,0,0,0,0,2022-02-16 00:01:00-06:00,2022-02-16 00:01:00-06:00 1000,5111,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 202,5,0,0,0,0,2022-02-17 00:01:00-06:00,2022-02-17 00:01:00-06:00 1050,3788,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 209,5,0,0,0,0,2022-02-18 00:01:00-06:00,2022-02-18 00:01:00-06:00 1100,5291,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 216,5,0,0,0,0,2022-02-19 00:01:00-06:00,2022-02-19 00:01:00-06:00 1150,4563,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 223,5,0,0,0,0,2022-02-20 00:01:00-06:00,2022-02-20 00:01:00-06:00 1200,4649,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 230,5,0,0,0,0,2022-02-21 00:01:00-06:00,2022-02-21 00:01:00-06:00 1250,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 237,5,0,0,0,0,2022-02-22 00:01:00-06:00,2022-02-22 00:01:00-06:00 1300,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 244,5,0,0,0,0,2022-02-23 00:01:00-06:00,2022-02-23 00:01:00-06:00 1350,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 251,5,0,0,0,0,2022-02-24 00:01:00-06:00,2022-02-24 00:01:00-06:00 1400,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 258,5,0,0,0,0,2022-02-25 00:01:00-06:00,2022-02-25 00:01:00-06:00 1450,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 265,5,0,0,0,0,2022-02-26 00:01:00-06:00,2022-02-26 00:01:00-06:00 1500,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 272,5,0,0,0,0,2022-02-27 00:01:00-06:00,2022-02-27 00:01:00-06:00 1550,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 279,5,0,0,0,0,2022-02-28 00:01:00-06:00,2022-02-28 00:01:00-06:00 1600,254,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 286,5,0,0,0,0,2022-03-01 00:01:00-06:00,2022-03-01 00:01:00-06:00 1650,203,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 293,5,0,0,0,0,2022-03-02 00:01:00-06:00,2022-03-02 00:01:00-06:00 1700,259,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 300,5,0,0,0,0,2022-03-03 00:01:00-06:00,2022-03-03 00:01:00-06:00 1750,255,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 307,5,0,0,0,0,2022-03-04 00:01:00-06:00,2022-03-04 00:01:00-06:00 1800,259,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 314,5,0,0,0,0,2022-03-05 00:01:00-06:00,2022-03-05 00:01:00-06:00 1850,284,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 321,5,0,0,0,0,2022-03-06 00:01:00-06:00,2022-03-06 00:01:00-06:00 1900,258,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 328,5,0,0,0,0,2022-03-07 00:01:00-06:00,2022-03-07 00:01:00-06:00 1950,284,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 335,5,0,0,0,0,2022-03-08 00:01:00-06:00,2022-03-08 00:01:00-06:00 2000,220,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 342,5,0,0,0,0,2022-03-09 00:01:00-06:00,2022-03-09 00:01:00-06:00 2050,197,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 349,5,0,0,0,0,2022-03-10 00:01:00-06:00,2022-03-10 00:01:00-06:00 2100,263,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 356,5,0,0,0,0,2022-03-11 00:01:00-06:00,2022-03-11 00:01:00-06:00 2150,283,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 363,5,0,0,0,0,2022-03-12 00:01:00-06:00,2022-03-12 00:01:00-06:00 2200,276,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 370,5,0,0,0,0,2022-03-13 00:01:00-06:00,2022-03-13 00:01:00-06:00 2250,212,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 377,5,0,0,0,0,2022-03-14 00:01:00-05:00,2022-03-14 00:01:00-05:00 2300,255,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 384,5,0,0,0,0,2022-03-15 00:01:00-05:00,2022-03-15 00:01:00-05:00 2350,212,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 391,5,0,0,0,0,2022-03-16 00:01:00-05:00,2022-03-16 00:01:00-05:00 2400,231,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 398,5,0,0,0,0,2022-03-17 00:01:00-05:00,2022-03-17 00:01:00-05:00 2450,209,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 405,5,0,0,0,0,2022-03-18 00:01:00-05:00,2022-03-18 00:01:00-05:00 2500,253,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 412,5,0,0,0,0,2022-03-19 00:01:00-05:00,2022-03-19 00:01:00-05:00 2550,233,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 419,5,0,0,0,0,2022-03-20 00:01:00-05:00,2022-03-20 00:01:00-05:00 2600,1661,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 426,5,0,0,0,0,2022-03-21 00:01:00-05:00,2022-03-21 00:01:00-05:00 2650,1940,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 433,5,0,0,0,0,2022-03-22 00:01:00-05:00,2022-03-22 00:01:00-05:00 2700,1177,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 440,5,0,0,0,0,2022-03-23 00:01:00-05:00,2022-03-23 00:01:00-05:00 2750,1537,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 447,5,0,0,0,0,2022-03-24 00:01:00-05:00,2022-03-24 00:01:00-05:00 2800,1908,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 454,5,0,0,0,0,2022-03-25 00:01:00-05:00,2022-03-25 00:01:00-05:00 2850,1290,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 461,5,0,0,0,0,2022-03-26 00:01:00-05:00,2022-03-26 00:01:00-05:00 2900,1286,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 468,5,0,0,0,0,2022-03-27 00:01:00-05:00,2022-03-27 00:01:00-05:00 2950,1944,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 475,5,0,0,0,0,2022-03-28 00:01:00-05:00,2022-03-28 00:01:00-05:00 3000,1365,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 482,5,0,0,0,0,2022-03-29 00:01:00-05:00,2022-03-29 00:01:00-05:00 3050,1252,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 489,5,0,0,0,0,2022-03-30 00:01:00-05:00,2022-03-30 00:01:00-05:00 3100,2010,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 496,5,0,0,0,0,2022-03-31 00:01:00-05:00,2022-03-31 00:01:00-05:00 3150,1998,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 503,5,0,0,0,0,2022-04-01 00:01:00-05:00,2022-04-01 00:01:00-05:00 3200,1342,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 510,5,0,0,0,0,2022-04-02 00:01:00-05:00,2022-04-02 00:01:00-05:00 3250,2158,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 517,5,0,0,0,0,2022-04-03 00:01:00-05:00,2022-04-03 00:01:00-05:00 3300,2033,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 524,5,0,0,0,0,2022-04-04 00:01:00-05:00,2022-04-04 00:01:00-05:00 3350,1935,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 531,5,0,0,0,0,2022-04-05 00:01:00-05:00,2022-04-05 00:01:00-05:00 3400,1860,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 538,5,0,0,0,0,2022-04-06 00:01:00-05:00,2022-04-06 00:01:00-05:00 3450,1279,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 545,5,0,0,0,0,2022-04-07 00:01:00-05:00,2022-04-07 00:01:00-05:00 3500,1340,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 552,5,0,0,0,0,2022-04-08 00:01:00-05:00,2022-04-08 00:01:00-05:00 3550,1746,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 559,5,0,0,0,0,2022-04-09 00:01:00-05:00,2022-04-09 00:01:00-05:00 3600,1312,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 566,5,0,0,0,0,2022-04-10 00:01:00-05:00,2022-04-10 00:01:00-05:00 3650,1802,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 573,5,0,0,0,0,2022-04-11 00:01:00-05:00,2022-04-11 00:01:00-05:00 3700,1997,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 580,5,0,0,0,0,2022-04-12 00:01:00-05:00,2022-04-12 00:01:00-05:00 3750,1657,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 587,5,0,0,0,0,2022-04-13 00:01:00-05:00,2022-04-13 00:01:00-05:00 3800,1684,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 594,5,0,0,0,0,2022-04-14 00:01:00-05:00,2022-04-14 00:01:00-05:00 3850,1811,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 601,5,0,0,0,0,2022-04-15 00:01:00-05:00,2022-04-15 00:01:00-05:00 3900,1959,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 608,5,0,0,0,0,2022-04-16 00:01:00-05:00,2022-04-16 00:01:00-05:00 3950,1501,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 615,5,0,0,0,0,2022-04-17 00:01:00-05:00,2022-04-17 00:01:00-05:00 4000,1434,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 622,5,0,0,0,0,2022-04-18 00:01:00-05:00,2022-04-18 00:01:00-05:00 4050,1286,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 629,5,0,0,0,0,2022-04-19 00:01:00-05:00,2022-04-19 00:01:00-05:00 4100,1598,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 636,5,0,0,0,0,2022-04-20 00:01:00-05:00,2022-04-20 00:01:00-05:00 4150,1747,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 643,5,0,0,0,0,2022-04-21 00:01:00-05:00,2022-04-21 00:01:00-05:00 4200,1254,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 650,5,0,0,0,0,2022-04-22 00:01:00-05:00,2022-04-22 00:01:00-05:00 4250,2049,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 657,5,0,0,0,0,2022-04-23 00:01:00-05:00,2022-04-23 00:01:00-05:00 4300,1905,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 664,5,0,0,0,0,2022-04-24 00:01:00-05:00,2022-04-24 00:01:00-05:00 4350,1423,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 671,5,0,0,0,0,2022-04-25 00:01:00-05:00,2022-04-25 00:01:00-05:00 4400,2151,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 678,5,0,0,0,0,2022-04-26 00:01:00-05:00,2022-04-26 00:01:00-05:00 4450,2005,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 685,5,0,0,0,0,2022-04-28 00:01:00-05:00,2022-04-28 00:01:00-05:00 4500,1831,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 692,5,0,0,0,0,2022-04-29 00:01:00-05:00,2022-04-29 00:01:00-05:00 4550,1820,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 699,5,0,0,0,0,2022-04-30 00:01:00-05:00,2022-04-30 00:01:00-05:00 4600,1827,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 706,5,0,0,0,0,2022-05-01 00:01:00-05:00,2022-05-01 00:01:00-05:00 4650,1891,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 713,5,0,0,0,0,2022-05-02 00:01:00-05:00,2022-05-02 00:01:00-05:00 4700,1265,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 720,5,0,0,0,0,2022-05-03 00:01:00-05:00,2022-05-03 00:01:00-05:00 4750,2047,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 727,5,0,0,0,0,2022-05-04 00:01:00-05:00,2022-05-04 00:01:00-05:00 4800,1646,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 734,5,0,0,0,0,2022-05-05 00:01:00-05:00,2022-05-05 00:01:00-05:00 4850,1940,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 741,5,0,0,0,0,2022-05-06 00:01:00-05:00,2022-05-06 00:01:00-05:00 4900,1831,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 748,5,0,0,0,0,2022-05-07 00:01:00-05:00,2022-05-07 00:01:00-05:00 4950,1217,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 755,5,0,0,0,0,2022-05-08 00:01:00-05:00,2022-05-08 00:01:00-05:00 5000,1623,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 762,5,0,0,0,0,2022-05-09 00:01:00-05:00,2022-05-09 00:01:00-05:00 5050,1183,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 769,5,0,0,0,0,2022-05-10 00:01:00-05:00,2022-05-10 00:01:00-05:00 5100,1702,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 776,5,0,0,0,0,2022-05-11 00:01:00-05:00,2022-05-11 00:01:00-05:00 5150,1623,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 783,5,0,0,0,0,2022-05-12 00:01:00-05:00,2022-05-12 00:01:00-05:00 5200,1328,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 790,5,0,0,0,0,2022-05-13 00:01:00-05:00,2022-05-13 00:01:00-05:00 5250,1530,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 797,5,0,0,0,0,2022-05-14 00:01:00-05:00,2022-05-14 00:01:00-05:00 5300,1792,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 804,5,0,0,0,0,2022-05-15 00:01:00-05:00,2022-05-15 00:01:00-05:00 5350,1989,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 811,5,0,0,0,0,2022-05-16 00:01:00-05:00,2022-05-16 00:01:00-05:00 5400,1723,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 818,5,0,0,0,0,2022-05-17 00:01:00-05:00,2022-05-17 00:01:00-05:00 5450,1740,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 825,5,0,0,0,0,2022-05-18 00:01:00-05:00,2022-05-18 00:01:00-05:00 5500,1822,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 832,5,0,0,0,0,2022-05-19 00:01:00-05:00,2022-05-19 00:01:00-05:00 5550,1812,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 839,5,0,0,0,0,2022-05-20 00:01:00-05:00,2022-05-20 00:01:00-05:00 5600,1310,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 846,5,0,0,0,0,2022-05-21 00:01:00-05:00,2022-05-21 00:01:00-05:00 5650,1574,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 853,5,0,0,0,0,2022-05-22 00:01:00-05:00,2022-05-22 00:01:00-05:00 5700,1371,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 860,5,0,0,0,0,2022-05-23 00:01:00-05:00,2022-05-23 00:01:00-05:00 5750,1822,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 867,5,0,0,0,0,2022-05-24 00:01:00-05:00,2022-05-24 00:01:00-05:00 5800,1375,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 874,5,0,0,0,0,2022-05-25 00:01:00-05:00,2022-05-25 00:01:00-05:00 5850,1737,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 881,5,0,0,0,0,2022-05-26 00:01:00-05:00,2022-05-26 00:01:00-05:00 5900,1407,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 888,5,0,0,0,0,2022-05-27 00:01:00-05:00,2022-05-27 00:01:00-05:00 5950,2086,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 895,5,0,0,0,0,2022-05-28 00:01:00-05:00,2022-05-28 00:01:00-05:00 6000,1937,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 902,5,0,0,0,0,2022-05-29 00:01:00-05:00,2022-05-29 00:01:00-05:00 6050,1145,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 909,5,0,0,0,0,2022-05-30 00:01:00-05:00,2022-05-30 00:01:00-05:00 6100,1588,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 916,5,0,0,0,0,2022-05-31 00:01:00-05:00,2022-05-31 00:01:00-05:00 6150,1775,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 923,5,0,0,0,0,2022-06-01 00:01:00-05:00,2022-06-01 00:01:00-05:00 6200,1083,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 930,5,0,0,0,0,2022-06-02 00:01:00-05:00,2022-06-02 00:01:00-05:00 6250,1914,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 937,5,0,0,0,0,2022-06-03 00:01:00-05:00,2022-06-03 00:01:00-05:00 6300,1789,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 944,5,0,0,0,0,2022-06-04 00:01:00-05:00,2022-06-04 00:01:00-05:00 6350,1231,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 951,5,0,0,0,0,2022-06-05 00:01:00-05:00,2022-06-05 00:01:00-05:00 6400,1848,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 958,5,0,0,0,0,2022-06-06 00:01:00-05:00,2022-06-06 00:01:00-05:00 6450,1907,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 965,5,0,0,0,0,2022-06-07 00:01:00-05:00,2022-06-07 00:01:00-05:00 6500,2039,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 972,5,0,0,0,0,2022-06-08 00:01:00-05:00,2022-06-08 00:01:00-05:00 6550,1972,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 979,5,0,0,0,0,2022-06-09 00:01:00-05:00,2022-06-09 00:01:00-05:00 6600,1816,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 986,5,0,0,0,0,2022-06-10 00:01:00-05:00,2022-06-10 00:01:00-05:00 6650,1983,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 993,5,0,0,0,0,2022-06-11 00:01:00-05:00,2022-06-11 00:01:00-05:00 6700,1695,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1000,5,0,0,0,0,2022-06-12 00:01:00-05:00,2022-06-12 00:01:00-05:00 6750,1762,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1007,5,0,0,0,0,2022-06-13 00:01:00-05:00,2022-06-13 00:01:00-05:00 6800,1828,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1014,5,0,0,0,0,2022-06-14 00:01:00-05:00,2022-06-14 00:01:00-05:00 6850,1911,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1021,5,0,0,0,0,2022-06-15 00:01:00-05:00,2022-06-15 00:01:00-05:00 6900,1690,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1028,5,0,0,0,0,2022-06-16 00:01:00-05:00,2022-06-16 00:01:00-05:00 6950,1895,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1035,5,0,0,0,0,2022-06-17 00:01:00-05:00,2022-06-17 00:01:00-05:00 7000,2086,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1042,5,0,0,0,0,2022-06-23 00:01:00-05:00,2022-06-23 00:01:00-05:00 7050,1775,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1049,5,0,0,0,0,2022-06-24 00:01:00-05:00,2022-06-24 00:01:00-05:00 7100,1992,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1056,5,0,0,0,0,2022-06-25 00:01:00-05:00,2022-06-25 00:01:00-05:00 7150,1435,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1063,5,0,0,0,0,2022-06-26 00:01:00-05:00,2022-06-26 00:01:00-05:00 7200,1273,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1070,5,0,0,0,0,2022-06-27 00:01:00-05:00,2022-06-27 00:01:00-05:00 7250,2321,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1077,5,0,0,0,0,2022-06-28 00:01:00-05:00,2022-06-28 00:01:00-05:00 7300,1666,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1084,5,0,0,0,0,2022-06-29 00:01:00-05:00,2022-06-29 00:01:00-05:00 7350,1598,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1091,5,0,0,0,0,2022-06-30 00:01:00-05:00,2022-06-30 00:01:00-05:00 7400,2090,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1098,5,0,0,0,0,2022-07-01 00:01:00-05:00,2022-07-01 00:01:00-05:00 7450,2066,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1105,5,0,0,0,0,2022-07-02 00:01:00-05:00,2022-07-02 00:01:00-05:00 7500,1253,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1112,5,0,0,0,0,2022-07-03 00:01:00-05:00,2022-07-03 00:01:00-05:00 7550,1367,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1119,5,0,0,0,0,2022-07-04 00:01:00-05:00,2022-07-04 00:01:00-05:00 7600,1737,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1126,5,0,0,0,0,2022-07-05 00:01:00-05:00,2022-07-05 00:01:00-05:00 7650,2065,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1133,5,0,0,0,0,2022-07-06 00:01:00-05:00,2022-07-06 00:01:00-05:00 7700,2065,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1140,5,0,0,0,0,2022-07-07 00:01:00-05:00,2022-07-07 00:01:00-05:00 7750,1548,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1147,5,0,0,0,0,2022-07-08 00:01:00-05:00,2022-07-08 00:01:00-05:00 7800,1849,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1154,5,0,0,0,0,2022-07-09 00:01:00-05:00,2022-07-09 00:01:00-05:00 7850,1175,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1161,5,0,0,0,0,2022-07-10 00:01:00-05:00,2022-07-10 00:01:00-05:00 7900,1430,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1168,5,0,0,0,0,2022-07-11 00:01:00-05:00,2022-07-11 00:01:00-05:00 7950,1716,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1175,5,0,0,0,0,2022-07-12 00:01:00-05:00,2022-07-12 00:01:00-05:00 8000,1854,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1182,5,0,0,0,0,2022-07-13 00:01:00-05:00,2022-07-13 00:01:00-05:00 8050,1338,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1189,5,0,0,0,0,2022-07-14 00:01:00-05:00,2022-07-14 00:01:00-05:00 8100,1474,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1196,5,0,0,0,0,2022-07-15 00:01:00-05:00,2022-07-15 00:01:00-05:00 8150,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1203,5,0,0,0,0,2022-07-16 00:01:00-05:00,2022-07-16 00:01:00-05:00 8200,1288,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1210,5,0,0,0,0,2022-07-17 00:01:00-05:00,2022-07-17 00:01:00-05:00 8250,1784,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1217,5,0,0,0,0,2022-07-18 00:01:00-05:00,2022-07-18 00:01:00-05:00 8300,1981,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1224,5,0,0,0,0,2022-07-19 00:01:00-05:00,2022-07-19 00:01:00-05:00 8350,1332,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1231,5,0,0,0,0,2022-07-20 00:01:00-05:00,2022-07-20 00:01:00-05:00 8400,1680,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1238,5,0,0,0,0,2022-07-21 00:01:00-05:00,2022-07-21 00:01:00-05:00 8450,1384,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1245,5,0,0,0,0,2022-07-22 00:01:00-05:00,2022-07-22 00:01:00-05:00 8500,1929,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1252,5,0,0,0,0,2022-07-23 00:01:00-05:00,2022-07-23 00:01:00-05:00 8550,1994,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1259,5,0,0,0,0,2022-07-24 00:01:00-05:00,2022-07-24 00:01:00-05:00 8600,1976,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1266,5,0,0,0,0,2022-07-25 00:01:00-05:00,2022-07-25 00:01:00-05:00 8650,1719,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1273,5,0,0,0,0,2022-07-26 00:01:00-05:00,2022-07-26 00:01:00-05:00 8700,1752,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1280,5,0,0,0,0,2022-07-27 00:01:00-05:00,2022-07-27 00:01:00-05:00 8750,1264,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1287,5,0,0,0,0,2022-07-28 00:01:00-05:00,2022-07-28 00:01:00-05:00 8800,1649,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1294,5,0,0,0,0,2022-07-29 00:01:00-05:00,2022-07-29 00:01:00-05:00 8850,1656,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1301,5,0,0,0,0,2022-07-30 00:01:00-05:00,2022-07-30 00:01:00-05:00 8900,1283,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1308,5,0,0,0,0,2022-07-31 00:01:00-05:00,2022-07-31 00:01:00-05:00 8950,1242,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1315,5,0,0,0,0,2022-08-01 00:01:00-05:00,2022-08-01 00:01:00-05:00 9000,1586,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1322,5,0,0,0,0,2022-08-02 00:01:00-05:00,2022-08-02 00:01:00-05:00 9050,1396,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1329,5,0,0,0,0,2022-08-03 00:01:00-05:00,2022-08-03 00:01:00-05:00 9100,2035,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1336,5,0,0,0,0,2022-08-04 00:01:00-05:00,2022-08-04 00:01:00-05:00 9150,1774,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1343,5,0,0,0,0,2022-08-05 00:01:00-05:00,2022-08-05 00:01:00-05:00 9200,1878,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1350,5,0,0,0,0,2022-08-06 00:01:00-05:00,2022-08-06 00:01:00-05:00 9250,1922,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1357,5,0,0,0,0,2022-08-07 00:01:00-05:00,2022-08-07 00:01:00-05:00 9300,2277,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1364,5,0,0,0,0,2022-08-08 00:01:00-05:00,2022-08-08 00:01:00-05:00 9350,1589,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1371,5,0,0,0,0,2022-08-09 00:01:00-05:00,2022-08-09 00:01:00-05:00 9400,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1378,5,0,0,0,0,2022-08-10 00:01:00-05:00,2022-08-10 00:01:00-05:00 9450,1689,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1385,5,0,0,0,0,2022-08-11 00:01:00-05:00,2022-08-11 00:01:00-05:00 9500,1995,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1392,5,0,0,0,0,2022-08-12 00:01:00-05:00,2022-08-12 00:01:00-05:00 9514,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1399,5,0,0,0,0,2022-08-13 00:01:00-05:00,2022-08-13 00:01:00-05:00 9564,1247,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1406,5,0,0,0,0,2022-08-14 00:01:00-05:00,2022-08-14 00:01:00-05:00 9614,1614,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1413,5,0,0,0,0,2022-08-15 00:01:00-05:00,2022-08-15 00:01:00-05:00 9664,1489,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1420,5,0,0,0,0,2022-08-16 00:01:00-05:00,2022-08-16 00:01:00-05:00 9714,1330,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1427,5,0,0,0,0,2022-08-17 00:01:00-05:00,2022-08-17 00:01:00-05:00 9764,1289,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1434,5,0,0,0,0,2022-08-18 00:01:00-05:00,2022-08-18 00:01:00-05:00 9814,1877,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1441,5,0,0,0,0,2022-08-19 00:01:00-05:00,2022-08-19 00:01:00-05:00 9864,1271,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1448,5,0,0,0,0,2022-08-20 00:01:00-05:00,2022-08-20 00:01:00-05:00 9923,1753,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1455,5,0,0,0,0,2022-08-21 00:01:00-05:00,2022-08-21 00:01:00-05:00 9974,1372,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1463,5,0,0,0,0,2022-08-22 00:01:00-05:00,2022-08-22 00:01:00-05:00 10025,1308,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1471,5,0,0,0,0,2022-08-23 00:01:00-05:00,2022-08-23 00:01:00-05:00 10076,1240,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1479,5,0,0,0,0,2022-08-24 00:01:00-05:00,2022-08-24 00:01:00-05:00 10127,1837,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1487,5,0,0,0,0,2022-08-25 00:01:00-05:00,2022-08-25 00:01:00-05:00 10178,1422,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1495,5,0,0,0,0,2022-08-26 00:01:00-05:00,2022-08-26 00:01:00-05:00 10229,1281,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1503,5,0,0,0,0,2022-08-27 00:01:00-05:00,2022-08-27 00:01:00-05:00 10280,1449,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1511,5,0,0,0,0,2022-08-28 00:01:00-05:00,2022-08-28 00:01:00-05:00 10331,1258,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1519,5,0,0,0,0,2022-08-29 00:01:00-05:00,2022-08-29 00:01:00-05:00 10382,1521,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1527,5,0,0,0,0,2022-08-30 00:01:00-05:00,2022-08-30 00:01:00-05:00 10433,1794,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1535,5,0,0,0,0,2022-08-31 00:01:00-05:00,2022-08-31 00:01:00-05:00 10484,1020,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1543,5,0,0,0,0,2022-09-01 00:01:00-05:00,2022-09-01 00:01:00-05:00 10535,1141,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1551,5,0,0,0,0,2022-09-02 00:01:00-05:00,2022-09-02 00:01:00-05:00 10586,1060,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1559,5,0,0,0,0,2022-09-03 00:01:00-05:00,2022-09-03 00:01:00-05:00 10637,1579,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1567,5,0,0,0,0,2022-09-04 00:01:00-05:00,2022-09-04 00:01:00-05:00 10688,961,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1575,5,0,0,0,0,2022-09-05 00:01:00-05:00,2022-09-05 00:01:00-05:00 10739,1251,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1583,5,0,0,0,0,2022-09-06 00:01:00-05:00,2022-09-06 00:01:00-05:00 10790,1748,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1591,5,0,0,0,0,2022-09-07 00:01:00-05:00,2022-09-07 00:01:00-05:00 10841,1475,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1599,5,0,0,0,0,2022-09-08 00:01:00-05:00,2022-09-08 00:01:00-05:00 10892,1229,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1607,5,0,0,0,0,2022-09-09 00:01:00-05:00,2022-09-09 00:01:00-05:00 10943,1082,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1615,5,0,0,0,0,2022-09-10 00:01:00-05:00,2022-09-10 00:01:00-05:00 10994,1768,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1623,5,0,0,0,0,2022-09-11 00:01:00-05:00,2022-09-11 00:01:00-05:00 11045,1111,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1631,5,0,0,0,0,2022-09-12 00:01:00-05:00,2022-09-12 00:01:00-05:00 11096,1221,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1639,5,0,0,0,0,2022-09-13 00:01:00-05:00,2022-09-13 00:01:00-05:00 11147,1649,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1647,5,0,0,0,0,2022-09-14 00:01:00-05:00,2022-09-14 00:01:00-05:00 11198,1565,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1655,5,0,0,0,0,2022-09-15 00:01:00-05:00,2022-09-15 00:01:00-05:00 11249,1492,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1663,5,0,0,0,0,2022-09-16 00:01:00-05:00,2022-09-16 00:01:00-05:00 11300,1215,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1671,5,0,0,0,0,2022-09-17 00:01:00-05:00,2022-09-17 00:01:00-05:00 11351,990,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1679,5,0,0,0,0,2022-09-18 00:01:00-05:00,2022-09-18 00:01:00-05:00 11402,1220,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1687,5,0,0,0,0,2022-09-19 00:01:00-05:00,2022-09-19 00:01:00-05:00 11453,1737,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1695,5,0,0,0,0,2022-09-20 00:01:00-05:00,2022-09-20 00:01:00-05:00 11504,1786,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1703,5,0,0,0,0,2022-09-21 00:01:00-05:00,2022-09-21 00:01:00-05:00 11555,1658,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1711,5,0,0,0,0,2022-09-22 00:01:00-05:00,2022-09-22 00:01:00-05:00 11606,1580,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1719,5,0,0,0,0,2022-09-23 00:01:00-05:00,2022-09-23 00:01:00-05:00 11657,1003,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1727,5,0,0,0,0,2022-09-24 00:01:00-05:00,2022-09-24 00:01:00-05:00 11708,1630,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1735,5,0,0,0,0,2022-09-25 00:01:00-05:00,2022-09-25 00:01:00-05:00 11759,1535,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1743,5,0,0,0,0,2022-09-26 00:01:00-05:00,2022-09-26 00:01:00-05:00 11810,1242,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1751,5,0,0,0,0,2022-09-27 00:01:00-05:00,2022-09-27 00:01:00-05:00 11861,1601,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1759,5,0,0,0,0,2022-09-28 00:01:00-05:00,2022-09-28 00:01:00-05:00 11912,1831,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1767,5,0,0,0,0,2022-09-29 00:01:00-05:00,2022-09-29 00:01:00-05:00 11963,1830,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1775,5,0,0,0,0,2022-09-30 00:01:00-05:00,2022-09-30 00:01:00-05:00 12014,1819,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1783,5,0,0,0,0,2022-10-01 00:01:00-05:00,2022-10-01 00:01:00-05:00 12065,1533,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1791,5,0,0,0,0,2022-10-02 00:01:00-05:00,2022-10-02 00:01:00-05:00 12116,1663,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1799,5,0,0,0,0,2022-10-03 00:01:00-05:00,2022-10-03 00:01:00-05:00 12167,1513,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1807,5,0,0,0,0,2022-10-04 00:01:00-05:00,2022-10-04 00:01:00-05:00 12218,1235,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1815,5,0,0,0,0,2022-10-05 00:01:00-05:00,2022-10-05 00:01:00-05:00 12269,1385,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1823,5,0,0,0,0,2022-10-06 00:01:00-05:00,2022-10-06 00:01:00-05:00 12320,1521,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1831,5,0,0,0,0,2022-10-07 00:01:00-05:00,2022-10-07 00:01:00-05:00 12371,1613,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1839,5,0,0,0,0,2022-10-08 00:01:00-05:00,2022-10-08 00:01:00-05:00 12422,1282,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1847,5,0,0,0,0,2022-10-09 00:01:00-05:00,2022-10-09 00:01:00-05:00 12473,1174,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1855,5,0,0,0,0,2022-10-10 00:01:00-05:00,2022-10-10 00:01:00-05:00 12524,1511,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1863,5,0,0,0,0,2022-10-11 00:01:00-05:00,2022-10-11 00:01:00-05:00 12575,1510,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1871,5,0,0,0,0,2022-10-12 00:01:00-05:00,2022-10-12 00:01:00-05:00 12626,1110,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1879,5,0,0,0,0,2022-10-13 00:01:00-05:00,2022-10-13 00:01:00-05:00 12677,1107,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1887,5,0,0,0,0,2022-10-14 00:01:00-05:00,2022-10-14 00:01:00-05:00 12728,1129,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1895,5,0,0,0,0,2022-10-15 00:01:00-05:00,2022-10-15 00:01:00-05:00 12779,1194,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1903,5,0,0,0,0,2022-10-16 00:01:00-05:00,2022-10-16 00:01:00-05:00 12830,1028,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1911,5,0,0,0,0,2022-10-17 00:01:00-05:00,2022-10-17 00:01:00-05:00 12881,1036,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1919,5,0,0,0,0,2022-10-18 00:01:00-05:00,2022-10-18 00:01:00-05:00 12932,1160,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1927,5,0,0,0,0,2022-10-19 00:01:00-05:00,2022-10-19 00:01:00-05:00 12983,1488,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1935,5,0,0,0,0,2022-10-20 00:01:00-05:00,2022-10-20 00:01:00-05:00 13034,1693,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1943,5,0,0,0,0,2022-10-21 00:01:00-05:00,2022-10-21 00:01:00-05:00 13085,1658,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1951,5,0,0,0,0,2022-10-22 00:01:00-05:00,2022-10-22 00:01:00-05:00 13136,1130,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1959,5,0,0,0,0,2022-10-23 00:01:00-05:00,2022-10-23 00:01:00-05:00 13187,1623,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1967,5,0,0,0,0,2022-10-24 00:01:00-05:00,2022-10-24 00:01:00-05:00 13238,1528,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1975,5,0,0,0,0,2022-10-25 00:01:00-05:00,2022-10-25 00:01:00-05:00 13289,1714,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1983,5,0,0,0,0,2022-10-26 00:01:00-05:00,2022-10-26 00:01:00-05:00 13340,1441,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1991,5,0,0,0,0,2022-10-28 00:01:00-05:00,2022-10-28 00:01:00-05:00 13391,1478,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 1999,5,0,0,0,0,2022-10-29 00:01:00-05:00,2022-10-29 00:01:00-05:00 13442,1346,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2007,5,0,0,0,0,2022-10-30 00:01:00-05:00,2022-10-30 00:01:00-05:00 13493,1568,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2015,5,0,0,0,0,2022-10-31 00:01:00-05:00,2022-10-31 00:01:00-05:00 13544,1076,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2023,5,0,0,0,0,2022-11-01 00:01:00-05:00,2022-11-01 00:01:00-05:00 13595,1462,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2031,5,0,0,0,0,2022-11-02 00:01:00-05:00,2022-11-02 00:01:00-05:00 13646,1365,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2039,5,0,0,0,0,2022-11-03 00:01:00-05:00,2022-11-03 00:01:00-05:00 13697,1491,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2047,5,0,0,0,0,2022-11-04 00:01:00-05:00,2022-11-04 00:01:00-05:00 13748,1486,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2055,5,0,0,0,0,2022-11-05 00:01:00-05:00,2022-11-05 00:01:00-05:00 13799,1576,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2063,5,0,0,0,0,2022-11-06 00:01:00-05:00,2022-11-06 00:01:00-05:00 13850,1121,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2071,5,0,0,0,0,2022-11-07 00:01:00-06:00,2022-11-07 00:01:00-06:00 13901,0.0,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2079,5,0,0,0,0,2022-11-08 00:01:00-06:00,2022-11-08 00:01:00-06:00 13952,1401,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2087,5,0,0,0,0,2022-11-09 00:01:00-06:00,2022-11-09 00:01:00-06:00 14003,1099,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2095,5,0,0,0,0,2022-11-10 00:01:00-06:00,2022-11-10 00:01:00-06:00 14054,1134,150.0,0 5,valNightly,reco,day,0 6,ops,stats,CPU 2103,5,0,0,0,0,2022-11-11 00:01:00-06:00,2022-11-11 00:01:00-06:00 ... 783 more lines ...
2935	31 Jan 2025	Pavel Murat	Forum	converting non-MIDAS slow control data into MIDAS history format ?
I think I found an answer to my question: a user-controlled event header does have a time stamp: https://daq00.triumf.ca/MidasWiki/index.php/Event_Structure#Event_Header -- apologies for the spam, regards, Pasha
2934	30 Jan 2025	Pavel Murat	Forum	converting non-MIDAS slow control data into MIDAS history format ?
Dear MIDAS experts, I have a time series of slow control measurements in an ASCII format - data records in a format (run_number, time, temperature, voltage1, ..., voltageN), and, if possible, would like to convert them into a MIDAS history format. Making MIDAS events out of that data is easy, but is it possible to preserve the time stamps? - Logically, this boils down to whether it is possible to have the event time set by a user frontend -- as always - many thanks, regards, Pasha
2933	20 Jan 2025	Ben Smith	Forum	mjsonrpc: how to increase the max allowed length of the callback response ?
> I'm using MIDAS javascript interface (mjsonrpc) to communicate with a frontend from a custom web page > and observe that the if the frontend's response exceeds certain number of bytes, it is always truncated. > > MIDAS C/C++ RPC interface allows users to specify the max response length : > > https://daq00.triumf.ca/MidasWiki/index.php/Remote_Procedure_Calls_(RPC)#C++_2 > > How would one do the same from with mjsonrpc ? I just documented the max_reply_length (javascript) and max_len (python) parameters on that page. Both are optional and default to 1024 bytes. I also added a link to the full mjsonrpc schema https://daq00.triumf.ca/MidasWiki/index.php/Mjsonrpc#Schema_(List_of_all_RPC_methods) . You can also find the auto-generated schema on any midas installation by going to the "Help" webpage served by mhttpd and clicking the "JSON-RPC schema" > "text table format" link.
2932	18 Jan 2025	Pavel Murat	Forum	mjsonrpc: how to increase the max allowed length of the callback response ?
Dear MIDAS experts, I'm using MIDAS javascript interface (mjsonrpc) to communicate with a frontend from a custom web page and observe that the if the frontend's response exceeds certain number of bytes, it is always truncated. MIDAS C/C++ RPC interface allows users to specify the max response length : https://daq00.triumf.ca/MidasWiki/index.php/Remote_Procedure_Calls_(RPC)#C++_2 How would one do the same from with mjsonrpc ? -- many thanks, regards, Pasha
2931	09 Jan 2025	Stefan Ritt	Suggestion	improved find_package behaviour for Midas
After some iterations, we merged the branch with the new build scheme. Now you can compile any midas program as described at https://bitbucket.org/tmidas/midas/pull-requests/48?link_source=email A default CMakeLists.txt file can look like this: cmake_minimum_required(VERSION 3.17) project(example) find_package(Midas REQUIRED PATHS $ENV{MIDASSYS}) add_executable(example example.cpp) target_link_libraries(example midas::midas) Which is much simpler than what we had before. The trick now is that the find_package() retrieves all include and link files automatically. There are different targets: midas::midas - normal midas program midas::midas-shared - normal midas programs using the shared midas library midas::mfe - old style mfe.cxx frontend midas::mfed - newer style frontend using mfed.cxx midas::mscb - programs using MSCB system midas::drivers - slow control program using any of the standard midas drivers We are not absolutely sure that all midas installations will work that way, so far we have tested it on RH8, MacOSX with cmake version 3.29.5. Comments and bug reports are welcome as usual. Alex and Stefan
2930	06 Jan 2025	Alexandr Kozlinskiy	Suggestion	improved find_package behaviour for Midas
currently to link Midas to project one has to do several steps in cmake script: - do `find_package` - get Midas location from MIDASSYS, or from MIDAS_LIBRARY_DIRS - set MIDAS_INCLUDE_DIRS, MIDAS_LIBRARY_DIRS and MIDAS_LIBRARIES to your target - add sources from Midas for mfe, drivers, etc. in general cmake already can to all of this automatically, and the only lines you would need are: - do `find_package(Midas ... PATHS ~/midas_install_location)` - and do `target_link_libraries(... midas::mfe)` (and all include dirs, libs, and deps are propagated automatically) see PR https://bitbucket.org/tmidas/midas/pull-requests/48 - nothing should break with current setups - if you want to try new `midas::` targets, try to link e.g. `midas::mfed` to your frontend
2929	05 Jan 2025	Stefan Ritt	Forum	time ordering of run transition calls to TMFeEquipment things
Hi Pavel, have you looked into cm_set_transition_sequence() which let's you define the sequence number for every midas client. You give any number between 1 and 1000 (default is 500 for frontends I believe). The default value of 500 is defined in mfe.cxx:2641 where you have 500 for all four transitions, but it can be overwritten in the frontend_init function via cm_set_transition_sequence(). Since you have separate values for the start and stop transition, you can get the different sequencing for both transitions as you need. Like set all type A to 400, type B to 600 for TR_START, and set type A to 600 and type B to 400 for TR_STOP. Since this works on the midas client level, it should also work for the tmfe.cxx framework. I'm however not sure if you have a similar default of 500 as in mfe.cxx:2641. But K.O. should know. Best, Stefan
2928	02 Jan 2025	Pavel Murat	Forum	time ordering of run transition calls to TMFeEquipment things
Hi K.O., your clarification is much appreciated! " > I am not sure what you are trying to do. It is always easier to suggest a solution to a specific problem. I think, I owe you an explanation :) : Consider ~ 40 nodes with two FPGAs (PCIE cards) per node, talking to the detector hardware. One of those FPGAs, in addition to reading the data, performs the global timing synchronization. The high-bandwidth data readout is not controlled by MIDAS, so all frontends perform only 'slow control'-type functions. In MIDAS language, an FPGA implements two different units of slow control equipment: one - configuring and controlling a single FPGA (equipment type A), and another one - synchronizing multiple FPGAs (equipment type B). On one of the nodes, unit A and unit B share the FPGA card, so they better be controlled by the same frontend. For one, I need to make sure that all type A equipment units, managed by multiple frontends, are initialized before the [single] type B unit which shares the frontend with the type A unit. And, of course, the end of a run transition has to be handled in the opposite order - type B unit shuts down first. As 'periodic' actions for all registered pieces of equipment are performed in the same loop [thread], registering the equipment in the needed order - first A, then B - should give a solution - thanks for making that clear. > > 1) "time ordering of run transitions" - of course midas transitions are ordered by transition sequence numbers > and the tmfe class provides methods to control this. ditto for the mfe.cxx frontends. > > 2) for one TMFrontend, the order of calling HandleBeginRun() is the order in which equipments were added to the > equipment using FeAddEquipment(). HandleEndRun() is called in reverse order. (I better check this). the ordering of the rpc handler calls in tmfe's tr_stop/tr_pause/tr_resume functions is ok. > > 3) to have multiple TMFrontends in one program would be unusual (mfe.cxx frontends completely do not support > this), but should work. Everything was coded to support this, but it was never tested in practice because we > cannot invent any useful use-case for it. HandleBeginRun() handlers are likely to be called in the frontends are > created. (I could check this and confirm it works, as long as you have a valid use-case for this configuration). agreed, I don't think there is a good use case for that, so no need to spend time checking. > > 4) Frontend X has EquipmentA and EquipmentB, you want EqA::HandleBeginRun() to be called at run transition 200 > and EqB::HandleBeginRun() to be called at run transition 400. > > This is not directly supported by mfe.cxx frontends (the begin_run() handler is a global function) and I did not > directly implement it in the TMFE frontend. > > But I think this would be a useful improvement. I will look into this. In the simplest case, registering the equipment units in the right order is definitely the answer. However a single FPGA can perform multiple logically independent tasks and thus represent multiple logical units of equipment. Those units however are not independent: they share the hardware (FPGA) and thus do depend on each other. Giving users a full control over the sequence in which those logical units execute their run transitions is quite likely to be needed, for example, to work around peculiarities of the custom-made kernel drivers. > > Likely I will add per-equipment data members fEqConfBeginRunSeqNo, fEqConfEndRunSeqno, etc. Value 0 would > unregister the corresponding run transition handler. This would cleanup the code quite a bit, a bunch > of RegisterTranstionXXX functions could go away. this also makes sense. -- thanks again, regards, Pasha > > K.O.
2927	01 Jan 2025	Konstantin Olchanski	Forum	time ordering of run transition calls to TMFeEquipment things
> I have a question about "tmfe approach" to implementing MIDAS frontends. If I read the code correctly, > within this approach it is the TMFeEquipment things, not the TMFrontend's themselves, > which handle the run transitions - the TMFrontend class that's correct and it is documented so in https://bitbucket.org/tmidas/midas/src/develop/tmfe.md > So how does a user control the sequence in which TMFeEquipment::HandleBeginRun functions of different > TMFeEquipment pieces are called at begin run? - there are two cases to consider: TMFeEquipment things > defined by the same TMFrontend and by different TMFrontend's. I am not sure what you are trying to do. It is always easier to suggest a solution to a specific problem. But I will try to answer anyway: 1) "time ordering of run transitions" - of course midas transitions are ordered by transition sequence numbers and the tmfe class provides methods to control this. ditto for the mfe.cxx frontends. 2) for one TMFrontend, the order of calling HandleBeginRun() is the order in which equipments were added to the equipment using FeAddEquipment(). HandleEndRun() is called in reverse order. (I better check this). 3) to have multiple TMFrontends in one program would be unusual (mfe.cxx frontends completely do not support this), but should work. Everything was coded to support this, but it was never tested in practice because we cannot invent any useful use-case for it. HandleBeginRun() handlers are likely to be called in the frontends are created. (I could check this and confirm it works, as long as you have a valid use-case for this configuration). 4) Frontend X has EquipmentA and EquipmentB, you want EqA::HandleBeginRun() to be called at run transition 200 and EqB::HandleBeginRun() to be called at run transition 400. This is not directly supported by mfe.cxx frontends (the begin_run() handler is a global function) and I did not directly implement it in the TMFE frontend. But I think this would be a useful improvement. I will look into this. Likely I will add per-equipment data members fEqConfBeginRunSeqNo, fEqConfEndRunSeqno, etc. Value 0 would unregister the corresponding run transition handler. This would cleanup the code quite a bit, a bunch of RegisterTranstionXXX functions could go away. K.O.
2926	29 Dec 2024	Pavel Murat	Forum	time ordering of run transition calls to TMFeEquipment things
Dear MIDAS experts, I have a question about "tmfe approach" to implementing MIDAS frontends. If I read the code correctly, within this approach it is the TMFeEquipment things, not the TMFrontend's themselves, which handle the run transitions - the TMFrontend class https://bitbucket.org/tmidas/midas/src/423082fb67c7711813fcda61f7cd03784c398f49/include/tmfe.h#lines-306:378 simply doesn't have methods to handle those directly. So how does a user control the sequence in which TMFeEquipment::HandleBeginRun functions of different TMFeEquipment pieces are called at begin run? - there are two cases to consider: TMFeEquipment things defined by the same TMFrontend and by different TMFrontend's. Many thanks and happy holidays to everyone! -- regards, Pasha
2925	19 Dec 2024	Stefan Ritt	Suggestion	New alarm count added
Another modification has been done to the alarm system. We have often cases where an alarm is triggered on some readout noise. Like an analog voltage just over the alarm threshold for a very short period of time, triggered sometimes from environmental electromagnetic effects like turning on the light. To mitigate this problem, an "alarm trigger count" has been implemented. Every alarm has now a variable "Trigger count required". If this value is zero (the default), the alarm system works as before. If this value is nowever set to a non-zero value N, the alarm limit has to be met on N consecutive periods in order to trigger the alarm. Each alarm has a "Check interval" which determines the period of the alarm checking. If one has for example: Check interval = 10 Trigger count required = 3 then the alarm condition has to be met for 3 consecutive periods of 10 seconds each, or for 30 seconds in total. The modification has been merged into the develop branch, and people have to be aware that the alarm structures in the ODB changed. The current code tries to fix this automatically, but it is important that ALL MIDAS CLIENTS GET RE-COMPILED after the new code is applied. Otherwise we could have "new" clients expecting the new ODB structure, and some "old" clients expecting the old structure, then both types of clients would fight against each other and change the ODB structure every few seconds, leading to tons of error messages. So if you pull the current develop branch, make sure to re- compile ALL midas clients. /Stefan
2924	19 Dec 2024	Stefan Ritt	Bug Report	[History plots] "Jump to current time" resets x range to 7d
I had put in a check which limits the range to 7d into the past if you press the "play" button, but now I'm not sure why this was needed. I removed it again and things seem to be fine. Change is committed to develop. Stefan
2923	17 Dec 2024	Lukas Gerritzen	Bug Report	[History plots] "Jump to current time" resets x range to 7d
To reproduce: - Open a history plot, click [-] a few times until the x axis shows more than 7 days. - Scroll to the past (left) - Click "Jump to current time" (the triangle) Expected result: The upper limit of the x axis is at the current time and the lower range is now - whatever range you had before (>7d) Actual result: The upper limit is the current time, the lower limit is now - 7d (The interval seems unchanged if the range was < 7d before clicking "Jump to current time")
2922	13 Dec 2024	Marius Koeppel	Info	New Feature: Message Search
Dear all, a new feature was implemented which allows to search the log messages in MIDAS. Attached one can find a more detailed explanation of how to use the feature. If you see any issues / bugs feel don't hesitate to report them. For now the code was tested on Linux / Mac OS using Chrome, Firefox and Safari. Best, Marius
Attachment 1: filters.pdf

2921	12 Dec 2024	Stefan Ritt	Suggestion	New alarm sound flag to be tested
We had the case in MEG that some alarms were actually just warnings, not very severe. This happens for example if we calibrate our detector once every other day and modify the hardware which actually triggers the alarm for about an hour or so. The problem with this is now that the alarm sounds every few minutes, and people get annoyed during that hour. They turn down the volume of their speakers, or even disable the alarm sound. If the detector gets back into the default mode again, they might forget to re-enable the alarm, which causes some risk. Turning down the volume is also not good, since during that hour we could have a "real" alarm on which people have to react quickly in order not destroy the detector. The art is now to configure the alarm system in a way that "normal" changes do not annoy people or cover up really severe alarms. After long discussions we came to following conclusion: We need a special class of alarm (let's call it 'warning') which does not annoy people. The warning should be visible on the screen, but not ring the alarm bell. While we have different alarm classes in midas, which let us customize the frequency of alarms and the screen colors, all alarms or warnings ring the alarm sound right now. This can be changed in the browser under "Config/Alarm sound" but that switch affects ALL alarms, which is not what we want. The idea we came up with was to add a flag "Alarm sound" to the alarm classes. For the 'warning' we can then turn off the alarm sound, so only the banner is shown on top of the screen, and the spoken message is generated every 15 mins to remind people, but not to annoy them. I added this "Alarm sound" flag in the branch feature/alarm_sound so everybody can test it. The downside is that all "Alarm/Classs/xxx" need to be modified to add this flag. While the new code will add this flag automatically (with a default value of 'true'), the size of the alarm class record changes by four bytes (one bool). Therefore, all running midas programs will complain about the changed size, until they get recompiled. Therefore, to test the new feature, you have to checkout the branch and re-compile all midas programs you use, otherwise you will get errors like Fixing ODB "/Alarms/Classes/Alarm" struct size mismatch (expected 352, odb size 348) I will keep the branch for a few days for people to try it out and report any issue, and later merge it to develop. Stefan

Goto page Previous 1, 2, 3 ... 8, 9, 10 ... 152, 153, 154 Next

ELOG V3.1.4-2e1708b5