• 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!

Here are a few examples of cool images, which were previously unreleased:

• PSP_008248_2640, Polygons and spots on defrosting dunes (right)
• PSP_008269_1395, crazy weird stuff in Hellas Planitia (be sure to look at the whole browse image on this one!)
• PSP_008322_1865, Multiple generations of slope streaks on a crater in Arabia Terra (left)
• PSP_008343_1430, Gullies on mesas in Gorgonum Chaos

I’ve only looked through the first few pages in the release. I know there are a lot more amazing images in there, so if you’re browsing through the images, post some of your favorites below!

This process seems simple in concept, but in practice it is quite complicated. There are three factors to account for:

• Relative timing
• Pixel binning
• Spacecraft jitter

First of all, HiRISE nearly always uses different resolutions for each color. For instance, RED might be at a scale of 25 cm/pixel (bin1) while IR and BG are at 1 meter/pixel (bin4). This “binning” minimizes the amount of data that has to be sent back to Earth, which is the most important constraint that HiRISE needs to deal with. Another reason for binning color is to improve the signal-to-noise ratio (SNR). This means that you can get a better signal by combining pixels at the expense of spatial resolution. In order to get the binned IR and BG images to line up properly, they must be enlarged to match the dimensions of the RED image. For example: RED is bin1, IR and BG are bin2. The RED image will be 2000 pixels wide by 40,000 pixels long (for example), the corresponding IR and BG images will be 1000 pixels wide by 20,000 pixels long. So the first step is to make the dimensions of all three images match.

Now the relative timing is easy to take care of. The start time of all images is a known quantity, and does not change from image to image. We know exactly when the BG detector starts imaging, followed by the RED detector, followed by the IR detector. So the beginning of each image is offset by a fixed amount. Once the images are shifted by this fixed offset (accounting for binning), they will be approximately lined up.

This brings us to the third factor in coregistering images — spacecraft jitter. Because HiRISE is imaging at such a high spatial resolution and at great speed, tiny motions of the MRO spacecraft cause slight variations in where the surface features appear in each of the three color detectors. Imagine that HiRISE is taking a picture of a 1m sized boulder on Mars. If the rock shows up in line 100 of the RED image, and we have already accounted for the relative offsets of the detectors and for binning, then the rock should also show up in line 100 of the BG image. But say we look and it is actually in line 99. Now when we try to stack the two images, the objects in them won’t line up exactly. Our color processing software corrects for this by holding the RED image fixed, and adjusting the corresponding BG and IR images to match it precisely. This is not a perfect process, but most of the time it works extremely well.

Producing the color HiRISE products is not a trivial process. But it is to a point where the processing is automated so new data is released without delay. Enjoy the colorful view!

The HiStitch pipeline combines the matching HiCal products for the same CCD into one more-or-less lined up CCD cube file. HiccdStitch combines these HiStitch cubes into RED, IR, and BG mosaics.

Both pipelines take some time, as overlapping pixels are accounted for and brought together. After these mosaics are created, additional steps create smaller jpeg files for easier viewing, and full-sized jpeg2000 files. We use these jpeg2000 files for validating our images.

There are later pipelines, but we first validate the HiccdStitch products: Did the previous pipelines work correctly? Did the uplink team command the camera correctly? Is there haze or clouds obscuring our view of the surface?

If everything looks good, and we have received the correct reconstructed SPICE ephemeris data, then the geometry pipelines are invoked. These pipelines project the images mathematically to a model of Mars and add geometry data to the images so that each pixel becomes a point on Mars with latitude and longitude coordinates.

The uplink team is constantly looking where to point the camera next. There is a program which is in beta testing now called HiWeb which allows scientists and other people to input suggestions. The Uplink team reviews the suggestions in the database, assigns a priority to each of these suggestions, and then finds when we can point the camera at the part. They also make sure a certain percentage of the upcoming pictures are assigned to look for a Phoenix landing spot, as this is a high priority item at the moment. They are still learning exactly how to best command the camera, and are constantly sharpening their skills.

