<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>HiBlog: HiRISE Team Blog &#187; validation</title>
	<atom:link href="http://hirise.lpl.arizona.edu/HiBlog/tag/validation/feed/" rel="self" type="application/rss+xml" />
	<link>http://hirise.lpl.arizona.edu/HiBlog</link>
	<description>High Resolution Imaging Science Experiment</description>
	<lastBuildDate>Tue, 08 Nov 2011 23:39:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Validation</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2006/12/14/validation/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2006/12/14/validation/#comments</comments>
		<pubDate>Fri, 15 Dec 2006 06:28:45 +0000</pubDate>
		<dc:creator>Tuvas</dc:creator>
				<category><![CDATA[Downlink]]></category>
		<category><![CDATA[HiRISE]]></category>
		<category><![CDATA[People]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[calibration]]></category>
		<category><![CDATA[caption]]></category>
		<category><![CDATA[commanding]]></category>
		<category><![CDATA[dust storm]]></category>
		<category><![CDATA[EDR]]></category>
		<category><![CDATA[gap]]></category>
		<category><![CDATA[haze]]></category>
		<category><![CDATA[HiVali]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[student]]></category>
		<category><![CDATA[University of Arizona]]></category>
		<category><![CDATA[validation]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=65</guid>
		<description><![CDATA[I thought I&#8217;d offer a few more words as to what is done with images at HiROC. Validation has been mentioned in the blog, and I&#8217;d like to explain a bit more about that. I&#8217;ve been involved in writing the primary validation tool, HiVali, and I will be the primary student validator for the next [...]]]></description>
			<content:encoded><![CDATA[<p>I thought I&#8217;d offer a few more words as to what is done with images at HiROC. Validation has been mentioned in the blog, and I&#8217;d like to explain a bit more about that. I&#8217;ve been involved in writing the primary validation tool, HiVali, and I will be the primary student validator for the next month. (The regular student validators are from out of state, and are going home for the Christmas holidays. I&#8217;m from around here, and offered my services to look at pretty pictures from Mars all day;-))</p>
<p><span id="more-65"></span>There are three stages to validation: quick look validation, in-depth validation, and geometric validation. Most of the validation is done by undergraduate students in a variety of departments from the University of Arizona. If they notice something odd, they flag it and notify the full-time operations team, who do a more detailed analysis. Currently there are two students who work solely with validation, and me. I volunteer when their work load becomes heavy (normally I work as a programmer for different software needed at HiROC).</p>
<p>The first stage is to let the staff at HiROC know quickly if there is any problem in commanding, or if there is haze in the field of view. Low resolution &#8220;browse&#8221; images that have come down in the last 24 hours are examined by someone (usually either myself or RichardLeis) to see if there is anything obviously wrong. If there is suspicion, a flag is raised and then other people will take a look at the images. This quick look helps prevent any commanding issues from continuing, and also helps us avoid taking more pictures in areas with some kind of atmospheric distortions (&#8221;haze&#8221;). This could include dust storms, clouds, melting ice caps in the polar regions, etc.</p>
<p>The second stage of more in-depth analysis involves a tool called HiVali. This tool allows one to quickly take a look at an image in more detail, and see if there are any kinds of problems with it. It reports statistics of pixels to see if there is saturation or low contrast. It checks to see if there are any gaps in the image, and other kinds of routine image checks. One part of this process, the part that takes the most time, is the visual validation, where a human physically looks at every inch of the picture in high resolution to see if there is anything odd.  These are usually things which can be fixed in the calibration processing.</p>
<p>The third stage is also a quick look, which is done after the image has been geometrically projected. If something is found that is strange in this stage, then the geometric processing is re-done to correct the error. If the image is in good condition, then many of the intermediary files are marked for deletion. Note that the EDRs and the final products are always kept, but there are several stages to the pipeline, as readers of this blog will know.</p>
<p>Sometime during this process, science team members also look at the image, to find if there is anything of special interest in the image. If there is, a caption is written, and it is prepared for the next batch of images to be released. If not, the image may be released without a special caption. All images will be released within 6 months of being taken. Once everything is perfected at HiROC, this release time will be reduced greatly, perhaps even to a few weeks. Currently, though, we are still working on the process of getting the images released.</p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2006/12/14/validation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stitch</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2006/12/10/stitch/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2006/12/10/stitch/#comments</comments>
		<pubDate>Sun, 10 Dec 2006 23:05:21 +0000</pubDate>
		<dc:creator>RichardLeis</dc:creator>
				<category><![CDATA[Downlink]]></category>
		<category><![CDATA[HiRISE]]></category>
		<category><![CDATA[Images & Science]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[CCD]]></category>
		<category><![CDATA[geometry]]></category>
		<category><![CDATA[HiCal]]></category>
		<category><![CDATA[HiccdStitch]]></category>
		<category><![CDATA[HiStitch]]></category>
		<category><![CDATA[JPEG2000]]></category>
		<category><![CDATA[mosaic]]></category>
		<category><![CDATA[pipeline]]></category>
		<category><![CDATA[pixel]]></category>
		<category><![CDATA[processing]]></category>
		<category><![CDATA[SPICE]]></category>
		<category><![CDATA[validation]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=64</guid>
		<description><![CDATA[To conclude our exploration of the pipelines that take raw channel files and create a beautiful, unmapped mosaic, let me introduce the Stitch pipelines:  HiStitch and HiccdStitch.
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, [...]]]></description>
			<content:encoded><![CDATA[<p>To conclude our exploration of the pipelines that take raw channel files and create a beautiful, unmapped mosaic, let me introduce the Stitch pipelines:  HiStitch and HiccdStitch.</p>
<p>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.</p>
<p>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.</p>
<p>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?</p>
<p>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.</p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2006/12/10/stitch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PSP activities</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2006/12/08/psp-activities/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2006/12/08/psp-activities/#comments</comments>
		<pubDate>Fri, 08 Dec 2006 18:17:29 +0000</pubDate>
		<dc:creator>Tuvas</dc:creator>
				<category><![CDATA[HiRISE]]></category>
		<category><![CDATA[Operations]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[calibration]]></category>
		<category><![CDATA[caption]]></category>
		<category><![CDATA[commanding]]></category>
		<category><![CDATA[HiPlan]]></category>
		<category><![CDATA[HiVali]]></category>
		<category><![CDATA[HiView]]></category>
		<category><![CDATA[HiWeb]]></category>
		<category><![CDATA[JPEG2000]]></category>
		<category><![CDATA[JPIP]]></category>
		<category><![CDATA[Phoenix]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[processing]]></category>
		<category><![CDATA[PSP]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[reprocessing]]></category>
		<category><![CDATA[suggestion]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[validation]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=63</guid>
		<description><![CDATA[Well, it&#8217;s been a while since we&#8217;ve been posting a lot, so I thought I&#8217;d just give you guys some kind of an idea as to what we&#8217;re doing these days.
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 [...]]]></description>
			<content:encoded><![CDATA[<p>Well, it&#8217;s been a while since we&#8217;ve been posting a lot, so I thought I&#8217;d just give you guys some kind of an idea as to what we&#8217;re doing these days.</p>
<p>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.</p>
<p>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&#8217;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&#8217;t have continuing problems. These problems are very rare, but on occasion happen, due to the changing nature of Mars.<span id="more-63"></span></p>
<p>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&#8217;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.</p>
<p>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.</p>
<p>The software team is writing software that will make people&#8217;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.</p>
<p>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)</p>
<p>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.</p>
<p>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!</p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2006/12/08/psp-activities/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Data Arriving, Release As Soon As Possible</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2006/11/08/data-arriving-release-as-soon-as-possible/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2006/11/08/data-arriving-release-as-soon-as-possible/#comments</comments>
		<pubDate>Thu, 09 Nov 2006 04:16:29 +0000</pubDate>
		<dc:creator>RichardLeis</dc:creator>
				<category><![CDATA[Downlink]]></category>
		<category><![CDATA[HiRISE]]></category>
		<category><![CDATA[Images & Science]]></category>
		<category><![CDATA[Releases]]></category>
		<category><![CDATA[browse]]></category>
		<category><![CDATA[caption]]></category>
		<category><![CDATA[ExpressView]]></category>
		<category><![CDATA[geometry]]></category>
		<category><![CDATA[JPEG2000]]></category>
		<category><![CDATA[pipeline]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[SPICE]]></category>
		<category><![CDATA[validation]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=53</guid>
		<description><![CDATA[The first HiRISE image data of the Primary Science Phase (PSP) arrived in Tucson last night sometime around 9 PM.  Although we thought the first data might not arrive until early this morning, I was a little antsy and took a look from home around 9:40 PM to see a complete first observation ready [...]]]></description>
			<content:encoded><![CDATA[<p>The first HiRISE image data of the Primary Science Phase (PSP) arrived in Tucson last night sometime around 9 PM.  Although we thought the first data might not arrive until early this morning, I was a little antsy and took a look from home around 9:40 PM to see a complete first observation ready for validation.</p>
<p>We are waiting for reconstructed <a href="http://naif.jpl.nasa.gov/naif/">SPICE</a> ephemeris data, which comes out every Wednesday &#8211; starting next week &#8211; before sending these data through our geometry pipelines, and ultimately releasing them to the scientific community and public.  Last time, we forced images through our geometry pipelines using predicted SPICE kernels; we do not want to double our workload by continuing that practice.  The SPICE kernels released next Wednesday will cover some of the images captured this week.</p>
<p>Once the images have been visually and statistically validated and the matching SPICE kernels have arrived, one of the downlink folks will send the images through the geometry pipelines.  We also need to get a select group of captions written and automatic caption information generated for the rest.</p>
<p>We are producing JPEG2000 products now in addition to smaller jpeg browse images, to be ready for our viewing client when it is ready for public release.  However, there are many different JPEG2000 viewers and plugins already out there to start practicing with.  One example is <a href="http://www.lizardtech.com/download/dl_options.php?page=viewers">ExpressView</a> from LizardTech.</p>
<p>Once we are on a roll, the data release will be steady and no one will be able to keep up with the wealth of Mars data coming in.  Until the first public release of PSP images, we will try to provide here on HiBlog more details about the many tasks that must still be completed.</p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2006/11/08/data-arriving-release-as-soon-as-possible/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HiYah!</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2006/10/27/hiyah/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2006/10/27/hiyah/#comments</comments>
		<pubDate>Fri, 27 Oct 2006 22:04:54 +0000</pubDate>
		<dc:creator>RichardLeis</dc:creator>
				<category><![CDATA[HiRISE]]></category>
		<category><![CDATA[Operations]]></category>
		<category><![CDATA[People]]></category>
		<category><![CDATA[cheetos]]></category>
		<category><![CDATA[geometry]]></category>
		<category><![CDATA[instrument monitoring]]></category>
		<category><![CDATA[Princess Leia]]></category>
		<category><![CDATA[processing]]></category>
		<category><![CDATA[validation]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=47</guid>
		<description><![CDATA[
I decided the blog does not have enough pictures, so a few of us gathered around a MacBook Pro and said &#8220;Cheetos!&#8221;.   Audrie is on the left, I&#8217;m next, Kite is next to me, and Tahirih is on the right.  Yes, Kite has Princess Leia hair.  No, I&#8217;m not a nerf [...]]]></description>
			<content:encoded><![CDATA[<p><img alt="Tahirih, Kite, Richard, and Audrie at HiRISE" src="http://pirlwww.lpl.arizona.edu/~rleis/graphics/hiops.jpg" /><br />
I decided the blog does not have enough pictures, so a few of us gathered around a MacBook Pro and said &#8220;Cheetos!&#8221;.   Audrie is on the left, I&#8217;m next, Kite is next to me, and Tahirih is on the right.  Yes, Kite has Princess Leia hair.  No, I&#8217;m not a nerf herder.  Who&#8217;s scruffy-looking?</p>
<p>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 &#8211; which is generally NEVER &#8211; she is blasting her way out of impossible situations that often involve walking carpets.</p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2006/10/27/hiyah/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Processing images at HiROC</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2006/10/13/processing-images-at-hiroc/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2006/10/13/processing-images-at-hiroc/#comments</comments>
		<pubDate>Fri, 13 Oct 2006 17:26:37 +0000</pubDate>
		<dc:creator>Tuvas</dc:creator>
				<category><![CDATA[Downlink]]></category>
		<category><![CDATA[HiRISE]]></category>
		<category><![CDATA[Images & Science]]></category>
		<category><![CDATA[Releases]]></category>
		<category><![CDATA[caption]]></category>
		<category><![CDATA[CCD]]></category>
		<category><![CDATA[DSN]]></category>
		<category><![CDATA[EDR]]></category>
		<category><![CDATA[gap]]></category>
		<category><![CDATA[geometry]]></category>
		<category><![CDATA[HiCal]]></category>
		<category><![CDATA[HiccdStitch]]></category>
		<category><![CDATA[HiStitch]]></category>
		<category><![CDATA[Internet 2]]></category>
		<category><![CDATA[ISIS]]></category>
		<category><![CDATA[JPEG2000]]></category>
		<category><![CDATA[MER]]></category>
		<category><![CDATA[mosaic]]></category>
		<category><![CDATA[noise]]></category>
		<category><![CDATA[PDS]]></category>
		<category><![CDATA[pipeline]]></category>
		<category><![CDATA[processing]]></category>
		<category><![CDATA[projection]]></category>
		<category><![CDATA[PSP]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[rover]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[SPICE]]></category>
		<category><![CDATA[validation]]></category>
		<category><![CDATA[Victoria Crater]]></category>
		<category><![CDATA[Website]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=45</guid>
		<description><![CDATA[Some of you out there may be asking: what happens to a HiRISE image between the time that it is taken and the time that it is released to the public? Well, I&#8217;d like to give a summary here.


The image is taken by the HiRISE camera, and is stored in up to 28 channels, two [...]]]></description>
			<content:encoded><![CDATA[<p>Some of you out there may be asking: what happens to a HiRISE image between the time that it is taken and the time that it is released to the public? Well, I&#8217;d like to give a summary here.</p>
<p><span id="more-45"></span></p>
<ol>
<li>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.</li>
<li>The image is placed inside a buffer on MRO, awaiting transmission to Earth, along with science data from the other instruments on MRO.</li>
<li>The image is received in packets by the Deep Space Network (<a title="Deep Space Network" href="http://deepspace.jpl.nasa.gov/dsn/">DSN</a>).</li>
<li>After 4 hours of collecting data at the DSN, the Jet Propulsion Laboratory (<a title="JPL website" href="http://www.jpl.nasa.gov/">JPL</a>) puts the packets together for what is known as a &#8220;quick look&#8221;. 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.</li>
<li>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<strong> </strong>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 <a href="http://www.internet2.edu/">Internet 2</a>(Faster, but sometimes can be bogged down).</li>
<li>The images are put together into a viewable format, using the minimum processing possible, and create what&#8217;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 (<a title="PDS website" href="http://pds.jpl.nasa.gov/">PDS</a>). They will be in the<strong> </strong>standard PDS format<strong>.</strong></li>
<li>After the EDRs have been created, they are converted to another format for ISIS. <a title="ISIS website" href="http://isis.astrogeology.usgs.gov/">ISIS</a>, 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 (<a title="USGS website" href="http://www.usgs.gov/">USGS</a>). Most of the tools that we use at HiROC for processing our images are written for ISIS files.</li>
<li>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<strong>.</strong></li>
<li>After the individual channels are calibrated, then they proceed to a program called HiStitch, which puts<strong> </strong>the two channels of the same CCD together. As they are a part of the same CCD, this requires little processing.</li>
<li>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.</li>
<li>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&#8217;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.</li>
<li>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.</li>
<li>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.</li>
<li>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.</li>
<li>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 <a href="http://hirise.lpl.arizona.edu/">HiRISE website. </a>They are also posted on the <a title="Planetary Photojournal" href="http://mars.jpl.nasa.gov/mro/">MRO website</a>, and occasionally on others.</li>
</ol>
<p>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.</p>
<p>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.</p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2006/10/13/processing-images-at-hiroc/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Downlink &#8211; We Have a Routine?</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2006/10/01/downlink-we-have-a-routine/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2006/10/01/downlink-we-have-a-routine/#comments</comments>
		<pubDate>Mon, 02 Oct 2006 06:49:16 +0000</pubDate>
		<dc:creator>RichardLeis</dc:creator>
				<category><![CDATA[Downlink]]></category>
		<category><![CDATA[HiRISE]]></category>
		<category><![CDATA[Interesting images]]></category>
		<category><![CDATA[Transition Imaging]]></category>
		<category><![CDATA[boulder]]></category>
		<category><![CDATA[cheetos]]></category>
		<category><![CDATA[commanding]]></category>
		<category><![CDATA[dust]]></category>
		<category><![CDATA[frost]]></category>
		<category><![CDATA[gap]]></category>
		<category><![CDATA[ice]]></category>
		<category><![CDATA[layering]]></category>
		<category><![CDATA[North Pole]]></category>
		<category><![CDATA[processing]]></category>
		<category><![CDATA[resolution]]></category>
		<category><![CDATA[validation]]></category>
		<category><![CDATA[water]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=38</guid>
		<description><![CDATA[My new temporary daily routine here at HiRISE Operations:

Validate the image data that have arrived since last time I checked. Are the raw image files we receive gap-free and are the file sizes as expected? Did the Uplink team command the HiRISE camera properly? So far, they have a perfect record!
Keep checking to see if [...]]]></description>
			<content:encoded><![CDATA[<p>My new temporary daily routine here at HiRISE Operations:</p>
<ol>
<li><strong>Validate the image data that have arrived since last time I checked.</strong> Are the raw image files we receive gap-free and are the file sizes as expected? Did the Uplink team command the HiRISE camera properly? So far, they have a perfect record!</li>
<li><strong>Keep checking to see if new data is arriving for processing.</strong></li>
<li><strong>Are our automated processes running properly?</strong></li>
<li><strong>Is the data being stored correctly and can the team access the images in the appropriate places?</strong></li>
<li>Finally!  <strong>Actually look at the new images.</strong>  In between &#8220;oohs&#8221; and &#8220;ahhs&#8221; check to see that the images look good.  Did our automated software handle the data correctly?  Do I need to do any manual reprocessing of image data?</li>
<li><strong>Report my findings to the team via email.</strong></li>
<li><strong>Get up and see what the scientists and other team members are up to.</strong></li>
<li><strong>Eat some Cheetos.</strong></li>
<li><strong>Repeat as necessary.</strong></li>
<li><strong>A million other tasks.<br />
</strong></li>
</ol>
<p>By the end of the day I am covered in Cheeto dust (joking) and amazed by some new vista of Mars (seriously).</p>
<p>What is it we find so amazing?  I can only speak for myself, but in observation <a href="http://hiroc.lpl.arizona.edu/images/TRA/TRA_000823_1720/">TRA_000823_1720</a>, the boulders lying about casting shadows indicate just how &#8220;Hi&#8221; resolution the HiRISE camera can go.  In the second observation  &#8211; <a href="http://hiroc.lpl.arizona.edu/images/TRA/TRA_000825_2665/">TRA_000825_2665</a> &#8211; the stack of water ice and dust layers and the patches of water frost make for a distinctive landscape.  At this resolution, there is a marked difference between the north polar region on Mars and the pictures I have seen of the Earth&#8217;s own polar regions.</p>
<p>To me, this is the great joy of planetary science:  seeing new vistas that are at once familiar and unfamiliar, and never, ever routine.</p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2006/10/01/downlink-we-have-a-routine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

