When software doesn't work, giving people the exact error message helps them identify your problem.

I'm not enough of a Star*Net user to deal with details, but I wonder if the !!! needs spaces before or after the characters, and I wonder why the # in the sequence #&&& because that makes teh &&& a comment.

@bill93

!!! Is okay with no spaces.

# signifies a comment. I've never used it in a data line so don't know if that's the problem.

Starnet produces an error file which is helpful in diagnosing issues.

'RMSE is a description but maybe it doesn't like the commas after.

Starnet default angle looks like 00-00-00.00, the angle can be 00.000000 but you have to tell it that in the settings.

Also all F2 angles should be converted to look like F1 angles. For example F2 H190-00-00 Z271-00-00 should be converted to H10-00-00 Z89-00-00. This data entry error could make it so the solution can't converge.

Paulozvac33?ÿ ?ÿWhat version of Star*Net are you using??ÿ What are the error messages?? Please list each error message just as it

appears on the screen.

?ÿ

JOHN NOLTON

Thanks all, I'll post each error message on Monday, I'm using version 6. Just may be worthly to mention the way the dat file has been done as I have the felling it has something to do with this.

I have 2 different jobs 2 different arbitrary?ÿ coor which I have put together in the same txt file, coord at the beginning are coor from previous job, I'm used to n4ce where you can play with data this way but I'm not sure if starnet works in a different way and this could be why it does not like it??ÿ

Thanks?ÿ

@dave-karoly is right, look for the data lines with a 2nd face measurement, then subtract 180 from the direction for those. You can leave the zeniths as-is in the 270ish form. I like your style. Looks like you are using some prism shots and some reflectorless? This is what 95% of my Star*net input data looks like, the only difference being that I use a zero height for the instrument so that everything is a trig level. Most of the British Empire was mapped with points intersected but never occupied observed from points occupied but never intersected.

?ÿ

?ÿ

?ÿ

The file runs fine, so there isn't any "error message". The errors the OP is referring to are the error factors.

The problem is with the measurements to S7 and S12 with the instrument at S6. Either the coordinates for one or all of those points are bad by about 0.3 meters, or the measurements to them are bad. Since you have no other measurements to those points from another instrument position it is impossible to identify anything beyond that. I'm actually leaning to a poor coordinate at S6.?ÿ Freeing that point in the horizontal, with no other change, makes the data pass with flying colors.

?ÿ

@norman-oklahoma

the only thing I saw was the 6 measurements to R5 from S6, 2 are roughly H 90 with Z 292 and 4 are roughly 270 with Z 67. Maybe the current version handles that correctly. I haven't been using Starnet since TBC has gotten so much better and easier to edit data.

Here is an awareness item for StarNet V9.2 and newer regarding conventional data...

Inline Option .NORMALIZE ON|OFF

This option controls whether Reverse Face or Face Two observations (containing a zenith angle greater than 180 degrees or 200 gons) will be automatically normalized prior to the adjustment.

By default, STAR*NET 9.2 and newer behave as if .NORMALIZE ON is set, while previous versions behaved as if .NORMALIZE?ÿOFF is set.

For example, the following data will result in stations 31 and 32 being computed at the same coordinate:

While the following data will result in stations 41 and 42 being computed at the same coordinate:

Please note that with .NORMALIZE OFF set, it is not possible to combine Face-1 and Face-2 observations within a single direction set.

?ÿ

Best regards,

Terry

I see, interesting, I'll try this tomorrow when I have access to the software again and update here.

Thank you all so much for all the help provided.

?ÿ

So do I have to transform all the second faces hz angles to face 1? I just noticed one of the files have been exported from n4ce averaging the coor whereas the other not, I've got 2 faces in every single shot not only from s6, do maybe averaging them all will help with the processing in starnet? The reflectorless shoots are scanning targets.

Thanks?ÿ

Regards

Paula?ÿ

Thanks Norman for checking it this far :)?ÿ

I will double check it all tomorrow but I had run it in n4ce and it all looked fine in there, also have checked graphically in cad.?ÿ

I'll try again and let u know if I managed.

?ÿ

Thanks?ÿ

?ÿ

Regards?ÿ

?ÿ

Paula?ÿ

It's for an older version, but it was a fantastic resource for me:

?ÿ

http://engineeringsurveyor.com/software/starnet-v6-manual.pdf