looking at the MER Pancam tracking website.... it seems none of the images for 612 were received, but images from previous sols were? Is this correct? Is Opportunity having more problems?

Sunspot, I've got the same.
And the same results for sols 611 and 610; only images from previous sols were downlinked.

What does it mean? My guess is that the planned sequences -- the ones we see on the tracking web -- were not executed due to any reason, so the data with less priority gets the opportunity to be downlinked.

Let's wait until either Steve or any of the insiders tell us something.

I remember several times in the past when we also did not hear anything from Oppy for a couple of days ... and yet anything was allright.
And I'm confident that this time it will also turn out to be a benign "send pause" ...

However, what really concerns me is yesterday's remark from pando (who is always very well informed):

[quote]
Unfortunately with all the software issues Oppy is experiencing it seems less and less likely that oppy will ever peek into Victoria
[/qoute]

hope, this refers only to the knwon software issue

Some interesting things planned for Sol 613


Sol Seq.Ver ETH ESF EDN EFF ERP Tot Description
--- -------- --- --- --- --- --- ---- -----------
613 p1420.01 0 0 0 0 0 0 hazcam_sunset_imaging
613 p1591.01 0 0 0 0 0 0 navcam_sunset_imaging
613 p2111.05 0 0 0 0 0 0 pancam_cal_targ_L234567Rall
613 p2396.06 0 0 0 0 0 0 pancam_snoopy_3cx1r_L2R2
613 p2539.13 0 0 0 0 0 0 pancam_foreground_L234567Rall
613 p2540.13 0 0 0 0 0 0 pancam_port_survey_L234567Rall
613 p2541.13 0 0 0 0 0 0 pancam_rear_survey_L234567Rall
613 p2600.07 0 0 0 0 0 0 pancam_tau
613 p2600.07 0 0 0 0 0 0 pancam_tau
613 p2694.05 0 0 0 0 0 0 pancam_dust_devil_hunter_waitfor180_L6
613 p2695.05 0 0 0 0 0 0 pancam_sunset_prepoint_L2R2
613 p2696.05 0 0 0 0 0 0 pancam_pre_sunset_L4567R2467
613 Total 0 0 0 0 0 0

The case may be a little bit different, if you are referring to those times in which no data was seen at Exploratorium/JPL sites.
Now we see three days in a row in which none of the planned sequences were executed; at least that is what the tracking website tells us.
Oppy is not silent, actually she is taking the opportunity to download data from previous sols, so the rover is not on "safe-mode".

Let's wait for the data from sol 613 to see if the situation changes.

can you provide a link to that 'tracking website' ive never seen it. thanks.

http://marswatch.astro.cornell.edu/merweb/merweb.pl

Jim said the tracking website was being a little funny a few days ago,

perhaps that is where the problem lies, not on Mars BUt it does look a bit ominous - 611 was a single navcam image to match a Mini TES observation - perhaps that's put a spanner in the works

The latest flight directors report doesn't mention any problems as of Sol 612

The tracking website states that no images have been received for Sol 613 yet

What EDRs do we have on the ground from sol 613?

Actual number of EDRs by sequence number and image type:

Sol Seq.Ver ETH ESF EDN EFF ERP Tot Description
--- -------- --- --- --- --- --- ---- -----------
613 p1420.01 0 0 0 0 0 0 hazcam_sunset_imaging
613 p1591.01 0 0 0 0 0 0 navcam_sunset_imaging
613 p2111.05 0 0 0 0 0 0 pancam_cal_targ_L234567Rall
613 p2396.06 0 0 0 0 0 0 pancam_snoopy_3cx1r_L2R2
613 p2539.13 0 0 0 0 0 0 pancam_foreground_L234567Rall
613 p2540.13 0 0 0 0 0 0 pancam_port_survey_L234567Rall
613 p2541.13 0 0 0 0 0 0 pancam_rear_survey_L234567Rall
613 p2600.07 0 0 0 0 0 0 pancam_tau
613 p2600.07 0 0 0 0 0 0 pancam_tau
613 p2694.05 0 0 0 0 0 0 pancam_dust_devil_hunter_waitfor180_L6
613 p2695.05 0 0 0 0 0 0 pancam_sunset_prepoint_L2R2
613 p2696.05 0 0 0 0 0 0 pancam_pre_sunset_L4567R2467
613 Total 0 0 0 0 0 0

