STAR*NET V6 - Circe
STAR*NET V6 - Circe
STAR*NET V6 - Circe
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 8 Analysis of Adjustment Output<br />
8.3 Summary of Files Used and Options Settings<br />
The first few lines of the listing file identify the version of <strong>STAR*NET</strong> that you are<br />
using, and your licensing information. If you need to contact Starplus Software for<br />
technical assistance, you may be asked for this information. The exact time and date of<br />
the run is shown, so that you can keep track of multiple runs of the same project.<br />
The project name, project folder and names of all input data files used in the adjustment<br />
are listed next.<br />
Last comes a summary of the option settings that were in effect at run time. These<br />
settings are important to have documented in the output listing file because many of<br />
these settings, such as default standard errors, refraction index, and instrument or target<br />
centering errors, directly affect your results. Note that when standard errors are changed<br />
to an Instrument Library setting by use of an “.INSTRUMENT” inline option in your<br />
data, these standard error settings are also shown in this section.<br />
8.4 Listing of Input Data Files (Optional)<br />
This section of the listing file is a direct line by line copy of your input data files. This<br />
can be useful for historical documentation purposes, because it contains all of your input<br />
data plus any comments you included in your data when it was prepared. This section is<br />
optional, and normally you will include it only for documentation or debugging<br />
purposes.<br />
8.5 Adjustment Solution Iterations (Optional)<br />
<strong>STAR*NET</strong> will optionally list the coordinate changes for each iteration in the<br />
adjustment. This option is normally used only for analyzing an adjustment that has large<br />
errors and will not converge. In that situation, it may be useful to track the coordinate<br />
changes at each iteration to see if some clue to the problem can be found. For normal<br />
runs, you usually will not want to see this information.<br />
Iteration # 1<br />
Changes from Last Iteration (FeetUS)<br />
Station dN dE dZ<br />
259 -0.0733 0.0209 0.0124<br />
51 -0.0337 -0.3068 0.1004<br />
52 0.0445 -0.3122 -0.0543<br />
55 -0.2011 0.0993 -0.0223<br />
Coordinate Iteration Changes (3D Example)<br />
118