|
|
|
|
|
The Post Processing Engine History view is a table listing all processed baselines since the module has been started. For a detailed description of the columns in the spreadsheet see the following table.
Column |
Description |
More Information |
|
|---|---|---|---|
Status icon |
Icon visually describing the processing status of the baseline. |
Float solution not accepted:
|
Float solution accepted:
|
Event Time |
Date and time the processing results were logged to the database. |
Time system can be selected at the status bar.
|
|
Session Start |
Date and time of the first available epoch of the processed baseline. |
GPS time. |
|
Session End |
Date and time of the last available epoch of the processed baseline. |
GPS time. |
|
Baseline |
<Base> - <Station> |
The baseline vector is defined by the starting (Base) and aiming (Station) reference station. Stations are indicated by their unique Station codes. |
|
Solution |
No position |
No solution possible. |
|
|
No/Old RTK position fixes |
Only after reset of calculation. No current solution possible, previous position fixes are kept. |
|
|
Float |
RTK, Float solution. |
|
|
Fixed |
RTK, Fixed ambiguities. |
|
Status |
Status message |
|
|
Orbit |
Broadcast, Predicted, or both (Mixed). |
Indicates which orbit types are used for processing. |
|
Epochs |
|
Number of epochs used for processing. |
|
Length |
In meters |
Calculated from the known positions. |
|
dx, dy, dz |
In meters |
Uni-directional baseline components. |
|
The baseline has been processed successfully and has a fixed solution.
The baseline has been processed with float solution. 
Baseline processing failed. See the