ESP_013948_1410, the kind of data we can't wait to get more of!

We are now returning to our normal mode of operations after several long months of being in safe mode. The anomaly on August 26th was the last in a series of computer glitches on board the MRO spacecraft that caused a reboot. The engineering teams have been working incredibly hard to get the anomaly figured out and prevent a possible side-effect from causing really serious problems. While they may not understand the original problem, and there is a chance it may happen again, they’re confident that at least it will not threaten the mission, so they’ve given us the go-ahead to resume normal operations.

Safe mode is a way of running the spacecraft where all of the science instruments are turned off and quiet. We still receive engineering telemetry so we can monitor temperatures and voltages. There are also “survival” heaters that prevent HiRISE from getting too cold in this mode.

During this time, the uplink operations staff has gotten a little restless. (more…)

We have now released all HiRISE images taken prior to August’s spacecraft safe mode event! Here are some statistics about our October 2009 release, which includes the images the HiRISE camera took of the Martian surface between Mars Reconnaissance Orbiter (MRO) orbits 14,200 to 14,499 (August 6, 2009 – August 26, 2009):

• 446 RDRs, 0.18 TB
• 6238 EDRs, 0.18 TB
• 5126 RDR Extras, 0.28 TB
• 12,464 EDR Extras 2.5 GB
• 16 Anaglyphs 0.001 TB

Totals for this release: 24,274 images, 0.62 TB

This brings our total released product numbers and data volume to:

• 23,122 RDRs, 12.2 TB
• 323,358 EDRs, 10.6 TB
• 196,058 RDR Extras, 15.6 TB
• 625,233, EDR Extras, 0.1 TB
• 1,192 Anaglyphs 0.5 TB

Total: 1,167,771 images, 37.7 TB

Just because we are not currently taking images does not mean we are slacking off. The Downlink team is busy reprocessing and validating all ESP observations. After reprocessing, these observations will all benefit from the same improvements we have made to our processing pipelines over the past several months. I also recently started reprocessing PSP observations, which is a much larger data set that will sync improvement to our processing pipelines made over the past few years! We are keeping busy and we are even getting help from the Uplink team while they wait for the go ahead to start taking new images of the Martian surface. Of course we all want that to happen as quickly as possible!

Last week, the MRO spacecraft unexpectedly “safed.” This is when it reboots and puts itself into a precautionary mode; in this case it was in response to an unexpected voltage reading (more information in this press release about the safing). The engineers at JPL and Lockheed Martin spent long hours investigating the cause, making sure the spacecraft is healthy and unharmed (which it does appear to be), and cautiously getting things back to normal. I’ll jump right to the happy ending of the story, which is that we are now back to normal, imaging Mars as usual (here’s the press release about resuming routine operations).

What do the people at the HiRISE Operations Center (HiROC) do when the MRO spacecraft safes?
(more…)

Last week we had a rare event: HiRISE turned off! We call this safe mode, because it’s a safety measure built into the instrument’s software. Whenever any of the sensors starts going out of bounds, like temperatures or voltages, the instrument powers down to prevent damage to the electronics. In this case, one temperature sensor went over its upper limit of 35 degrees Celsius. It’s pretty disconcerting when something unexpected like this happens, but at least we know the instrument is protected.

We had the difficult detective job of figuring out what went wrong. It was clear early on that the instrument overheated, but we couldn’t figure out why. Our tool that predicts the temperatures (”HiTemp”) didn’t predict anything that hot. We didn’t take a really large image, which would heat us up (at least, nothing bigger than normal! ). The local operations team worked with the health & safety people, the spacecraft engineers at LMA, and some of the software developers at Ball Aerospace that originally designed HiRISE. Together we all investigated the problem.

(more…)