List of integer antenna IDs used in conjunction with the current measurement.

For two-way ground range, and Doppler a single antenna ID identifies the antenna on the satellite. If the list is empty, the default antenna associated with the SatToGround transponder is used. If no such default exists, then the measurement is considered to be to the center of mass.

For two-way space based range, a single antenna ID identifies the antenna on the target satellite. If the list is empty, the default antenna associated with the SatToSat transponder is used. If no such default exists, then the measurement is considered to be to the center of mass.

For one-way bistatic range, BRTS range and BRTS Doppler, the first antenna ID identifies the uplink antenna on the satellite and the second ID identifies the downlink antenna. If the list is empty, the default antennas associated with the Relay transponder are used (default antenna 2 is the downlink). If no such defaults exist, then the measurement is considered to be to the center of mass.

For 4 legged range and 5 legged doppler, the first antenna ID identifies the uplink antenna on the satellite and the second ID identifies the crosslink antenna. If the list is empty, the default antennas associated with the Relay transponder are used (default antenna 2 is the downlink). If no such defaults exist, then the measurement is considered to be to the center of mass.

Note: TDRS antenna ids are returned from the UTDF tracking data provider as 0 - SGL, 1 - SA1, 2 - SA2, 3 - MA.

For GPS CA, P1, and/or P2 pseudorange and/or L1, L2, LA phase a single antenna ID associated with the GPS Receiver is used. If the list is empty, the default antenna associated with the GPS Receiver is used. If no such default exists, then the measurement is considered to be to the center of mass.

For TDOA, FDOA and TDOA Dot the first two antenna IDs identify the uplink and downlink antennas on the path 1 relay satellite and the third and fourth antenna IDs identify the uplink and downlink antennas on the path 2 relay.

For SD TDOA, SD FDOA and SD TDOA Dot the first two antenna IDs identify the uplink and downlink antennas on the path 1 relay satellite and the third and fourth antenna IDs identify the uplink and downlink antennas on the path 2 relay. The fifth and sixth antenna IDs identify the uplink and downlink antennas on the path 3 relay satellite and the seventh and eighth antenna IDs identify the uplink and downlink antennas on the path 4 relay. Note that the path 1 and path 3 use the same relay satellite but can use different uplink and downlink antennas. The same is true for path 2 and path 4.

An ID is added to the AntennaIDs list using the insert method. For example the syntax in perl would be:

Applies to GPS Phase Count measurements. Specifies the change in the cycle count across the phase count interval, where the phase count interval is specified by the Doppler_Dt parameter.

Not to be confused with the Value parameter, which specifies the actual cycle counter value at this measurement time.

NOTE: You should not input times in EpochSec or any other epoch-related time, since you have no control over the Epoch in ODTK.

Specifies the Doppler count interval in units of seconds. If this value is undefined, it will default to 0, and the user can override the value via each facility's Measurement Statistics for Doppler measurements.

This parameter also specifies the GPS phase count interval for GPS phase measurements. For GPS Phase measurements it must be set along with the CycleCountChange parameter.

Only applicable to GNSS measurements. A one character identifier that identifies the GNSS system type:

'G' = GPS, 'R' = GLONASS, 'E' = Galileo, 'C' = BeiDou, 'J' = QZSS

Only applicable to GNSS measurements. A one character identifier that identifies the GNSS system type:

'G' = Geodetic, 'S' = Spaceborne

Only applicable to GNSS measurements. List of RINEX 3 three-character code identifiers associated with this measurement. See http://igscb.jpl.nasa.gov/components/formats.html, RINEX 3 format, Section 5.

Single-Frequency and Single-Frequency Single Differenced measurements have one code identifier in the list.

Dual-Frequency Single Differenced measurements have two code identifiers in the list.

The code identifiers are the RINEX 3 identifiers that identify (observation type, frequency band, mode/channel).

For example:

A single frequency GPS L1 C/A pseudo range would have one list item: "C1C".

A dual frequency GPS L2C and L5 phase would have two items in the list: "C2L", C5X".

The %IAgODTrackingNameList:IAgODProvideTrackingDataLib~IAgODTrackingNameList% methods are used to manage these list entries.

