Difference between revisions of "Mce status"

From MCEWiki
 
(Snapshot output)
Line 21: Line 21:
 
The output block has the following form:
 
The output block has the following form:
  
   <HEADER>
+
   &lt;HEADER&gt;
   <RB cc led> 00000007
+
   &lt;RB cc led&gt; 00000007
   <RB cc ...>
+
   &lt;RB cc ...&gt;
   </HEADER>
+
   &lt;/HEADER&gt;
 
 
This is a compliant MAS runfile v2 block, alas.
 
 
 
  
 +
This is a compliant [[Runfile format v2 | runfile block]], alas.
  
 
= Mapping output =
 
= Mapping output =

Revision as of 15:11, 19 March 2008

Overview

The primary purpose of mce_status is to provide a snapshot of the MCE configuration. This is most important just prior to aquiring frame data, in order to properly interpret the frame output in subsequent analysis.

The secondary function of mce_status, or, at least, the primary secondary function of mce_status, is to provide a summary of the mappings that MAS uses to translate card and parameter names into MCE hardware addresses.

Snapshot output

mce_status is non-interactive. By default, when invoked, it scans the MCE hardware configuration file and issues read commands to each card/parameter name pair in the file. The results are printed to standard out in a pseudo-XML format. (Alternative output formats can be made available on request.)

The output block has the following form:

 <HEADER>
 <RB cc led> 00000007
 <RB cc ...>
 </HEADER>

This is a compliant runfile block, alas.

Mapping output

When invoked with the -g option, mce_status scans the hardware configuration file and outputs first the list of direct hardware mappings, and then the list of functional mappings. The list looks something like this:

...

Command line options

Right.