Differences between revisions 1 and 2
Revision 1 as of 2012-08-28 08:49:04
Size: 765
Editor: solpc
Comment:
Revision 2 as of 2012-08-28 08:52:57
Size: 956
Editor: solpc
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
||0|| 0-3 || 0x0F ||HFCORRVR || Height of formation code version used to find disk center. Vers 2 for all data to date.|| || 0|| 0-3 || 0x0F ||HFCORRVR || Height of formation code version used to find disk center. Vers 2 for all data to date.||
Line 11: Line 11:

Prior to Aug 2012 hmi.lev1 had a keyword named HFCORRVR which can be taken as correct for fields 0 and 1 except that a 0 in the first nibble (field 0) should be taken as meaning missing.

Calibration Version keywords

A keyword for calibration version keywords are included in level-1 data (CALVER32) through higher level products (CALVER64) starting in August 2012. This keyword is, at the start, considered to be a set of fields consisting of single hexidecimal digits.

The presently assigned values are from least significant nibble:

Field

bits

mask

name

Note

0

0-3

0x0F

HFCORRVR

Height of formation code version used to find disk center. Vers 2 for all data to date.

1

4-7

0xF0

CROTA2VR

Version of CROTA2 in the Master pointing table. Vers 0 prior to Transit of Venus, then 1.

A value of all bits set in a field signifies missing information. The default value of CALVER64 is 0xFFFFFFFFFFFFFFFF.

Prior to Aug 2012 hmi.lev1 had a keyword named HFCORRVR which can be taken as correct for fields 0 and 1 except that a 0 in the first nibble (field 0) should be taken as meaning missing.

JsocWiki: CalibrationVersions (last edited 2022-10-04 03:03:40 by PhilScherrer)