As an alternative to inputting a date string, we provide the option of inputting time directly in our internal units of julian day number and minutes after midnight, in TDT time. The JulianDay is the whole number corresponding to midnight of a given day, and the minutes after midnight must be converted to TDT.

The defaults are 0 for JulianDay and 0.0 for MinutesAfterMidnight.

Thus, to input a date of 06 Jun 2002 00:00:00, one would use the perl command syntax:

$pObs->{JulianDay} = 2452431;
$pObs->{MinAfterMidnight} = 1.06973333333333;

List of integer laser retro reflector IDs used in conjunction with laser ranging measurements.

When the provider is inputting measurements to ODTK for processing, this list may be either a single retro reflector ID or the list may be empty. If the list is empty then the retro reflector object included under the vehicle of interest will be used for bias and CM offsets. If the list is empty and more than one retro reflector object is included then the retro reflector name which is first alphabetically is used. If the list is empty and no retro reflector objects are included then the measurement will be processed assuming retro reflector bias of zero and CM offset of zero.

During simulation when ODTK is outputting measurements to the provider, this list will contain a single element identifying the retro reflector used. 

An ID is added to the LaserRetroIDs list using the insert method. For example the syntax in perl would be:

$pObs->{ LaserRetroIds }->Insert(0, $Rnum);

A numeric ID that specifies the type of measurement.

The default is 13 (nothing).

As an alternative to inputting a date string, we provide the option of inputting time directly in our internal units of julian day number and minutes after midnight, in TDT time. The JulianDay is the whole number corresponding to midnight of a given day, and the minutes after midnight must be converted to TDT.

The defaults are 0 for JulianDay and 0.0 for MinutesAfterMidnight.

Thus, to input a date of 06 Jun 2002 00:00:00, one would use the perl command syntax:

$pObs->{JulianDay} = 2452431;
$pObs->{MinAfterMidnight} = 1.06973333333333;

This flag only applies to laser ranging measurements. It tells the measurement model whether to acount for the retro reflector phase center offset to the vehicle center of mass. The default is "true".

If the measurements in the file have already had center of mass corrections applied, then this flag should be set to false.

A flag that tells the measurement model whether to include an ionospheric correction.

The default is 'true'.

If the measurements in the file have already had ionospheric corrections removed, then this flag should be set to false. Note that if this flag is set to true, the user can override it via the interface for the TrackingSystem object.

A flag that tells the measurement model whether to include a tropospheric correction.

The default is 'true'.

If the measurements in the file have already had tropospheric corrections removed, then this flag should be set to false. Note that if this flag is set to true, the user can override it via the interface for the TrackingSystem object.

A numeric ID that defines the event correlating to the measurement time tag.

The default is 0.

List of integer tracking data IDs used in conjunction with the current measurement.

The default is an empty list.

The TrackerIDs list and TrackerNames list are mutually exclusive. If all of the object IDs are integers, add them to the TrackerIDs list; if any of the IDs are alphanumeric, then all the IDs must be added to the TrackerNames list instead.

For two-way ground range, az, el, and Doppler the first tracking ID is the ID of the ground facility used to track the satellite and the second (and last) ID is the ID for the satellite being tracked.

For accelerometer measurements the first tracking ID is the ID of the Accelerometer Sensor  and the second (and last) ID is the ID for the satellite hosting the accelerometer.

For space based RA, DEC, azimuth, elevation, range, and Doppler, the first tracking ID is the ID of the observing satellite and the second (and last) ID is the ID for the satellite being tracked.

For GPS CA, P1, and/or P2 pseudorange and/or L1, L2, LA phase (non single-differenced) the first tracking ID is the ID of the GPS Receiver and the second (and last) ID is the PRN of the transmitting SV.

For GPS SD measurements the first tracking ID is the ID of the GPS Receiver, the second ID is the PRN of the first SV, and the third (and last) ID is the PRN of the second SV.

For GPS 2 legged measurements the first tracking ID is the ID of the GPS Receiver, the second ID is the ID of the relay satellite and the third ID is the PRN of the transmitting SV.

