<?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; projection</title>
	<atom:link href="http://hirise.lpl.arizona.edu/HiBlog/tag/projection/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>DIY Wallpapering</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2008/12/18/diy-wallpapering/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2008/12/18/diy-wallpapering/#comments</comments>
		<pubDate>Thu, 18 Dec 2008 21:45:15 +0000</pubDate>
		<dc:creator>Ingrid Daubar</dc:creator>
				<category><![CDATA[Images & Science]]></category>
		<category><![CDATA[Releases]]></category>
		<category><![CDATA[Website]]></category>
		<category><![CDATA[caption]]></category>
		<category><![CDATA[Color]]></category>
		<category><![CDATA[IAS viewer]]></category>
		<category><![CDATA[product]]></category>
		<category><![CDATA[projection]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[wallpaper]]></category>
		<category><![CDATA[weekly release]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=223</guid>
		<description><![CDATA[ One of our blog readers asked about the wallpapers we post on our website for some of our released images. If you haven&#8217;t seen these, they&#8217;re linked over on the lower right of pages like this. Many different sizes are available, from 800&#215;600 all the way up to 2560&#215;1600 (for lucky people with ginormous [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://hirise.lpl.arizona.edu/PSP_009717_2545"><img src="http://hirise.lpl.arizona.edu/images/wallpaper/800/PSP_009717_2545.jpg" alt="PSP_009717_2545" align="left" height=200 /></a> One of our blog readers <a href="http://hirise.lpl.arizona.edu/HiBlog/?p=206">asked about</a> the wallpapers we post on our website for some of our released images. If you haven&#8217;t seen these, they&#8217;re linked over on the lower right of pages <a href="http://hirise.lpl.arizona.edu/PSP_009717_2545">like this</a>. Many different sizes are available, from 800&#215;600 all the way up to 2560&#215;1600 (for lucky people with ginormous monitors), so you can choose the right size for your screen resolution.</p>
<p>Our masterful web master creates these wallpapers for each of our weekly captioned releases (these are the images we release each week with some commentary written by the science team). He picks out an interesting area from each image and produces custom cutouts in different sizes. We provide these extra files because we think the images are so beautiful, everyone should have them on their desktop.  <img src='http://hirise.lpl.arizona.edu/HiBlog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   Because they&#8217;re all done by hand, though, we unfortunately don&#8217;t have the resources to make these special products for every single image. For example, most of the 1,642 images we released in our big <a href="http://hirise.lpl.arizona.edu/releases/dec_08.php">December PDS release</a> don&#8217;t have wallpapers. However, you can make your own, and here&#8217;s how!<br />
<span id="more-223"></span></p>
<p>I make my own wallpapers all the time, so I can see the images that I planned. You can make your own, too &#8211; it&#8217;s really easy.  They&#8217;re basically just screenshots, zoomed in on a part of the image at high resolution.  If you&#8217;ve never done that before, here are instructions for one way to do it.</p>
<p>Let&#8217;s say you&#8217;re enamored with <a href="http://hirise.lpl.arizona.edu/PSP_009308_2295">this image of Phlegra Montes (PSP_009308_2295)</a>, which was part of our PDS release, but it doesn&#8217;t have any wallpapers. There are a few ways to do this. The one we recommend (and the one I personally use) is the IAS Viewer.  We&#8217;ve talked about this tool <a href="http://hirise.lpl.arizona.edu/HiBlog/?tag=ias-viewer">quite a few times on this blog</a>, but here&#8217;s a short step-by-step in case you&#8217;re new to this tool:</p>
<ol>
<li> On the image page, click on <strong>JP2 QUICKLOOK (IAS Viewer)</strong>, and a menu will drop down showing the available products.
</li>
<li> Click on the product you want.
<ul>
<li> Personally, I like <strong>color</strong>, but that&#8217;s only in the middle of the observation. If you want to see the entire field of view, get the <strong>grayscale</strong>, which includes all of our red-filter CCDs. <strong>Map-projected</strong> products will have the image oriented so that North is up &#8211; I prefer this because then the shadows appear to my eyes to be in the &#8220;right&#8221; direction. In this example, I chose <u>IRB color (map projected)</u> </li>
</ul>
</li>
<li> You&#8217;ll get a popup window asking you to verify the certificate &#8211; click <strong>Trust</strong>.</li>
<li> The IAS Viewer will open.  Make this as big as you can fit on your screen. Make the image that opened as big as you can fit, too.</li>
<li> <strong>Zoom</strong> (magnifying glass with plus) and <strong>pan</strong> (scroll bars, hand tool, or Overview map at top left) until you like the view.  Don&#8217;t forget to <a href="http://hirise.lpl.arizona.edu/HiBlog/?p=102">re-stretch</a>!
<ul>
<li> The resolution is shown in the bottom of the viewer &#8211; <strong>1&#215;8</strong> means it&#8217;s eight times reduced, <strong>2x</strong> means it&#8217;s zoomed in to twice the full resolution, etc.</li>
<li> Make sure you zoom in to full-resolution (<strong>1&#215;1</strong>) at least once, because it&#8217;s awesome! </li>
</ul>
</li>
<p><a href='http://hirise.lpl.arizona.edu/HiBlog/wp-content/uploads/2008/12/psp_009308_2295_test_wallpaper.jpg' title='Test Wallpaper'><img src='http://hirise.lpl.arizona.edu/HiBlog/wp-content/uploads/2008/12/psp_009308_2295_test_wallpaper.jpg' alt='Test Wallpaper' height=200 align=right /></a></p>
<li> Save the view to a JPG file (disk button). It might look something like the one to the right.
</li>
<li> <em>(optional)</em> Open the JPG file in another application, such as Photoshop or GraphicConverter to do additional stretching or processing.  For example, you might want to tweak the color or contrast to your particular taste.
</li>
<li> Use that file as your wallpaper or screensaver, or both!
</li>
</ol>
<p><strong>Caution:</strong> Doing this may lead you to spend WAY too much time looking at beautiful HiRISE images and making wallpaper!  <img src='http://hirise.lpl.arizona.edu/HiBlog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   You&#8217;ll find that you can make many, <em>many</em> unique full-resolution wallpapers out of a single HiRISE image!</p>
<p><em><br />
Thanks to the webmaster for help in writing this, as well as for all the outstanding wallpapers he&#8217;s already produced!</em></p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2008/12/18/diy-wallpapering/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Image Fest #3</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2008/03/18/image-fest-3/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2008/03/18/image-fest-3/#comments</comments>
		<pubDate>Tue, 18 Mar 2008 17:29:42 +0000</pubDate>
		<dc:creator>GuyMac</dc:creator>
				<category><![CDATA[Color]]></category>
		<category><![CDATA[HiRISE]]></category>
		<category><![CDATA[Images & Science]]></category>
		<category><![CDATA[Interesting images]]></category>
		<category><![CDATA[1500]]></category>
		<category><![CDATA[CCD]]></category>
		<category><![CDATA[dune field]]></category>
		<category><![CDATA[dune fields]]></category>
		<category><![CDATA[geometry]]></category>
		<category><![CDATA[Glow]]></category>
		<category><![CDATA[off-nadir]]></category>
		<category><![CDATA[polygons]]></category>
		<category><![CDATA[projection]]></category>
		<category><![CDATA[PSP]]></category>
		<category><![CDATA[roll angle]]></category>
		<category><![CDATA[TDI]]></category>
		<category><![CDATA[Viking]]></category>
		<category><![CDATA[Viking Lander]]></category>
		<category><![CDATA[Viking Lander 1]]></category>
		<category><![CDATA[Viking Lander 2]]></category>
		<category><![CDATA[VL1]]></category>
		<category><![CDATA[VL2]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=162</guid>
		<description><![CDATA[Here are 40 RGB color images from the 1500 &#8211; 1600 orbit range of MRO.
View Images
There are, as always, many magnificent images here. Some of the noteworthy observations are:
PSP_001521_2025 and PSP_001501_2280: On the HiRISE web site you can see diagrams made by Tim Parker show the locations of various parts (lander, backshell, heatshield or parachute) [...]]]></description>
			<content:encoded><![CDATA[<p>Here are 40 RGB color images from the 1500 &#8211; 1600 orbit range of MRO.</p>
<p><a href="/HiBlog/wp-content/uploads/psp_0015.html">View Images</a></p>
<p>There are, as always, many magnificent images here. Some of the noteworthy observations are:</p>
<p><a href="/HiBlog/wp-content/uploads/psp_0015.html#PSP_001521_2025">PSP_001521_2025</a> and <a href="/HiBlog/wp-content/uploads/psp_0015.html#PSP_001501_2280">PSP_001501_2280</a>: On the HiRISE web site you can see diagrams made by Tim Parker show the locations of various parts (lander, backshell, heatshield or parachute) for <a href="/PSP_001521_2025">Viking Lander 1</a> and <a href="/PSP_001501_2280">Viking Lander 2</a>. It&#8217;s possible they aren&#8217;t in the color strip (I haven&#8217;t found them)!</p>
<p><a href="/HiBlog/wp-content/uploads/psp_0015.html#PSP_001508_1245">PSP_001508_1245</a> and <a href="/HiBlog/wp-content/uploads/psp_0015.html#PSP_001510_2195">PSP_001510_2195</a>: These two exhibit a &#8220;glow&#8221; pattern of saturated pixels due to high TDI (Time Delay Integration) settings on the blue-green CCDs. (All of the exposure settings are chosen for each observation based on a photometric model of the scene).</p>
<p><a href="/HiBlog/wp-content/uploads/psp_0015.html#PSP_001538_2035">PSP_001538_2035</a>: This is a rim-to-rim section across a crater called Tooting that is about 30 kilometers in diameter. It&#8217;s also interesting to note how the altitude of the rims, when combined with the large off-nadir roll angle (23 degrees), leads to an <a href="http://hirise-pds.lpl.arizona.edu/PDS/EXTRAS/RDR/PSP/ORB_001500_001599/PSP_001538_2035/PSP_001538_2035_COLOR.abrowse.jpg">oddly bowed geometric projection</a>. But it is correct; as the terrain rose, fell, and rose again from HiRISE&#8217;s angled point of view, the center of the ground track deviated slightly east or west from a true great-circle line.</p>
<p><a href="/HiBlog/wp-content/uploads/psp_0015.html#PSP_001558_1325">PSP_001558_1325</a> and <a href="/HiBlog/wp-content/uploads/psp_0015.html#PSP_001593_2635">PSP_001593_2635</a>: These dune fields are striking, forming incredible patterns.</p>
<p><a href="/HiBlog/wp-content/uploads/psp_0015.html#PSP_001582_2245">PSP_001582_2245</a>: Looking like a super-sized area of dried mud, the polygonal cracks in this image are amazing.</p>
<p><strong>Updated (2008-Apr-10)</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2008/03/18/image-fest-3/feed/</wfw:commentRss>
		<slash:comments>2</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>

