The following ten VIDF fields form the pitch angle information block. These fields are only defined if the VIDF field Pitch Angle Defined is set to 1, otherwise they are entered into the VIDF as NULL fields.
The pitch angle definition block together with the VIDF Normal Contants Definitions is a full definition of all of the information necessary to compute the pitch angles for the defined UDF sensors. The UDF UDF kernal makes use of all of the information in computing pitch angles.
A scalar field, this field defines the pitch angle algorithm flag. If the VIDF field Pitch Angle Defined is 0 then this field is undefined and is entered into the VIDF as a null line.
When defined the field is an integer value which indicates which algorithm should be used in computing the pitch angles. Currently there is only the one defined algorithm which has an associated value of 1.
The algorithm used in association with pitch angle format 1 is:
Here PA is the computed pitch angle, N is the sensor vector unit normal and B is the vector magnetic field. In this computation both N and B must be given in the same coordinate system. The values for N are specified in the VIDF Constants Block (constant id's 6 thru 8).
The field begins with the line format id b followed by an integer specifying the number pitch angle algorithm. An optional comment field may follow.
Sample PITCH ANGLE FORMAT field:b 1 /* Pitch Angle Format */
This is a scalar field which holds the UDF Project acronym of the UDF definition containing the magnetic field information used in the pitch angle computation. If the VIDF field Pitch Aangle Defined is 0 then this field is undefined and is entered into the VIDF as a null line.
The magnetic field project field begins with the line format id T Sample MAGNETIC FIELD PROJECT field:
T TSS /* Magnetic Field PROJECT */
This is a scalar field which holds the UDF Mission acronym of the UDF definition containing the magnetic field information used in the pitch angle computation. If the VIDF field Pitch Aangle Defined is 0 then this field is undefined and is entered into the VIDF as a null line.
The magnetic field mission field begins with the line format id T followed by a text entry not to exceed 20 characters in length. An optional comment field may follow.
Sample MAGNETIC FIELD MISSION field:T TSS-1 /* Magnetic Field MISSION */
This is a scalar field which holds the UDF Experiment acronym of the UDF definition containing the magnetic field information used in the pitch angle computation. If the VIDF field Pitch Aangle Defined is 0 then this field is undefined and is entered into the VIDF as a null line.
The magnetic field experiment field begins with the line format id T followed by a text entry not to exceed 20 characters in length. An optional comment field may follow.
Sample MAGNETIC FIELD EXPERIMENT field:T TEMAG /* Magnetic Field EXPER */
This is a scalar field which holds the UDF Instrument acronym of the UDF definition containing the magnetic field information used in the pitch angle computation. If the VIDF field Pitch Aangle Defined is 0 then this field is undefined and is entered into the VIDF as a null line.
The magnetic field instrument field begins with the line format id T followed by a text entry not to exceed 20 characters in length. An optional comment field may follow.
Sample MAGNETIC FIELD INSTRUMENT field:T TEMAG /* Magnetic Field INST */
This is a scalar field which holds the UDF Virtual Instrument acronym of the UDF definition containing the magnetic field information used in the pitch angle computation. If the VIDF field Pitch Aangle Defined is 0 then this field is undefined and is entered into the VIDF as a null line.
The magnetic field virtual instrument field begins with the line format id T followed by a text entry not to exceed 20 characters in length. An optional comment field may follow.
Sample MAGNETIC FIELD VIRTUAL INSTRUMENT field:T TMMI /* Magnetic Field VINST */
This is a array field of length 3 containing the three UDF sensor numbers associated with the magnetic components Bx , By, and Bz respectively. These sensor numbers will have been defined in the UDF definition of the magnetic field virtual instrument defined in the previous five field. If the VIDF field Pitch Angle Defined is 0 then this field is undefined and is entered into the VIDF as a null line.
The magnetic field sensors field begins with the array designation line: m followed by the input 3 M. Here 3 is the total number of entries and M is the number of entries given on each line. The following line begins with the line format s followed by the three integer sensor numbers. An optional comment field may be added to the end of each line.
Sample MAGNETIC FIELD SENSORS field:m 3 3 /* Magnetic Vector Components */ s 0 1 3 /* Bx By and Bz Sensors */
This is an scalar field holding the the number of steps in the algorithm used to convert the raw magnetic field data to physical units. This is generally copied directly out of the PIDF Units block associated with the magnetic field UDF definition which holds the conversion algorithm to be used. If the VIDF field Pitch Angle Defined is 0 then this field is undefined and is entered into the VIDF as a null line.
The field begins with the line format id s followed by an integer specifying the number of algorithm steps. An optional comment field may follow.
Sample MAGNETIC FIELD ALGORITHM STEPS field:s 1 /* Num of Algorithm Steps */
This is an array field which holds the VIDF table numbers used at each step of the algorithm that converts the raw magnetic field data to physical units. This is generally copied directly out of the PIDF Units block associated with the magnetic field UDF definition which holds the conversion algorithm to be used. If the VIDF field Pitch Angle Defined is 0 then this field is undefined and is entered into the VIDF as a null line.
The algorithm table field begins with the array designation line: m followed by the input N M. N is the total number of entries and is set to the value of the Number of Algorithm Steps field and M is the number of entries given on each line. Each of the following N lines begins with the line format s followed by M entries (except the last line which may have less). An optional comment field may be added to the end of each line. NOTE: VIDF table numbers do not exceed 255.
Sample ALGORITHM TABLE field:m 1 1 /* Algorithm Tables */ s 3 /* T00 */
This is an array field holding the VIDF table operations used at each step of the algorithm that converts the raw magnetic field data to physical units. This is generally copied directly out of the PIDF Units block associated with the magnetic field UDF definition which holds the conversion algorithm to be used. If the VIDF field Pitch Angle Defined is 0 then this field is undefined and is entered into the VIDF as a null line.
The algorithm operator field begins with the array designation line: m followed by the input N M. N is the total number of entries and is set to the value of the Number of Algorithm Steps field and M is the number of entries given on each line. Each of the following N lines begins with the line format s followed by M entries (except the last line which may have less). An optional comment field may be added to the end of each line.
Sample ALGORITHM OPERATIONS field:m 1 1 /* Algorithm Tables */ s 0 /* = operation */