The downlink team is making sure operations run smoothly at HiROC. They are verifying that the processing has taken place, make sure that the images have been calibrated correctly, that there are no image processing artifacts on the images we are about to release. If there is any artifacts created from processing the image, the source of the problem is identified and fixed, and then the image is reprocessed. While previously we have sent images to the public that had some small processing artifacts during the post-MOI and Transition imaging, we currently are waiting until the images have been completely validated. The downlink team is also taking a quick look at each image that comes down, and making sure there isn’t something unexpected, for example, haze at Mars, lots of saturated pixels, etc. If any such problems are found, they notify the uplink team, to ensure that we don’t have continuing problems. These problems are very rare, but on occasion happen, due to the changing nature of Mars.

During and after the validation process, the images are reviewed by several of the science team members of HiRISE. Things of special nature are noted, and these images receive captions. The others are slated for a more general release. Due to the large size of the HiRISE images, it is almost impossible to search every square inch of the pictures by any one or even a small group of people. I’m sure many of you have noticed this with just the images which have been released, there are many more which are still being validated which have yet to be released.

The Systems team is responsible for making sure that the HiROC computers are all working in top shape. They are quick to find problems when they arise and fix them so that it does not affect the flow of data here. They are preparing servers for two upcoming services that HiROC will provide, HiWeb, which was mentioned previously, and a JPIP server, which will allow for the effective distribution of JPEG 2000 images.

The software team is writing software that will make people’s lives easier. Some are working with the HiPlan suite of tools, which is used to plan upcoming images, to make it even easier to use for the uplink team. Some are working on HiVali, the validation software, which is used to make it easier to verify that an image is ready to release to the public, quickly finding problems with the image. Some are working on HiView, a program which will allow distribution of images over the JPIP protocol to the general public. Still others are working on getting HiWeb ready for public release.

Let me also talk a bit about a few upcoming products mentioned in this entry. HiView will allow you to download only the parts of a HiRISE image that you find most interesting. It will work great, even for those who have slow internet connections. I personally have tested this with a connection rate of 1kBytes/sec, and it works reasonably well even at that slow speed. It will allow the user to save the parts of the image they find the most interesting to their hard drive for future study (HiView will require a constant internet connection to download the image)

Another upcoming product is HiWeb. HiWeb will allow any user (Yes, that’s you!) to suggest future targets to image with the HiRISE camera. Preference is given to targets of scientific interest. The suggestions are given a priority, and placed in a database to be targeted depending on the orbit of MRO and the allocated bandwidth.

So, that’s what’s happening at HiROC these days. In short, we are all very busy, but very much enjoying our work. I personally can’t remember a time that I’ve had as much fun working as these last few months have been. And surely the best is yet to come!

The EDR_Stats pipeline creates a *.cub file from the *.IMG file. These cube files are the file type used in ISIS 3.0, an image processing software package provided for planetary science missions by the United States Geological Survey (USGS). This package contains an entire suite of useful tools, many of which are used by our pipelines.

During the creation of a cube, a variety of statistics are gathered. For example, the number of gaps, saturated pixels, calibration pixels, and other pixels are counted. Image mean, standard deviation, and other statistics are also calculated. EDR_Stats takes these results and uploads them to our database. The resulting cube is archived in our storage directory.

The final EDR_Stats pipeline step lets the next pipeline – HiCal – know that an image channel cube file is ready for calibration processing. Let the cleanup of image data begin!

It is important to note that while there are a multitude of image formats available, Experimental Data Records (EDRs) are a standardized way of packaging planetary science data sets for release to the world while ensuring future access to said data. In the case of HiRISE images, there are two components to an EDR product: (1) the image data and (2) the label.

