I am working on a small project - running 3 receivers on 3 points simultaneously.?ÿ Running two R8-3 and one R8-1.?ÿ Processing the baselines in TBC v5.20, and the Tracking Summary in the Baseline Processing Report for 2 of the lines looks normal, but the third looks like this:
The baseline processing stats all look OK, and the data doesn't appear choppy to me.?ÿ I am having a similar issue with a larger project that I just started, and that one has a mix of different receivers.?ÿ This makes me wonder if this is just another TBC glitch and fix is updating to v5.21.?ÿ Anything else I should be looking at?
?ÿ
Edit:?ÿ Tried to edit the title....
?ÿ
Alan
?ÿ
A recent version of TBC changed the way baselines are processed. The new processor looks at the data collected and based on time and distance, the processor changes the epoch interval of your data and starts the processing. Unfortunately, the tracking and processing graphics have not been updated to reflect this change and the tracking summaries look a little disturbing. There is nothing wrong with your data. There is a setting in TBC to turn off the new way of dithering your data, but I don't have TBC loaded to show you where to change the setting, if you want to. For more info, see link below.
https://drive.google.com/file/d/16nktMJR2gUE1NRKVrItKqZnruuLI04mN/view
?ÿ
Tim
Former TBC user...
Tim,
Thanks for that. I was aware of that processor update, but don't know how I've never noticed that tracking graphic before. The test of the "fix" was simple - I just went into the processing settings & switched the Processing Interval from "Automatic" to 5s so all the baselines processed at the same interval & the graphic is back to normal.