5.5Process Menu

Azimuth determination options

1.Off, no azimuth determination - Process using this option first to see the quality of the solution. If the quality is good, then the option 2 or 3 will work.

2.On, use distance constraint in KAR and engage KAR if out of tolerance - Single frequency users who know the fixed distance between the L1 phase centres of their moving antenna should use this option because it speeds up KAR resolution time. Otherwise, use option 3.

3.On, but compute only - Use this option if you need straightforward azimuth, if the quality of the data is not suitable for KAR usage or if the distance is not known or unstable.

4.On, but only use distance constraint to engage KAR if out of tolerance - Dual frequency users should use this option if they know the fixed distance between the L1 phase centres of their two moving antennae. If not, use the option 3.

See Section 2.3, on Page 33 or information regarding all of the options available via this menu.

5.6 Setting Menu

See Section 2.6, on Page 94 for information regarding all of the options available via this menu. Only the Moving Baseline Options feature will be discussed here, as it is exclusive to GrafMov.

5.6.1Moving Baseline Options

This feature is the only way for GrafMov to distinguish a moving baseline project from a typical project with a static base station.

Moving Baseline Processing

Determines whether or not to process data as a moving baseline project. If this option is disabled, the processor will behave as it does in GrafNav, and assume the base station is static.

Azimuth Determination

These options are listed in the shaded box.

Standard deviation/tolerance

This value is used to engage KAR if the distance between the two antennas becomes too large or too small. Using a strict tolerance might cause GrafMov to engage KAR continuously, resulting in a possible infinite loop or very long processing time. By default, 2 cm is used, but you can change this after processing without azimuth determination.