Application listing: Difference between revisions

From MidasWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 26: Line 26:
* '''[[mh2sql]]''' → ''Import history files into SQL database''
* '''[[mh2sql]]''' → ''Import history files into SQL database''


* '''[[Mhdump|mhdump]]'''  → ''Display history events''
* '''[[Mhist|mhist]]'''  → ''Display history data''
 
* '''[[Mhdump|mhdump]]'''  → ''Display history data (lower-level)''


* '''[[mhttpd]]'''  → ''Webserver for Run Control''
* '''[[mhttpd]]'''  → ''Webserver for Run Control''
Line 38: Line 40:
* '''[[msysmon]]''' → ''Log CPU/network usage into midas history''
* '''[[msysmon]]''' → ''Log CPU/network usage into midas history''


* '''[[mmessenger]]''' → ''Forward midas messages to slack/discord/mattermost'''
* '''[[mmessenger]]''' → ''Forward midas messages to slack/discord/mattermost''


* '''[[mtape]]'''    → ''Tape manipulator''
* '''[[mtape]]'''    → ''Tape manipulator''

Latest revision as of 16:05, 3 August 2023


Introduction

The MIDAS package after Compilation & Build will contain a new directory

$MIDASSYS/linux/ space or space $MIDASSYS/linux-m32/

under which the MIDAS library (in ../lib) and the images (in ../bin) will be placed. Most of the MIDAS applications are located here. There a few other applications that can be manually built under /$MIDASSYS/utils as well.

  • dioDirect I/O driver utility
  • hveditHigh Voltage editor and GUI
  • mchartAssembles data for stripchart
  • mdumpDisplay contents of event banks
  • melogSend information to elog
  • mevbEvent builder application
  • mh2sqlImport history files into SQL database
  • mhistDisplay history data
  • mhdumpDisplay history data (lower-level)
  • mhttpdWebserver for Run Control
  • mstatMonitor and display
  • msysmonLog CPU/network usage into midas history
  • mmessengerForward midas messages to slack/discord/mattermost
  • mtapeTape manipulator
  • odbhist ODB parameter history display