Follow along! We’re in the midst of twittering an entire planning cycle, start to finish. Right now we’re in what’s called “IO week 1″, the second week of a 5-week planning process. You can follow the hashtag #hitwycle to see all the updates in real time.

This blog entry describes it in much more detail, from when we tried to do this last fall. Unfortunately, that time the spacecraft went into safe mode, and we had to stop the experiment. Here’s hoping for better luck this time! :\

Cast of characters:

One difference is that this time the CIPP (@nick_space) is here in Tucson. So it’s pretty easy to walk over to his office and ask him a question. Despite that, we’ve actually had a few discussions over twitter instead. Talk about lazy!! The good side of that is that you get to follow the day-to-day planning and see what it’s really like to plan two weeks of HiRISE images!

Links:

HiRISE has been conducting a survey of polar scarps where several dust avalanches were caught in action in the previous Mars year. The first new avalanche found by this campaign can be seen in the images from HiRISE observation ESP_016228_2650.

Questions remain about how these dust avalanches are triggered, though it is believed to be related to the spring warming of CO₂. You can find out more in Patrick Russell’s caption for HiRISE observation PSP_007338_2640.

January was a particularly eventful month for HiRISE. Let’s hit the HiLights (in no particular order).

#1. A special issue of the journal Icarus was devoted entirely to HiRISE. It contains over twenty scientific papers produced using HiRISE as a primary data source, representing years of research by dozens of scientists. You can find out more by reading our press release.

A plot of HiRISE stereo observations in Tharsis and Valles Marinaris

#2. We observed the Phoenix Lander in springtime, as frost slowly melted around its landing site. There was some small hope that Phoenix would be attempting to awake from ‘Lazarus’ mode but evidently the Mars Odyssey orbiter has not heard its signal.

The Phoenix Mars Lander as of January 2010

#3. Our image that captured a dust avalanche on a dune was very popular around the web. Astronomer Phil Plait called it “another dose of Martian awesome” and provided a great analysis on his blog.

Active dust flow caught by HiRISE

#4. Our image of ancient viscous flows on the floor of Mars’s largest impact basin stood out (to me). “HiRISE images are revealing some very strange landforms on the floor of Hellas,” says HiRISE P.I. Alfred McEwen. You can read more in the caption for ‘Contortions on the Floor of Hellas Basin‘.

An section of a Hellas Basin flow in 3-D

#5. Our first DTM’s were released, the initial results of a very labor-intensive process. These precise 3-D maps provide a wealth of information for scientists. But in addition, they will make for very cool simulated fly-over movies. Doug Ellison of UMSF has published some on his youtube page. In a related effort, UMSF user Bernhard Braun produced 3-D HiRISE data using photoclinometry (”shape from shading”).

Doug Ellison’s fly-thru of Candor Chasma

#6. HiWish, our public suggestion page, was made available to great fanfare (thanks). We’ve received over 700 target suggestions in the ten days since launching it, and some of these are already being planned as upcoming observations.

Adding a new target in HiWish on the slopes of Olympus Mons

#7. Mars and Earth made their closest approach of the year, at a distance of about six light minutes. Thus, MRO is in the middle of a high data rate period. HiRISE has been making the most of this, taking 20-30 images per day lately.

Plot of observations received vs. time (includes calibration images)

The response to HiWish has been incredible! We’ve had well over one hundred target suggestions from the public since launch. Here are some more questions and answers that will go in our FAQ.

What are some strategies to improve my suggestion’s chances?

First, make sure you justify the image in terms of small-scale features that might be seen, things like boulders or thin layers or dunes, not giant volcanoes or channels. We need to know how HiRISE’s meter-scale resolution is necessary, especially if there are existing MOC, CTX, HSRC or other images of the area.

Second, choose an appropriate science theme. There are one-sentence descriptions below the map, and detailed descriptions via clicking on the science theme name.

Third, choose a location on Mars that isn’t very popular—avoid regions with lots of other suggestions. Other suggestions are shown with white markers (when you are zoomed in on the map).

How long might it take for my image to be taken and released?

This is very difficult to predict. First, there’s the caveat that we can’t guarantee that we’ll get to it. It depends on how highly a Science Theme Lead prioritizes it. They look at suggestions on a monthly basis. Uplink, downlink and validation are a matter of weeks. And, our PDS releases occur on a monthly basis. So in the absolute best case, it is a matter of months. Remember that you are competing against other suggestions and for the STL’s prioritization.

No doubt you have been introduced to HiWish. We’ve gotten a lot of questions about it, including the following. We’ll add these answers to our FAQ.

My registration failed? What can I do?

We’ve streamlined the registration process, so please try again (with a new username). We do not know the reason why so many people have had trouble registering, but will continue to work on the problem.

Why can’t I save my suggestion? The button is grayed-out!