The EDRgen pipeline uses a program called HiRISE_Observation to create an EDR from the original channel raw data. The image data is converted into a file type with the extension *.IMG and important information about the observation is attached to this *.IMG file in the form of a text label. This label includes information about this mission; the observation name, commanding, time, and temperatures parameters; and other useful information.

After the EDR is created, it is archived in our storage directory hierarchy (we follow a hierarchy that includes mission phase, orbit range, and observation ID). Finally, the database sources table for the next pipeline – EDR_Stats – is updated with the location of the new EDR. Further processing of this EDR, in a different format, is necessary to start cleaning up the image.

How long do each of these pipelines take? HiDog generally downloads a new channel file in a few minutes or less. EDRgen can create a new *.IMG file in a few minutes or less, and we have a few EDRgen pipelines working in parallel. The fact is, most of the pipelines are incredibly fast on our processing cluster. Later pipelines that stitch and mosaic take significantly longer, but rapid progress in computer technology have blown away early conservative estimates of how long HiRISE image processing would take.

Audrie, Tahirih and I did not previously appear in pictures on HiBlog because during transition imaging we were busy working in our offices and Tuvas for some reason did not visit us. We feel so left out (joking)! The three of us make up HiRISE Downlink Operations, which includes downloading new images, processing them, and image validation (the Student Validators also participate in this task). Audrie also works on instrument monitoring and safety. Tahirih also does most of the geometry processing. I also eat cheetos and chocolate cake. When Kite is not busy with HiRISE Uplink tasks – which is generally NEVER – she is blasting her way out of impossible situations that often involve walking carpets.

1. The image is taken by the HiRISE camera, and is stored in up to 28 channels, two for each of the 14 CCD arrays of the camera. Each channel covers about half of the image. Of the 14 CCDs, 10 are red CCDs, two are blue-green, and two are near-infrared. The color CCDs are aligned with the center red CCDs.
2. The image is placed inside a buffer on MRO, awaiting transmission to Earth, along with science data from the other instruments on MRO.
3. The image is received in packets by the Deep Space Network (DSN).
4. After 4 hours of collecting data at the DSN, the Jet Propulsion Laboratory (JPL) puts the packets together for what is known as a “quick look”. The entire image generally has not yet been received by this point in time, but it is enough of the image that it can be processed to take a quick look at it. Subsequently, JPL puts together all of the data it has received every 4 hours and makes it available to the computers at HiROC.
5. After the files have been put together by JPL, then one of the computers at HiROC looks and sees that there is data on the JPL server and copies the data to our system at HiROC. This is the start of what is known as the pipeline, the system of programs at HiROC which process the images. This usually happens either via a direct connection to JPL (slower), or through the Internet 2(Faster, but sometimes can be bogged down).
6. The images are put together into a viewable format, using the minimum processing possible, and create what’s known as an EDR, or Experimental Data Record. This is done without calibration, stitching together the channels, or any other processing, aside from putting the image together. For an image which uses all 14 CCDs, there will be 28 EDRs. These generally speaking are of mainly scientific interest, but they will be released to the general public via the Planetary Database System (PDS). They will be in the standard PDS format.
7. After the EDRs have been created, they are converted to another format for ISIS. ISIS, the Integrated Software for Imagers and Spectrometers is a suite of tools used for processing images for most interplanetary missions, that was developed by the United States Geological Society (USGS). Most of the tools that we use at HiROC for processing our images are written for ISIS files.
8. After the ISIS files have been created, they are calibrated via a program called HiCal. This reduces the inherent noise of the camera to be more consistent with what is being photographed. All digital cameras create some level of noise, and while HiRISE is an extremely good instrument, it still generates a low level of noise.
9. After the individual channels are calibrated, then they proceed to a program called HiStitch, which puts the two channels of the same CCD together. As they are a part of the same CCD, this requires little processing.
10. Next, after each CCD been stitched together, the full CCD images run through a program called HiccdStitch. This program puts the different ccds together, making a mosaic for each color band. This requires some processing, as the ccds slightly overlap, and it can sometimes be difficult to match the different arrays exactly.
11. If the image has not been completely received, then at this point, the pipeline stops, until JPL has received the entire image, or if there are a few confirmed gaps in the image which we haven’t been able to recover. Transmission over the vast distance between Earth and Mars is not easy, and even the best systems have some small error.
12. After the image has been completely stitched together, then the image is geometrically projected. To understand this, realize that the images that HiRISE takes are flat, while Mars is actually round. Geometrical Projection alters the image so that the image points in compass directions, while correcting any distortions that are created by the ellipsoidal shape of Mars. With the geometrical projection images and the right software tools, such as qview for ISIS, the exact distance can be found between two point on the image. In order for this to happen, we must wait for information to be gathered on the exact position of the spacecraft. This is done by the nagivational team, based off of the downlink frequency. This takes two weeks after the picture has been taken, so Geometric Projection might take a while. This is the longest wait point of the operation. An image can be released from predicted information, however, most images will wait for the correct SPICE kernels to be calculated, in order to get the best information. If an image is geometrically projected from predicted information, it will be calculated with the correct info after it has been received.
13. The images are then validated by a team of students known as the HiRISE Validators. They check to make sure that everything in the pipeline worked perfectly, see if there are any gaps in the images, and other similar tasks. If they notice a problem, they contact the HiRISE Operators, who will take steps to resolve the problems, which may include passing part or all of the image through the pipeline again, or tweaking the software to make it work perfectly.
14. The image is converted to a format that the general public can use. Currently that format is JPG, or TIFF, but eventually we will use JPEG 2000.
15. After all of this, the science team members of HiRISE will look at an image to see if there is anything noteworthy. If there is, it is given a caption, and perhaps a press release. If not, it will be posted on the HiRISE website. They are also posted on the MRO website, and occasionally on others.

