You might remember that we were planning on releasing HiRISE images to the public on a monthly basis. That plan was delayed by issues with our processing software, hardware and other events. A productive summer working on these issues culminated last week with one of our larger releases of Mars images!  Here are some statistics about our September 2009 release, which includes the images the HiRISE camera took of the Martian surface between Mars Reconnaissance Orbiter (MRO) orbits 12,600 to 14,199, or roughly April 4 through August 6, 2009:

• 2,996 RDRs, 1 TB
• 42,370 EDRs, 1 TB
• 34,481 RDR Extras, 1.6 TB
• 83,784 EDR Extras, 0.02 TB
• 636 Anaglyphs, 0.01 TB

Totals for this release: 163,631 image products, 3.6 TB

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

• 22,676 RDRs, 12 TB
• 317,120 EDRs, 10.4 TB
• 192,270 RDR Extras, 15.3 TB
• 612,769 EDR Extras, 0.1 TB
• 2,892 Anaglyphs, 0.5 TB

Total: 1,148,363 images, 37.5 TB

In summary, we released nearly 1500 observations, most of those with both black & white and color RDR products. Several newer observations matched up with older observations from a slightly different angle of the same location on the surface, resulting in 636 awesome new anaglyphs. The RDRs are the fully processed, geometrically projected products best for scientific inquiry. If you really want to, though, anyone can download and process HiRISE data from scratch. You can do this using ISIS software, which is publicly available for free download. See the ISIS Web site for download information, processing instructions, and tutorials.

Starting this week, I will be looking over the observations taken August 6 through August 26 before MRO went into safe mode and make sure they are ready for release. We plan to release these images in early October. We are also in the process of reprocessing those Extended Science Phase mission images prior to all the latest processing pipeline fixes and updates.  Once we are satisfied with that data set, we will release them to the public and then start reprocessing the images from the Primary Science Phase…a major project that should keep me and the rest of Downlink busy for several months!

Originally posted at Spaced Out (Again):

We are going to try to Twitter a planning cycle for the HiRISE (http://hirise.lpl.arizona.edu) experiment. The idea is to give people a feeling of all the work we have to do to get images from Mars out of a very special piece of equipment. Here are a couple of things you need to know to follow what is going on.

The scientist in charge of the scientific support for the cycle is called the CIPP. For cycle 75, that is @nick_space. Nick will be assisted by his Post-Doc., Anya, who is @mozhetbyt

The targeting specialist ensures that the plan produced can be implemented and keeps the CIPP from doing anything stupid. The targeting specialist is called the HiTS and for cycle 75 that is @laughingrid.

The HiRISE project has its own Twitter account (@HiRISE) which can also be followed.
We will try to use #hitwycle as a search hashtag for tweets.

(more…)

UA job posting website

If you live in Tucson, you might be interested to know that we’re looking for a new HiRISE Targeting Specialist (HiTS) here at HiROC!

Our faithful blog readers are probably already familiar with some of what the HiTS do, but for the rest of you, here are some past entries related to different aspects of the job:

• Welcome, Newbies! – Training other new HiTS
• ESP so far – In the extended mission, things are (supposedly!) easier…
• How big are our feet? – Planning software HiTS use, HiPlan
• High data rate and HiTemp – Some of the challenges of planning images
• Looking Back – Special sequence commanding

I’ve found it to be an exciting and rewarding job, but it’s not an easy one. You need to be the type of person who thrives under pressure; can deal with firm deadlines, but is also creative and self-motivated in between deadlines; pays attention to small details, but can also “see the big picture” (so to speak ). You need to be able to communicate with, and translate between, people with diverse backgrounds and experience, from researchers on the science team to NASA engineers. Ideally, you’d have some relevant scientific background (planetary science, astronomy, or geology, for example), be familiar with UNIX and some programming, and most importantly, be excited about exploring Mars!

To view the complete job description, requirements, and apply online, click this link to the University of Arizona job listing. If you have any questions about the job, please leave them in the comments below!

Remember when I said we would start releasing data monthly to the PDS and public? We decided to work on improving calibration a little bit longer before we reprocess our data and start the monthly releases. Therefore, we are not going to have a June release (except for the usual weekly captioned image releases on Wednesdays), but we are getting closer to a regular monthly release! We are still ahead in our releases per PDS requirements, and we are preparing for the big reprocessing that is coming up. For example, our software pipelines have been updated to better automate reprocessing and we have hired two new student validators who will be responsible for visually inspecting all of the images as they are reprocessed. Training started this week.

Consider the May PDS release our practice run. Thank you for your patience…monthly releases of HiRISE images are indeed coming, but not quite as soon as we expected.

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…)

