[X] My Assistant

[djellison]

CODE

4. What EDRs did we request?

Expected EDRs by sequence number and image type:

Sol   Seq.Ver  ETH ESF EDN EFF ERP Tot  Description
----- -------- --- --- --- --- --- ---- -----------
01724 p1550.01 2   0   1   0   0   3    navcam_tau
01724 p1588.03 6   0   6   0   0   12   navcam_cloud_movie_right_eye_pri_57
01724 p2600.12 2   2   0   0   2   6    pancam_tau
01725 p0060.02 40  40  0   0   0   80   photon_transfer_left_navcam
01725 p2601.03 4   2   0   0   2   8    pancam_tau_L78R48
01726 p1588.03 6   0   6   0   0   12   navcam_cloud_movie_right_eye_pri_57
01727 p0061.01 40  40  0   0   0   80   photon_transfer_right_navcam
01728 p0064.01 40  40  0   0   0   80   photon_transfer_left_front_hazcam
01728 p1588.03 6   0   6   0   0   12   navcam_cloud_movie_right_eye_pri_57
01729 p0065.01 40  40  0   0   0   80   photon_transfer_right_front_hazcam
01730 p0066.01 40  40  0   0   0   80   photon_transfer_left_rear_hazcam
01730 p1588.03 6   0   6   0   0   12   navcam_cloud_movie_right_eye_pri_57
01731 p0067.01 40  40  0   0   0   80   photon_transfer_right_rear_hazcam
01732 p0068.02 40  40  0   0   0   80   photon_transfer_mi
01732 p1588.03 6   0   6   0   0   12   navcam_cloud_movie_right_eye_pri_57
01733 p0062.01 40  40  0   0   0   80   photon_transfer_left_pancam
01734 p0063.01 40  40  0   0   0   80   photon_transfer_right_pancam
01734 p1588.03 6   0   6   0   0   12   navcam_cloud_movie_right_eye_pri_57
01736 p1588.03 6   0   6   0   0   12   navcam_cloud_movie_right_eye_pri_57
01738 p1588.03 6   0   6   0   0   12   navcam_cloud_movie_right_eye_pri_57
01740 p1588.03 6   0   6   0   0   12   navcam_cloud_movie_right_eye_pri_57
      Total    422 364 55  0   4   845

Looks like a busy time - the Photon Transfer sequences are interesting, I'll ask some Q's as to what that's about. With a healthy rover, Conjunction must be frustrating. Safe, low data volume, but time consuming sequences are all good

Doug

[dvandorn]

Well, yes, but... it's my understanding that this "shaking" plan actually improved the dust situation on Spirit's mini-TES. So while in Oppy's case the main dust problem may be in the internal optics, it was certainly worth a shot.

-the other Doug

[RoverDriver]

Well, yes, but... it's my understanding that this "shaking" plan actually improved the dust situation on Spirit's mini-TES. So while in Oppy's case the main dust problem may be in the internal optics, it was certainly worth a shot.

-the other Doug

AFAIK the MTES shake was run on the testbed and on MERB but never on MERA. Do you remember what Sol it should have run on MERA or do you have a reference regarding your statement? I'm not arguing with you, I ask only to refine my search and see if and when it was run so I can look up the activity.

On MERB we ran the MTES shake on sol 1680 (for 3 seconds) and 1705 (for 6 seconds) and I thought we were going to do a MTES shake before Conjunction but I see that we didn't. And so far I have not heard that either one resulted in significant improvement on the MTES functionality.

Paolo

[dvandorn]

AFAIK the MTES shake was run on the testbed and on MERB but never on MERA. Do you remember what Sol it should have run on MERA or do you have a reference regarding your statement? I'm not arguing with you, I ask only to refine my search and see if and when it was run so I can look up the activity.

As with many things, I recall reading something but not exactly where and when. My memory is that when the regional dust storm hit at Gusev, there was some update somewhere (surely either posted here or linked to from here) stating that MERA (i.e., Spirit) had just completed a mini-TES shaking and that initial results looked promising. The news was in juxtaposition to the new dust storm, irony in the possibility that just after getting her mini-TES dusted off, a bunch more dust got dumped on the poor girl.

As with anything, I admit the possibility of remembering this incorrectly.

-the other Doug