Please make sure you have provided four things: a title, a science rationale, a region of interest on the map (thick white rectangle with blue marker), and a science theme.

I filled out the suggestion, but can’t get to the next step. What’s wrong?

There should be an error message next to the field that needs to be changed. Typically, this is an invalid character in the title, or something of that nature.

Where Is the Face On Mars?

We have already looked at this in image PSP_003234_2210.

Cydonia

A DTM (or synonymously DEM for Digital Elevation Model) is a grid, or raster, file describing elevation values at regularly spaced points, or posts.

HiRISE DTMs are made from two images of the same area on the ground, taken from different look angles. All the stereo pairs acquired so far are available here. Not all of these have been made into DTMs due to the time-intensive process. Creating a DTM is complicated and involves sophisticated software and a lot of time, both computing time and man-hours.

As mentioned in a previous post, the great advantage of a HiRISE DTM is the high resolution of the source imagery. As a general guide, terrain can be derived at a post spacing about 4X the pixel scale of the input imagery. HiRISE images are usually 0.25 – 0.5 m/pixel, so the post spacing is 1-2 m with vertical precision in the tens of centimeters.

The three basic stages of creating a DTM are:

1. Prepare the images for ingestion into the stereo software
2. Triangulate the images
3. Extract terrain

In order to prepare the images, we must first correct the geometry by removing any optical distortions inherent to HiRISE. Then the spacecraft pointing information at the time of each observation is gathered.

Triangulation is also called bundle adjustment. This step requires the most operator skill and time. The result is a transformation of the original images to epipolar space. What this means is that all the stereo information is now captured in the horizontal direction, or x-parallax. During triangulation, we also align the stereo model to MOLA elevations, so the end result is tied to the global elevation map produced by the MOLA instrument team. This is the same map that you see in the context map pane of every HiRISE observation page.

Once the images are triangulated, then terrain can be extracted. This step is computationally intensive, but automated, so it just takes a lot of computer time. The output of terrain extraction is reviewed for any artifacts or errors. These are edited out if possible. Since editing is extremely time-consuming, it is only done on easily corrected errors and in the areas of most interest to the researcher. The less editing we have to do, the better, so a lot of effort goes into preparing the images so that the input is as high quality as possible. The excellent contrast and value range of HiRISE imagery usually result in high quality terrain extraction that requires minimal editing.

After we have terrain, we can make other products, such as orthoimages. An orthoimage is a picture that has been orthorectified. This means that the pixels have been projected so that at each pixel it is as if you are looking directly down at the terrain. In the original stereo images, we rely on the fact that there are topographical distortions (parallax) to derive the elevations in the terrain model. In the orthoimages, all topographic distortions have been removed.

The final products are map projected using the same mapping definitions as the regular HiRISE RDR products.

A really useful (and cool) thing to do with the orthoimages is to drape them over the terrain for 3D viewing. Below is a subimage from the Newton Gullies DTM showing the imagery draped over the terrain.

You can see animated fly-throughs made with HiRISE DTMs by going to the HiClips page and clicking on the JPL Flythrough Clips. This is a great way to see and understand the geological relationships from a ground perspective.

Researchers use DTMs to take measurements and model geological processes. DTMs are very powerful research tools. In fact, almost every HiRISE DTM produced results in publication. There is a long waiting list for these products because they are so valuable and so difficult to produce. Several institutions involved with HiRISE contribute to DTM production to maximize the number of projects produced and to avoid duplication of effort.

Standard PDS products linked to the DTM project page are usually quite large files. The links provided will download the files to your system. To get a quick view of what the project looks like, click on the Extras links to see a reduced version of the products, displayed as images, grayscale, shaded relief and colorized altimetry.

Standard PDS products:

• The DTM in standard PDS image object (.IMG) format with an embedded label
• The left orthoimage at the same resolution as the DTM, in JPEG2000 format with detached label
• The left orthoimage at the resolution of the original image, in JPEG2000 format with detached label
• The right orthoimage at the same resolution as the DTM, in JPEG2000 format with detached label
• The right orthoimage at the resolution of the original image, in JPEG2000 format with detached label

Extras available in the PDS Extras directory (letters in parentheses correspond to PDS file names such as <Product_ID>.br.jpg):

• Browse (br), annotated browse (ab), and thumbnail (th) jpegs of the DTM as a grayscale image
• Browse (sb), annotated browse (sa), and thumbnail (st) jpegs of the DTM as a shaded relief image
• Browse (cb), annotated browse (ca), and thumbnail (ct) jpegs of the DTM as colorized altimetry
• Browse (br), annotated browse (ab), and thumbnail (th) jpegs of the lower resolution orthoimages

PDS product naming convention for HiRISE DTMs:

PRODUCT_ID = aabcd_xxxxxx_xxxx_yyyyyy_yyyy_Vnn
where
aa = DT, indicating it’s a DTM product
b = type of data

