How to read the "readable" PIDF

Below is an example PIDF:

PIDF version 2.0: IMAGE: IMAGE-1: HENA: SCIENCE: IMHIH (APL)

Group  0: Neutral Hydrogen Pixels
   0 SSD H Elevation 0     0    s0    0,4,7,8
   1 SSD H Elevation 1     1    s0    0,4,7,8
   2 SSD H Elevation 2     2    s0    0,4,7,8
   3 SSD H Elevation 3     3    s0    0,4,7,8
   4 SSD H Elevation 4     4    s0    0,4,7,8
  .....
  19 SSD H Elevation 19   19    s0    0,4,7,8

Group  1: General Info
  20 Spin Number          -1a0  s0    5
  21 Start Sector Number  -1a1  s0    6

Units
   0 [ -1.0,   259.0 ]     : Unitless          : Telemetry   : Raw  
   1 [ -1.0,     4.0 ]     : Unitless          : Telemetry   : Raw  
   2 [ -1.0,     9.0 ]     : Unitless          : Scan Index  : Scan 
   3 [ -1.0,     4.0 ]     : Unitless          : Integer     : Value
   4 [  0.0, 66000.0 ]     : c/acc             : counts/acc  : c/acc t0,op0
   5 [  0.0, 66000.0 ]     : Unitless          : Value       : Val  
   6 [  0.0,   130.0 ]     : Unitless          : Value       : Val  
   7 [  1.0, 66000.0 ] log : c/sec             : Count Rate  : c/sec t150,op0
   8 [  1.0,   1.0e9 ] log : cnts/(cm**2-s-sr) : Number Flux : NF    [u7] t1,op3

Scans
   0 block= 0 units=  1I

Subsequent lines, introduced by "Group N", contain lists of sensors defined for that PIDF group. Each line describes:

• the PIDF sensor number, which is usually the order in which the sensor is defined in the source PIDF.
• the PIDF sensor name.
• the VIDF/ancillary number. This indicates the magic numbers to feed read_drec() and convert_to_units() in order to get data values. An "a" followed by a digit indicates an ancillary sensor, whatever that is.
• if a sensor uses "pitch angles", there will be a 'p' between the vnum and scan fields. I have yet to see any PIDF that defines the pitch angle flag.
• the scan, whatever that is.
• the units defined for this sensor. Each sensor may use one or more units. Unit definitions are listed at bottom.

The Units header introduces the unit definitions. Each units line contains:

• the unit number corresponding to that listed in each sensor line.
• the range defined for that unit.
• whether or not the unit is to be plotted on a log scale.
• the three labels (actually the PIDF "unit_label", "long_description", and "short_description"), in that order.
• the tables and operations used by the unit. Note that tables are defined in the VIDF.

The Scans header introduces the scans. I have no idea what this is.

PLEASE NOTE: My script does not extract everything in the source PIDF. In particular, the "component" field, "Data Quality", "modes", and some "scan" thingies are ignored. Source code is open; feel free to add support for these if you need them.

Operated by the University of California for the National Nuclear Security Administration, of the US Department of Energy.     Copyright © 2002 UC | Disclaimer/Privacy