For GPS navigation solution measurements, the only tracking ID is that of the GPS Receiver.

For TDOA, TDOA Dot and FDOA measurements, the first tracking ID is the ID of the emitter, the second (path 1) and third (path 2) IDs are the IDs of the relay satellites and the fourth ID is the ID of the receive station. The measurements are time tagged based on signal reception on path 1 and are computed as (path 2 minus path 1).

For SD TDOA and SD FDOA measurements, the first (path 1 and path 2) and second (path 3 and path 4) tracking IDs are the IDs of the emitters, the third (path 1 and path 3) and fourth (path 2 and path 4) IDs is the ID of the relay satellite and the third ID is the ID of the receive station. The measurements are time tagged based on signal reception on path 1 and are computed as (path 4 minus path 3) - (path 2 minus path 1).

For SB TDOA, SB TDOA Dot and SB FDOA measurements, the first tracking ID is the ID of the emitter, the second (path 1) is the ID of a tracking instrument on the first receiving satellite and the third (path 2) ID is the ID of the second receiving satellite. The measurements are time tagged based on signal reception on path 1 and are computed as (path 2 minus path 1).

For SB TDOA SBE and SB FDOA SBE measurements, the emitter id comes first followed by (path 1) ID of a tracking instrument on the first receiving satellite and finally the (path 2) ID of the second receiving satellite. The measurements are time tagged based on signal reception on path 1 and are computed as (path 2 minus path 1).

For TDOA 2 Emitters and TDOA 2 Emitters Dot measurements, the first (path 1) and second (path 2) tracking IDs are the IDs of the emitters, the third ID is the ID of the relay satellite and the fourth ID is the ID of the receive station. The measurements are time tagged based on signal reception on path 1 and are computed as (path 2 minus path 1).

An ID is added to the TrackerIDs list using the insert method. For example the syntax in perl would be:

$pObs->{TrackerIDs}->Insert(0, $Snum); $pObs->{TrackerIDs}->Insert(1, $Vnum);

The insertion order, 0 for Tracker Snum and 1 for satellite Vnum, is important because otherwise wrong values will be assigned to the satellite ID and tracker ID.

Some space based azimuth/elevation or right ascension/declination measurements include an earth-fixed position vector of the sensor. The following VBScript code adds the x, y, and z positions to the observation object:

pObs.TrackerVector.CoordSystem = eCBF
pObs.TrackerVector.ElmType = ePosOnly

pObs.TrackerVector.X.Unit = "m"
pObs.TrackerVector.X.Value = Xpos
pObs.TrackerVector.Y.Unit = "m"
pObs.TrackerVector.Y.Value = Ypos
pObs.TrackerVector.Z.Unit = "m"
pObs.TrackerVector.Z.Value = Zpos
pObsSet.Add pObs

List of integer transponder IDs used in conjunction with the current measurement. The default is an empty list.

For TDOA, FDOA and TDOA Dot the first transponder ID identifies the transponder on the path 1 relay satellite and the second transponder ID identifies the transponder on the path 2 relay.

For SD TDOA, SD FDOA and SD TDOA Dot the first transponder ID identifies the transponder on the path 1 relay satellite and the second transponder ID identifies the transponder on the path 2 relay. The third transponder ID identifies the transponder on the path 3 relay satellite and the fourth transponder ID identifies the transponder on the path 4 relay.

Note that the path 1 and path 3 use the same relay satellite but can use different transponders. The same is true for path 2 and path 4.

An ID is added to the TransponderIDs list using the insert method. For example the syntax in perl would be:

$pObs->{TransponderIDs}->Insert(0, $Snum); $pObs->{ TransponderIDs }->Insert(1, $Vnum);

A method to define the numeric value of both the measurement and the input unit. Thus Value has a "Unit" member which must be an ODTK-recognized unit string.

The default is 0.0.

For example, if pObs is created to hold a Doppler measurement, then to input a value in units of meters/second, the VBS commands would be:

pObs.MeasureType = 2 ' Doppler
pObs.value.Unit = "m/sec"
pObs.value = 6628.234