The first few cycles of the extended science phase (ESP) have been very similar to the previous primary science phase (PSP). The main difference has been that the Observation IDs start with ESP instead of PSP! (like ESP_011268_2485) We’re also adding some warm-up observations on the night side of the planet now, which is adding some extra work in the planning. Luckily (?), Mars is at its farthest distance from the Earth right now, so the data rate is very low. This means fewer images to plan, so we have some extra time to do special things like this.

The next cycle, however, will mark some changes in the way we do the planning process. This is cycle 58 (can you believe it’s been that many cycles since we started??). For most of that time, we’ve been doing things in much the same way. We’ve gotten so good at it that everyone decided they wanted to change everything & mess it all up. haha, just kidding. We’re actually trying to simplify things. Even though we’ve gotten pretty good at this, it’s still an incredibly complex process. We would like to continue doing it for a long time and still remain sane. Also, we expect that our funding will be cut in the future, and we want to make sure we can still do everything even if we have fewer people. Plus, things just wouldn’t feel right if we weren’t constantly changing something!

If you’re interested in the nitty-gritty details, here are some of the things we’re changing: (more…)

The data rate from the Mars Reconnaissance Orbiter (MRO) – in orbit around Mars on the other side of the Sun from our perspective here on the Earth – is set to increase soon, marking the end of solar conjunction and the beginning of MRO’s Extended Science Phase (ESP).  HiRISE will capture the first image of our next phase in Mars exploration this weekend.  Like all first images after the HiRISE camera has been idle for awhile, we will look especially closely for, but do not expect, any issues.

In these days leading up to the beginning of ESP the downlink team is checking our processing software and tools to make sure they are ready for the observation ID prefix change from PSP_XXXXXX_XXXX to ESP_XXXXXX_XXXX. The automated processing pipelines are ready to go.  My own validation and reporting Perl scripts make use of modules that are mission phase aware and pattern match file extensions instead of observation ID prefixes, so I think I am set. Any minor tools we miss can be easily updated as necessary.

With improvements to our tools and new procedures, we can sometimes recover image data previously stuck in the original raw data files. During this quiet period, I had an opportunity to go back to old observations, some from early in the Primary Science Phase (PSP), and recover errant channels that failed our processing software at the time.   This resulted in a few new channels of image data that we will include in a later reprocessing of our images.  For example, PSP_001746_1515 was originally processed without the RED1_0 channel. You can see this channel gap if you click on the observation’s “Full image (grayscale, non-map projected)” link.  An improved mosaic will include most of RED1_0, albeit with a small image data gap near one end.  Why did we not create this channel before?  Sometimes a data gap occurs between channels, obliterating the second channel’s science header.  The software at Jet Propulsion Laboratory’s RSDS that splits our image data into separate raw data channel files cannot figure out where to split the image data correctly within this gap and so image data from two or more channels are trapped in one raw data file.  When this jumbo raw data file hits our EDRgen processing pipeline here in Tucson, Arizona, the tool called HiRISE_Observation became confused when it discovered image data from another channel near the end of the file, and the error it flags halts the EDRgen processing pipeline.

