Computed Points not adjusted by DPOS

[Sean Joyce]

On a new project, I took 2 measurements on a control point and averaged them. (autonomous)
Points 2 and 3 are the observations and point 4 is the average of the 2& 3.
I typically average the point right after the observations are taken so it is not overlooked later.
After the DPOS adjustment point 4 has the same unadjusted coordinates from the autonomous survey.
Points 2 & 3 were adjusted.
The averaged point appears to be treated like a design point (no adjustment).
It looks like now I have to go through my recent projects and check for any point adjustment errors.
Any way to fix this so averaged points are treated differently and considered surveyed points ?

 

[Sean Joyce]

Went back on a previous project and found that the averaged points (which I used for a localization) were adjusted by DPOS.
So not sure now how I could make a mistake handling the averaging and the DPOS on the project mentioned above.
On the same project I received 2 slightly different solutions (.02') submitted through the L.S. and same file submitted through
the DPOS website.

 

[Shawn Billings]

Were 2 and 3 observed from the same base session?

 

[Sean Joyce]

Yes same base1 session, point 2 then point 3, after rotating the rod bubble 180 degrees.
I also have another issue that I am trying to figure out.
The total station distance between 1 and 2 agrees with the inverse between the unadjusted grid coordinates.
The inverse using the adjusted grid coordinates disagrees by 0.45'
Scale factor is not the problem.

 

[Shawn Billings]

Can you post a screen shot of the statistics screen for 1 2 3 and 4?

Also what do you mean by adjusted? DPOS or point average? Thanks