Jeremy
"Minimum Fix Count" ? I do not understand the question.
Perhaps you meant the AR ratio?, RTKLIB calls this the "Min. Ratio to
Fix Ambiguity"
If that is correct, and you wish to be "generous" at the expense of
increasing the overall probability of a false Ambiguity Resolution fix
(selecting the wrong set of integers result in an incorrect position),
then use a value like 2.7 or so. Do not go much lower.
[ My limited experience with RTKLIB on this is to leave the value alone
and it does a very good job using a classic comparison of the ratios
method. However this is clearly an area where the tool can be improved,
but I would not expect such improvements to become easily available as
open source. For those that care, the optimal AR process is a very
complex topic, see
https://www.ion.org/publications/search.cfm?searchText=+Ambiguity+Resolution
for a good summary of the key literature, but again now you are into
things rather deep ]
Regards, David Kelley
On 10/15/2014 12:36 AM, jeremy.bouathong wrote:
Hi David,
thanks for your advice. Do you know what is exactly the Minimum Fix Count to
Hold the Ambiguity?
Regards,
Jeremy
_______________________________________________
This message is sent to you from [email protected] mailing list.
Visit http://lists.osgeo.org/mailman/listinfo/foss-gps to manage your
subscription
For more information, check http://wiki.osgeo.org/wiki/FOSS-GPS