We now have improved tools and procedures for dealing with this problem.  By running HiRISE_Observation outside of the EDRgen pipeline, it will successfully produce an EDR for the first channel before it complains about the second channel’s image data.  While we would love to get at that second (or third, or later!) channel’s image data, right now we recoverthe data that is easiest to reach.  Someday, we might have a tool that will recognize a missing science channel header, reconstruct this header, and then fit the header in correctly between the first channel and the additional channels stuck in one raw data file.

When will you see the new PSP_001746_1515 products, newly improved with the recovered RED1_0 channel?  Hopefully in a few months.  While I have recovered this EDR (as well as EDRs from other observations), we would like to wait to reprocess the entire observation until we have even better image calibration built into our processing pipelines.  It makes little sense for me to reprocess this observation now when we are just going to be reprocessing it again sometime early next year. Once all of our improvements are in place in the upgraded processing pipelines, we will reprocess ALL of our observations, a huge undertaking.

Next week we will be back to our normal downlink activities: making sure the processing pipelines behave, validating new observations, providing daily reports to the rest of the team, and processing color and RDR mosaics.  We will also add in routine creation and validation of anaglyphs and preparation for our next Planetary Data System (PDS) release in March.  The quiet time during solar conjuction was nice, but we are anxious to see new images from Mars!

After the long process of creating the HiGlyph Pipeline (anaglyphs producing software), processing the images through this pipeline and having them all properly validated, we here at HiRISE are proud to present you with a whole mess of anaglyphs (362 of them, to be exact )!

And now, for all of those curious minds out there, a brief overview of the HiGlyph Pipeline:

• Anaglyphs are created in a three-step process. The first step is to take the two images of the stereo pair and map project them. This helps the pipeline determine which image will be the left image and which will be the right image in the anaglyph.

• The second step takes the two images and looks to see if there are any improvements that can be done on them before putting them together. If there are not, the images move on. Often, due to the difference in viewing angle, the two images do not have a 100% overlap. Thus, to make the image a bit neater and easier to see, we trim off the excess portion of the image (the parts that do not overlap) and then assemble them so the left image is the red and the right image is the blue/green.

• The third and final step of this image processing is simply to prepare the images you see here and to update our catalog.

Seems complicated, right? Well luckily we have wonderful programmers that create these intricate programs. All I have to do is create a list of these images and run them through this pipeline. What really makes my job interesting is the validation process!

I have had the pleasure of being able to look at all 362 of the anaglyphs we have released today. But, you might ask, aside from looking super cool in 3-D glasses , what does it take to validate these anaglyphs? Well, at the beginning of this process the student validators and I got to ask that very same question. Since HiRISE has never had software to create images like this before, we played lab rat and came up with an entirely new technique for validation.

• You may notice that when not wearing the 3-D glasses there is a bit of a horizontal shift in the anaglyph. This shift is good because it is what allows us to see the image in 3-D. But, since the map projection of this process is not always spot on, we sometimes wind up with a vertical shift too. This is bad! Since most of us do not have googly eyes, this makes the image very difficult to see. With our validation process, we have to spot this out and fix it so that you do not have to strain your eyes (well… not too much at least ) in order to see the anaglyph.

Well, with that said, I leave you to your regularly scheduled HiRISE browsing! Enjoy!

We’re in the midst of the last cycle in MRO’s Primary Science Phase (PSP). Conjunction is coming up, when Mars is behind the Sun, so we won’t be able to communicate with the spacecraft for a few weeks. We’ll get a welcome break during that time – Uplink will have two whole planning cycles off, and Downlink will get a chance to catch up with their processing.

I can’t believe it’s been two years since the last conjunction and the start of PSP! A lot has changed since we started out with those first images. (more…)

We’ve just released 1008 new HiRISE images to the PDS! (See main page, or click here for the catalog.) This release covers orbits 8200 – 9299 of the primary mission, or in other words, the end of April through the end of July. That means we’re releasing data that’s only about 6 weeks old! This is awesome – I’m so impressed with the downlink team! The amount of work required to process these images is astounding, let alone prepare and post everything for an official release.

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!