<?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; mosaic</title>
	<atom:link href="http://hirise.lpl.arizona.edu/HiBlog/tag/mosaic/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>Phoenix support</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2008/05/19/phoenix-support/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2008/05/19/phoenix-support/#comments</comments>
		<pubDate>Tue, 20 May 2008 01:28:45 +0000</pubDate>
		<dc:creator>Ingrid Daubar</dc:creator>
				<category><![CDATA[HiRISE]]></category>
		<category><![CDATA[Operations]]></category>
		<category><![CDATA[Outreach & Education]]></category>
		<category><![CDATA[Phoenix]]></category>
		<category><![CDATA[Special Events]]></category>
		<category><![CDATA[boulders]]></category>
		<category><![CDATA[EDL]]></category>
		<category><![CDATA[Green Valley]]></category>
		<category><![CDATA[landing]]></category>
		<category><![CDATA[mosaic]]></category>
		<category><![CDATA[reconnaissance]]></category>
		<category><![CDATA[Relay]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=180</guid>
		<description><![CDATA[ It seems like we&#8217;ve been preparing for the Phoenix mission for such a long time &#8211; and now it&#8217;s finally close to landing day! T-6 days according to our countdown clock! Things are getting pretty crazy here, and I thought a little overview of how the HiRISE team is supporting the Phoenix mission would [...]]]></description>
			<content:encoded><![CDATA[<p><a href='http://hirise.lpl.arizona.edu/TRA_000894_2475'><img src='http://hirise.lpl.arizona.edu/HiBlog/wp-content/uploads/2008/05/tra_000894_2475_cut.png' alt='TRA_000894_2475 cut-out showing boulders in the northern plains' HEIGHT="200" ALIGN="right" /></a> It seems like we&#8217;ve been preparing for the <a href="http://phoenix.lpl.arizona.edu/">Phoenix</a> mission for such a long time &#8211; and now it&#8217;s finally close to landing day! <strong>T-6 days</strong> according to our countdown clock! Things are getting pretty crazy here, and I thought a little overview of how the HiRISE team is supporting the Phoenix mission would be useful.  </p>
<p>We&#8217;ve been imaging the northern plains for Phoenix since we started our mission (here&#8217;s <a href="http://hirise.lpl.arizona.edu/apotelesmata.php?q=phoenix&#038;order=release_date&#038;submit=Search">a bunch of reconnaissance images on our website</a>). The first images we got back showed lots of scary boulders (a close-up of one of our Transition images shown to the right), so we sampled other areas and searched for a relatively boulder-free landing spot. The area the Phoenix team finally chose is being called the &#8220;<a href="http://en.wikipedia.org/wiki/Green_Valley_%28Mars%29">Green Valley</a>&#8220;, not because of the &#8220;green light = safe to go&#8221; connotation, but rather because some geological maps made of the area happened to use green as the color for the valley. Perhaps coincidentally, <a href="http://maps.google.com/maps?ie=UTF8&#038;oe=utf-8&#038;client=firefox-a&#038;q=Green+Valley,+AZ,+USA&#038;ll=31.966144,-110.983887&#038;spn=1.043873,1.881409&#038;z=9">Green Valley</a> is also a town near Tucson, where both Phoenix and HiRISE are based.  Whatever the reason, I like that the name has a lovely calm, comforting feel.  <img src='http://hirise.lpl.arizona.edu/HiBlog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p><a href='http://hirise.lpl.arizona.edu/HiBlog/wp-content/uploads/2008/05/phoenix_ellipse_mosaicking.png' title='Footprints of mosaic images of Phoenix 3-sigma ellipse'><img src='http://hirise.lpl.arizona.edu/HiBlog/wp-content/uploads/2008/05/phoenix_ellipse_mosaicking.png' alt='Footprints of mosaic images of Phoenix 3-sigma ellipse' height=200 align=left /></a>Once the Phoenix team picked out their <a href="http://planetary.org/news/2007/0125_A_Green_Valley_for_Phoenix.html">landing site</a>, we worked on a high-resolution mosaic of the entire 3-sigma landing ellipse (&#8221;3-sigma&#8221; means there is a 99% probability it will land within this area; see <a href="http://www.planetary.org/blog/article/00001425/">this great blog entry on landing ellipses</a> at the Planetary Society). The Phoenix landing ellipse is shown to the left, along with the footprints of a number of HiRISE images.  (This was before we were quite done with the mosaic.)  These images have helped the Phoenix team characterize the regional geology and assess the safety of the landing site.</p>
<p>In addition to scouting landing sites, we&#8217;re also going to be involved with Phoenix during its prime mission on the ground.  We&#8217;ve been planning and practicing several different ways of cooperating: <span id="more-180"></span></p>
<ul>
<li><strong>Early Imaging:</strong> We are going to attempt to take observations of Phoenix on the ground several times in the first week of the mission.  There are three images planned, two on the first day and one on &#8220;sol 5&#8243;. (The Pheonix mission will be counting time in <a href="http://en.wikipedia.org/wiki/Solar_day">Mars days</a>, or &#8220;sols.&#8221;) Since the first two images are so early, there&#8217;s a good chance we won&#8217;t know quite where it landed yet, so the chances of seeing it are slim.  The sol 5 image should be really good, though &#8211; we&#8217;ll know the exact landing spot by then, plus the image will have ideal lighting conditions and the highest resolution we can get.</li>
<li><strong>Relay:</strong> The <a href="http://mars.jpl.nasa.gov/mro/mission/sc_instru_electra.html">Electra</a> instrument on MRO will relay commands from Earth to the Phoenix lander, and it will relay data from Phoenix back to Earth.  This affects HiRISE only indirectly &#8211; we&#8217;ll be planning our science imaging around the times Electra needs to be communicating with Phoenix.	</li>
<li><strong>Cooperative Science:</strong> Phoenix and MRO have been planning coordinated science observations using different instruments on both missions.  For example, when Phoenix takes a measurement of the amount of ice on the ground, they might want an image from HiRISE at the same time, to see how much frost is visible in the surrounding area.
</li>
</ul>
<p>Landing will be just the beginning of all these exciting activities.  Come join us for a public celebration on landing day, May 25th! There are all sorts of events planned:<br />
<center> <a href="http://www.lpl.arizona.edu/calendar/calendar.php?ID=107">http://www.lpl.arizona.edu/calendar/calendar.php?ID=107</a></center></p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2008/05/19/phoenix-support/feed/</wfw:commentRss>
		<slash:comments>1</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>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>
	</channel>
</rss>