As I read it using the Pancam website....looking back to Sol 608...

608: A driving day was commanded, and at least some of that drive occured (3 of 5 stumble checks)

609: Remote sensing commanded, and executed and downlinked in full
http://qt.exploratorium.edu/mars/opportuni...JLP2537R7M1.JPG

610: Driving sol commanded - no data recieved at all as yet

611: Commanded a single observation
p1950.23 nav_mtes_rvrAz0_ElN45_1bpp_pri57 but not recieved.

612: Driving sol commanded ( same as 610 ) - but again, nothing recieved.

613: Lots of remote sensing commanded but not recieved

614: Some remote sensing commanded

615: Driving day commanded

that is as of sol 613.9

Now - as I see it, they wouldnt have commanded driving and remote obs 2 sols in advance if they didnt think the rover was healthy - BUT - there clearly was a problem on 610. It might be a different link in the chain of course - just new imagery not filtering thru to the DB or the raw image pages, or even a problem with Odyssey perhaps - who knows.

Possible events - 610: Problem with the drive, 611: Rover checkout, MiniTES trouble? 612: Prognosis healthy - command driving, 613: Lots of remote obs with healthy rover 614: Housekeeping to cure 610 problem a little better, and some remote obs, and 615 on the road again.



Doug

I have a slightly different reading on those tracking website reports.
Doug, you are talking about data not received but I think they were actually not executed.

See, for example, sub-section 12 on the same report for sols 610-613:
-----
12. How does what we requested compare with what the rover executed? (be sure PUL's
know, and if important, the PEL. update the SSF list
/home/mersci/pan/B/ops/Sol_all_seq_list.txt as appropriate)

Data products:
Number Number
Number Number Still not (yet)
Sol Seq.Ver Requested Created on Rover Created Description
--- --------- --------- ------- --------- ----------- -----------
610 p0775.03 20 0 0 20 navcam_5x1_az_306_3_bpp
610 p1201.03 4 0 0 4 front_haz_penultimate_1_bpp_crit16
610 p1214.05 4 0 0 4 front_haz_ultimate_4bpp_pri15
610 p1235.04 4 0 0 4 front_hazcam_stumble_0.5_bpp_pri_56
610 p1235.04 4 0 0 4 front_hazcam_stumble_0.5_bpp_pri_56
610 p1235.04 4 0 0 4 front_hazcam_stumble_0.5_bpp_pri_56
610 p1235.04 4 0 0 4 front_hazcam_stumble_0.5_bpp_pri_56
610 p1311.06 4 0 0 4 rear_haz_ultimate_1_bpp_crit18
610 p1335.03 4 0 0 4 rear_hazcam_stumble_0.5_bpp_pri_56
610 p1335.03 4 0 0 4 rear_hazcam_stumble_0.5_bpp_pri_56
610 p1335.03 4 0 0 4 rear_hazcam_stumble_0.5_bpp_pri_56
610 p1335.03 4 0 0 4 rear_hazcam_stumble_0.5_bpp_pri_56
610 p1675.01 20 0 0 20 navcam_5x1_az_126_1_bpp
610 p2627.01 36 0 0 36 pancam_sky_radiance_thumbs_L457R247
611 p1950.23 4 0 0 4 nav_mtes_rvrAz0_ElN45_1bpp_pri57
612 p0773.03 12 0 0 12 navcam_3x1_az_306_3_bpp
612 p1214.05 4 0 0 4 front_haz_ultimate_4bpp_pri15
612 p1215.02 4 0 0 4 front_hazcam_ultimate_0.5_bpp_pri_15
612 p1235.04 4 0 0 4 front_hazcam_stumble_0.5_bpp_pri_56
612 p1235.04 4 0 0 4 front_hazcam_stumble_0.5_bpp_pri_56
612 p1235.04 4 0 0 4 front_hazcam_stumble_0.5_bpp_pri_56
612 p1235.04 4 0 0 4 front_hazcam_stumble_0.5_bpp_pri_56
612 p1305.03 4 0 0 4 rear_haz_penultimate_0.5bpp_pri18
612 p1335.03 4 0 0 4 rear_hazcam_stumble_0.5_bpp_pri_56
612 p1335.03 4 0 0 4 rear_hazcam_stumble_0.5_bpp_pri_56
612 p1335.03 4 0 0 4 rear_hazcam_stumble_0.5_bpp_pri_56
612 p1335.03 4 0 0 4 rear_hazcam_stumble_0.5_bpp_pri_56
612 p1677.03 28 0 0 28 navcam_7x1_az_126_3_bpp
613 p1420.01 4 0 0 4 hazcam_sunset_imaging
613 p1591.01 4 0 0 4 navcam_sunset_imaging
613 p2111.05 28 0 0 28 pancam_cal_targ_L234567Rall
613 p2396.06 14 0 0 14 pancam_snoopy_3cx1r_L2R2
613 p2539.13 28 0 0 28 pancam_foreground_L234567Rall
613 p2540.13 28 0 0 28 pancam_port_survey_L234567Rall
613 p2541.13 28 0 0 28 pancam_rear_survey_L234567Rall
613 p2600.07 6 0 0 6 pancam_tau
613 p2600.07 6 0 0 6 pancam_tau
613 p2694.05 11 0 0 11 pancam_dust_devil_hunter_waitfor180_L6
613 p2696.05 66 0 0 66 pancam_pre_sunset_L4567R2467
614 p2619.07 117 0 0 117 pancam_skysurvhi_L2345678R345678
614 p2627.01 36 0 0 36 pancam_sky_radiance_thumbs_L457R247
Total 584 0 0 584
-----

