Cdms workshop: Difference between revisions
Jump to navigation
Jump to search
(The midas documentation has moved to https://midas.triumf.ca/docs/) |
|||
| Line 1: | Line 1: | ||
<div style="border: 1px solid #a2a9b1; border-left: 6px solid #f28500; background-color: #fef6e7; padding: 0.5em 1em; margin-bottom: 1em;">'''This is a historical page.''' It is kept for reference, and is no longer updated. The current midas documentation is at [https://midas.triumf.ca/docs/develop/ midas.triumf.ca/docs].</div> | |||
= Notes for the CDMS workshop March 2014 = | = Notes for the CDMS workshop March 2014 = | ||
Latest revision as of 22:00, 30 October 2026
This is a historical page. It is kept for reference, and is no longer updated. The current midas documentation is at midas.triumf.ca/docs.
Notes for the CDMS workshop March 2014
MIDAS general picture
MIDAS main data path
hardware -> mfe user thread -> ring buffer -> (compression thread -> ring buffer ->) mfe main thread -> TCP socket -> mserver -> event buffer -> event builder thread -> SYSTEM buffer -> mlogger -> (ring buffer -> compression thread -> ) data file -> lazylogger -> dcache/castor/hadoop/cloud storage
Needs to scale from 0.5GB/0.3GHz/1core PPC on FPGA to 1GB/1GHz/1core 32-bit ARM to 64GB/4GHz/12core 64-bit x86!
MIDAS web security
MIDAS slow controls paths
MIDAS history paths
Write path:
hardware -> mfe -> SYSTEM buffer -> mlogger -> data.mid.gz mfe -> ODB -> hotlink mlogger -> hs_write -> .hst binary file, MySQL database, SQLITE database, (maybe "no sql" database)
Plot path:
user web browser -> mhttpd -> hs_read -> read from .hst binary file, MySQL database, etc -> use "gd" to make .png image -> send png file to user -> (future: return to user a JSON data, plot using JS graphics)