This process may take as long as a week or two to complete, depending on the load of MRO, scheduling concerns, load at HiROC, etc. The first image took about 9 hours to be completely processed after it was taken by HiRISE. The Victoria Crater picture, taken during a much busier time on MRO, took about 36 hours to make its way to our hands. This was in part due to the larger size of the image, as well as the cache of images already awaiting transmission on MRO to earth. The captions for the images taken during Transition imaging took anywhere from a few hours to a few weeks to write, and this will likely continue to hold. We at HiROC want to release the images we take as fast as possible to the public, and we are doing everything we can to realize this goal. Several shortcuts were taken during the Transistion imaging phase that allowed for images to be released quicker. For Primary Science Phase, this will take a bit longer because these shortcuts will not be taken, but we expect that we will release most images within two weeks after them being taken, shortly after we have finished receiving, processing, and captioning the image.

There are some variations to this process, for example, the Victoria Crater picture was released in a press conference jointly with the Mars Exploration Rovers (MER) team. Also, color images require extensive calibration and take a lot more time. However, this is the general idea. Currently the entire system, except for writing the captions and adding the images to our website, is essentially completely automatic for receiving and processing HiRISE images, due to years of preparation by the HiTECH and HiOPS teams.

Finally, it was at this moment that Steve Squyres (Principal Investigator, Mars Exploration Rovers) called our Chris Okubo and asked for whatever we had in helping plan a rover drive “right now.” Chris O. is normally the most laid back person on the team, which kind of masks the fact that he is a very sharp, hard-working geologist, and somehow also found the time to plan more HiRISE observations than anyone else, by a substantial margin. Chris was at this moment as close to agitated as I’ve ever seen him.

But with some quick work by the Downlink Operations crew (Tahirih in particular), the rover drivers were able to get what they needed, and transmit instructions that would place Opportunity closer to the edge of Victoria Crater.

It seemed to be the dramatic climax to an incredible week.

The color image of Victoria Crater, our first color image from science orbit, is stunning, check it out if you haven’t already!

Shown below is HiRISE’s eagle-eyed view of Opportunity from 168 miles above.