Agreed re dusty seasons, it’s bad timing and a great pity. There have been a number of recent dust devils in Jezero captured by the cameras. One of the image processing nerds on Mastodon posts them occasionally, but they are usually impossible to see in the raw NavCam image sets, as they are so feint, it takes special processing to extract the data. I’ll see if I can find some of his posts and share them here.
There’s a new set of NavCam images just hit the server on sol 1343, complete with a ‘RMC site’ number change (to 63.0000). However a close review of the HazCam images from 1342 and 1343, shows us that the rover is in the exact same place. So I’m assuming it was either a failed drive, or there were issues with the motion sensors at the end of the drive on 1342 that forced a reset. We won’t know the cause either way unless we get one of those rare mission updates, or we wait 6 months and see the mission managers repot in the PDS
Agreed re dusty seasons, it’s bad timing and a great pity. There have been a number of recent dust devils in Jezero captured by the cameras. One of the image processing nerds on Mastodon posts them occasionally, but they are usually impossible to see in the raw NavCam image sets, as they are so feint, it takes special processing to extract the data. I’ll see if I can find some of his posts and share them here.
There’s a new set of NavCam images just hit the server on sol 1343, complete with a ‘RMC site’ number change (to 63.0000). However a close review of the HazCam images from 1342 and 1343, shows us that the rover is in the exact same place. So I’m assuming it was either a failed drive, or there were issues with the motion sensors at the end of the drive on 1342 that forced a reset. We won’t know the cause either way unless we get one of those rare mission updates, or we wait 6 months and see the mission managers repot in the PDS