SCLK and PositionSensor get out of sync about marsrover HOT 4 OPEN

Matt - not to pressure you into doing something you don't want to - but if you decide you want an issue to look at - this could be a good start.

from marsrover.

roverDevel is where all bugFixes go to.

from marsrover.

2017-12-17 20:42:01,610 [pool-4-thread-1] INFO space.exploration.mars.rover.kernel.SpacecraftClock - Internal time::2016-01-01T03:03:00.000-06:00 sclk of::1/01210:06:41:14:91150
2017-12-17 20:42:07,691 [pool-4-thread-1] INFO space.exploration.mars.rover.kernel.PositionSensor - Houston - this is curiosityActual.ephemerisTime: 5.04889748183912E8
stateCuriosity: -2.21331994261E8
stateCuriosity: -1.12446652913E8
stateCuriosity: -4.1574799206E7
stateCuriosity: 28.484
stateCuriosity: -15.194
stateCuriosity: -7.162
owltMSLEarth: 839.632
stateEarth: 2.2136176861E8
stateEarth: 1.12461782101E8
stateEarth: 4.158039376E7
stateEarth: -28.492
stateEarth: 15.194
stateEarth: 7.163
owltEarthMSL: 839.745
positionEarthWRTCuriosity: 2.2136176861E8
positionEarthWRTCuriosity: 1.12461782101E8
positionEarthWRTCuriosity: 4.158039376E7
owltEarthMSL2: 839.745
angSepHGAEarth: 112.029
utcTime: "2016-01-01~03:08:00"
sol: 1210
sclkValue: " 1/01210:06:46:06:88479"

from marsrover.

for Sol 1210 - in a few seconds the computer clock and the positionSensor clock are 5 minutes apart. With a timeScaleFactor of 60, every second for us means 1 minute for the rover.

This was done so that we wouldn't have to wait 5 minutes for the messages to go back and forth.

from marsrover.