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 />
The answer to a non-convergence problem may be as easy as simply increasing the<br />
number of iterations. Because of the geometry of the network, or possibly because of<br />
some poor initial estimates of approximate coordinates, some networks just take a larger<br />
number of iterations to converge. If the adjustment still fails to converge, even after<br />
increasing the iterations to a much larger number, say 20, there is likely some problem in<br />
your data which needs to be found and fixed.<br />
8.10 Coordinate Changes from Entered Provisionals (Optional)<br />
<strong>STAR*NET</strong> optionally lists differences between hand-entered provisional coordinates<br />
and the final adjusted coordinates. This option is particularly useful in deformation<br />
studies where the purpose is to determine how much specific stations moved since the<br />
previous survey.<br />
To do this, simply enter the specific adjusted coordinates from your previous survey as<br />
provisional (approximate) coordinates for a new survey, and request this optional listing<br />
section. Only changes from these hand-entered provisional coordinates will be shown in<br />
this output listing section, not the remaining approximate coordinates computed by the<br />
program.<br />
Coordinate Changes from Entered Provisionals (US Feet)<br />
Station dN dE dZ<br />
319 0.0000 0.0000 0.0000<br />
46 -0.5022 -0.2278 -1.6420<br />
552 -1.0064 0.9188 0.9973<br />
559 -1.0477 0.7678 0.9115<br />
560 0.2513 0.4325 0.2234<br />
Coordinate Changes from Entered Provisionals (3D Example)<br />
When entering provisional coordinates to be used as the basis for computing the changes<br />
as described above, it is important to place these coordinate values at the beginning of<br />
your data so that they will be read “first” during the processing.<br />
Why is this? When <strong>STAR*NET</strong> reads data and finds more than one set of approximate<br />
coordinates for a particular station, only the “first” coordinate values are remembered.<br />
The remaining are ignored. Therefore, placing your provisional coordinates first in the<br />
data assures you that some other approximate coordinates may be already existing later<br />
in the data will not corrupt your desired results.<br />
You might consider creating your “provisional” coordinates in a separate file, and<br />
placing this file as the first entry in your data file list. Then at some future time when you<br />
want to update the provisional coordinates for a subsequent run, simply replace that<br />
file’s contents with the newer provisional coordinates.<br />
126