• E = areoid elevations
• 1 = orthoimage pixels from first image
• 2 = orthoimage pixels from second image

c = projection (others are possible but these are the important ones)

• E = Equirectangular
• P = Polar Stereographic

d = grid spacing (think of this as pixel scale in meters)

• A = 0.25 m
• B = 0.5 m
• C = 1.0 m
• D=2.0 m

xxxxxx_xxxx = orbit number and latitude bin from SOURCE_PRODUCT_ID[1]
yyyyyy_yyyy = orbit number and latitude bin from SOURCE_PRODUCT_ID[2]
V = letter indicating producing institution

• U = USGS
• A = University of Arizona
• C = CalTech
• N = NASA Ames
• J = JPL
• O = Ohio State
• Z = other

nn= 2 digit version number

Below is an example of the set of annotated browse images for the Russell Crater Dunes DTM.

The grayscale image of the DTM looks weird, if you have not looked at lots of these before, but keep in mind that the color of the pixels represents elevation. The higher the elevation, the brighter the pixel. Lower elevations are darker. The shaded relief is another way of visualizing the topography. The pixels are illuminated from a certain direction, to show the relief of the topography, rather than the elevation. It is also emphasizes any artifacts in the DTM. In the example here, many artifacts (errors) can be seen such as the faceted areas and boxes in the lower left and top of the image. These artifacts are usually caused by areas of low contrast (such as in this project) or sharply differing shadows. Most HiRISE DTMs will not have a lot of these artifacts, fortunately! The area of most interest to the researcher who requested this DTM was the long slope with the gullies, which was well-illuminated and had good contrast. So in that area, there were few, if any, artifacts. Adding color-coded elevation to the shaded relief creates the colorized altimetry map, where the lowest elevations are purple, green is the median elevation value, and white is the highest elevation. In the Russell Crater Dunes project shown here, the difference in elevation from the highest to the lowest point is almost 590 meters (~1935 ft.). That is a tall dune!!

We are happy to be able to share HiRISE DTMs with the scientific community and with the public. We will continue to release more DTMs as they become available, so stay posted!

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. Read the rest of this entry »

There might not be any new HiRISE images to release (yet) but that does not mean we have been idle here at the HiRISE Operations Center. In fact, we have been very busy improving our existing images with new calibration and a different color stretch, making sure our entire data set is consistent, and preparing new product types!

For starters, our Extended Science Phase (ESP) images are now consistent, making use of all the latest and greatest fixes and improvements to our processing pipelines. These updated products are out now. The older Primary Science Phase (PSP) observations are still reprocessing; we should have them ready for an upcoming monthly release.

Next up, we have a fantastic new product called a Digital Elevation Model. Learn more about these products in an upcoming blog post!

Finally, several of our observations have been improved with updated descriptions.  For example, an image might have been taken of a crater that did not have an official name at that time. After the crater receives an official name, we try to go back and update the description for observations of that crater. Recently we had time to do that for a lot of observations. Unfortunately, the software used to update the EDR and RDR labels inadvertently corrupted the first few image data lines. Our attentive Targeting Specialists and Student Validators spotted the minor differences between reprocessed images and older versions. We have corrected the description update tools and reprocessed the EDRs from the 745 observations affected by this problem. Anyone who has downloaded HiRISE EDRs prior to the December 2009 release should check the list below to ensure any EDRs being worked with are not on this list. If the EDRs you have are from the observations on the list, you can check the “creation date” in their label. If the creation date is before November 4, 2009 then you should download the latest version. If the creation date is after November 4, 2009 then the EDR is good. The latest version of all of the EDRs for the following observations are now available on the PDS and on our website.
Read the rest of this entry »

I just realized our Twitter account has almost 1,000 followers! It’s crazy to think that our words and pictures are going out to that many people every day. Considering how many taxpayers fund this mission, though, a thousand people is only a tiny percentage.

We recently calculated the cost of building and running HiRISE since its inception, and it comes to ~70 million dollars over the last seven years. That sounds like a lot of money to me, but it works out to only 22 CENTS per American! What a bargain! I admit, I’m a little biased, but I think HiRISE’s amazing images, exciting science, and advances in exploration are well worth that investment. The return on that investment isn’t just a matter of the data we get back from Mars – that money goes toward employing engineers, scientists, students, and operations staffers like me. I counted almost 100 people on our team roster that are at least partially supported by HiRISE funds.

Ideally, we’d reach far more than 1,000 people – as “the people’s camera,” we’d love to give every person their 22 cents’ worth. Of course, not everyone uses Twitter, so we try to do other things, like this blog, our website, facebook, on-line learning & activities, and in-person tours and talks.

What else could we be doing? What kinds of things would you like to see us do more of? What’s worth 22 cents to you?

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!