Nothing has been received until now because there is nothing to downlink. It is fine for sol 614 but being currently on sol 613.9 and without any data reported to be downloaded for 613 is worrysome.

Another possibility (a good one) would be that those reports are out of synch.

Let's see if any insider tells us something new.

Does that include things like engineering data? If there was a problem, I would have thought they would just want engineerig daata rather than science data?

" you are talking about data not received but I think they were actually not executed."

We dont know that. All we know is what was requested, and what was recieved. We dont know that it didnt happen - I'm assuming they didnt execute, or only partially executed, obviously - but we dont actually KNOW that.

Doug

Just looked at the Pancam tracking site... and no Images have been received from Spirit so far this sol.. although I suppose there is still time for them to come down.

6. What unexpected sequences ran? (that is, sequences we did not enter in the SSF
list file /home/mersci/pan/A/ops/Sol_all_seq_list.txt)

Sol Seq.Ver
--- ---------
634 f0006.00
634 f0006.00
634 f0006.00
634 f0006.00
634 f0006.00

Good News I think:

2. What EDRs do we have on the ground from sol 614?

Actual number of EDRs by sequence number and image type:

Sol Seq.Ver ETH ESF EDN EFF ERP Tot Description
--- -------- --- --- --- --- --- ---- -----------
614 p2111.05 13 3 0 0 1 17 pancam_cal_targ_L234567Rall
614 p2111.05 0 0 0 0 0 0 pancam_cal_targ_L234567Rall
614 p2542.13 13 0 0 0 0 13 pancam_santa_anna_L234567Rall
614 p2543.13 4 0 0 0 0 4 pancam_chinook_L234567Rall
614 p2544.13 0 2 0 0 0 2 pancam_scirocco_L234567Rall
614 p2545.13 0 1 0 0 0 1 pancam_mistral_L234567Rall
614 p2546.13 0 0 0 0 0 0 pancam_ostria_L234567Rall
614 p2600.07 2 2 0 0 2 6 pancam_tau
614 p2600.07 0 0 0 0 0 0 pancam_tau
614 p2619.07 0 0 0 0 0 0 pancam_skysurvhi_L2345678R345678
614 p2627.01 0 0 0 0 0 0 pancam_sky_radiance_thumbs_L457R247
614 Total 32 8 0 0 3 43

EDIT: yayyyyyyy some new pictures at exploratorium