Shawn,
That is an awesome explanation.
Jim,
I like the fact that it is red. This is an incredibly rare occurrence you captured. I have never seen it. I would really have liked to have had multiple points there for comparison. I would not be happy with that shot for a property corner or control. I am guessing that you are looking at a 50% chance of a "bad fix" at one half the confidence guard distance. I would liken this to the times during a long duration shot where you are seeing two defined groups of points within 0.12 feet of one another on the Hz scatter plot during collection, just slightly more extreme.
I see that your epochs is set to 900, which is great for DPOS. I like to use a different strategy, which actually involves quite a few more RTK resets overall. I like the ratio of 7 resets, to 45 epochs. My profile just automatically repeats this over and over until I stop it. In the open, for control, I collect 5 of the above shots for each monument, and use cluster averaging. This results in at least 35 re-initializations and 225 epochs per monument. I am seeing absolutely stunning results. I feel that going 900 epoch, without re-initializing the engines is too long.
Because of the above, and my desire for the longest possible file for DPOS, I would like to have an option to Verify with resets, at user definable intervals during a RTK shot. As an example, Once Verify Phase One ends, i want to perform 50 epochs of Phase 2, then begin the Verify Phase 1 process again, when completed, perform 50 more epochs of Phase 2, then Verify Phase 1 again, and on and on.
I seem to remember a comment that Javad made regarding the relationship between engine resets and accuracy. Something along the lines of the solution drifts from the truth the longer the engine remains fixed. I may be mistaken, but that is what I remember.