STAR*NET V6 - Circe
STAR*NET V6 - Circe
STAR*NET V6 - Circe
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 8 Analysis of Adjustment Output<br />
10. Run a minimally constrained adjustment. If you are tying your survey to a number of<br />
fixed points, start off with one fixed point and a fixed azimuth, or two fixed points,<br />
until you have all of the data debugged. Then start fixing (with the “!” symbol) any<br />
remaining fixed points one by one.<br />
11. Run the adjustment but restrict it to a single iteration in the Adjustment Options.<br />
Look at the changes in coordinates after the first iteration to see which stations seem<br />
to be acting strangely.<br />
12. Run the adjustment with the “Coordinate Changes each Iteration” listing option on,<br />
then review that section in the listing looking for any unusual or excessive changes<br />
in coordinates during adjustment.<br />
13. Use the “.DATA OFF” and “.DATA ON” inline options to turn off sections of your<br />
input data file. Break it down into pieces until you find the section where the errors<br />
may reside.<br />
14. Unweight observations that you suspect by using a standard error of “*”. Run the<br />
adjustment and see if your problems go away. Remember that you will have much<br />
more success with this technique if you have a number of redundant observations in<br />
the survey.<br />
15. If you have interconnected traverses, try disconnecting any suspect traverse, when<br />
possible, by temporarily renaming its ending station name and removing its closing<br />
angle. Turn it into an open ended traverse that will influence nothing else. See where<br />
the end of the traverse moves to when you adjust. Do other traverses improve?<br />
16. Run Blunder Detect. See Chapter 6, “Running Adjustments” for details.<br />
136