Base Statistics Screens

Kelly Bellis

ME PLS 2099
5PLS
Maybe I'm confused, and not recalling when and where and under which circumstances, but base station stats screens don't look like they used use to look, for example:

Back in February:
GNSS1_01_Base___Rover_Statistics_20160227-06.49.57.png



As compared with the same file "ReDPOSed" seen today:
BASEROVER-STATISTICS_20160519-16.37.04.png


In the "before" example we see much more information relevant to the given file. In the "after" example, its hard to tell that we're even talking about the same .jps file. Is the after example supposed to look like this? That it, showing the time pegged at 19800106?; FIX: No?; No idea of how much shift was made?

Strangely, and after trying to explore and discover what was going on, the stats screen is now showing some additional information; however some of the questions posed earlier linger:
BASEROVER-STATISTICS_20160519-16.54.41.png


I'm also curious why the error ellipse in the after example so incredibly increased in size? There are also unexplained changes, albeit fairly small, in the DPOS-resolved x, y and u.

As this is only my first day looking at JField 2, there's a very good chance that I've gotten something wrong, or misunderstood or is this the way JField 2 is supposed look like. Any help will be appreciated.
 

Vladimir Prasolov

Well-Known Member
JAVAD GNSS
Hi Kelly,

Regarding shift we have beautiful screen with all coordinates. Selected coordinate has coordinate values, but all other shifts from that coordinate:

upload_2016-5-20_11-26-39.png


I would suggest to use that screen. For base/rover statistic screen I will fix input to show shift.
That particular example had bad CORS solution with huge RMS due to that solution is not FIXED.
 

Attachments

  • upload_2016-5-20_11-21-23.png
    upload_2016-5-20_11-21-23.png
    43.7 KB · Views: 332

Kelly Bellis

ME PLS 2099
5PLS
Hello Vladimir,

I will look for that, but I'm still curious why the error ellipse in the after example has so incredibly increased in size? There are also unexplained changes, albeit fairly small, in the DPOS-resolved x, y and u, but more change than I would have anticipated by the possible introduction of precise orbital data.
 

Michael Stazhkov

Developer
JAVAD GNSS
That particular example had bad CORS solution with huge RMS due to that solution is not FIXED.
It can be the bug which Shawn have found. The bug cause wrong solution type and RMS for a current position of the Base point after the "Base Shift". You can check the new PreRelease version 2.0.0.241.
But you need to reprocess the DPOS task.
 

Kelly Bellis

ME PLS 2099
5PLS
It can be the bug which Shawn have found. The bug cause wrong solution type and RMS for a current position of the Base point after the "Base Shift". You can check the new PreRelease version 2.0.0.241.
But you need to reprocess the DPOS task.
Thanks for the reply, but I prefer not to switch back and forth between the most stable release and other versions. I don't mind waiting for this to be fixed and fortunately, this job is finished.
 

Shawn Billings

Shawn Billings
5PLS
ReDPOS the base file and it will repopulate with the correct statistics. I just tested the PreRelease version for this yesterday. It appears the statistics and time are correct now, but the solution type is still unreliable.
 

Kelly Bellis

ME PLS 2099
5PLS
ReDPOS the base file and it will repopulate with the correct statistics. I just tested the PreRelease version for this yesterday. It appears the statistics and time are correct now, but the solution type is still unreliable.
I'm not running the pre-release. I'm running JField 2.0.0.219. No other updates for the stable release appear to be available this morning.
 
Top