<?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; JMARS</title>
	<atom:link href="http://hirise.lpl.arizona.edu/HiBlog/tag/jmars/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>Google context maps</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2008/10/03/google-context-maps/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2008/10/03/google-context-maps/#comments</comments>
		<pubDate>Fri, 03 Oct 2008 16:55:58 +0000</pubDate>
		<dc:creator>Ingrid Daubar</dc:creator>
				<category><![CDATA[HiRISE]]></category>
		<category><![CDATA[Images & Science]]></category>
		<category><![CDATA[Website]]></category>
		<category><![CDATA[context]]></category>
		<category><![CDATA[elevation]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Hellas]]></category>
		<category><![CDATA[infrared]]></category>
		<category><![CDATA[IR]]></category>
		<category><![CDATA[JMARS]]></category>
		<category><![CDATA[map]]></category>
		<category><![CDATA[MOC]]></category>
		<category><![CDATA[MOLA]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[THEMIS]]></category>
		<category><![CDATA[visible]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=204</guid>
		<description><![CDATA[ Our image web pages all have this great map feature (click the image to the right for an example).  (It&#8217;s been there for a while, so you may have noticed it already.) If you scroll down to the bottom, below the Observation Toolbox, you&#8217;ll see a mini context map from Google maps for [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://hirise.lpl.arizona.edu/PSP_009548_1420"><img src="http://hirise.lpl.arizona.edu/images/2008/details/PSP_009548_1420.jpg" alt="PSP_009548_1420"align=right height=180 /></a> Our image web pages all have this great map feature (click the image to the right for an example).  (It&#8217;s been there for a while, so you may have noticed it already.) If you scroll down to the bottom, below the <strong>Observation Toolbox</strong>, you&#8217;ll see a mini context map from <a href="http://maps.google.com/maps">Google maps</a> for the specific image whose page you&#8217;re viewing.  It&#8217;s so useful to be able to see the HiRISE footprints placed on a broader view of Mars, showing the surrounding geology. Plus, you can pan and zoom around in the map.  Way cool.<br />
<span id="more-204"></span><br />
There are 3 different maps available: <strong>Elevation</strong>, <strong>Visible</strong>, and <strong>Infrared</strong>.  I&#8217;m not 100% certain which maps they&#8217;re using, but these are my guesses from comparing maps in <a href="http://jmars.asu.edu/">JMARS</a>, one of the tools we use for targeting. (JMARS is publicly available, by the way, and we recommend using it! Especially since it&#8217;s got an awesome HiRISE stamp layer now&#8230; but that&#8217;s another post!) </p>
<table>
<tr>
<td>
<a href='http://hirise.lpl.arizona.edu/HiBlog/wp-content/uploads/2008/10/elevation.png' title='elevation google map example'><img src='http://hirise.lpl.arizona.edu/HiBlog/wp-content/uploads/2008/10/elevation.thumbnail.png' alt='elevation google map example' align=left /></a>
</td>
<td>
<strong>Elevation</strong> = Colorized MOLA (<a href="http://mola.gsfc.nasa.gov/">Mars Orbiter Laser Altimeter</a>) &#8211; I find this the most useful map to orient myself on the planet when I zoom pretty far out. The map isn&#8217;t very high resolution, but large global-scale features are easily identifiable.
</td>
</tr>
<tr>
<td><a href='http://hirise.lpl.arizona.edu/HiBlog/wp-content/uploads/2008/10/visible.png' title='visible google map example'><img src='http://hirise.lpl.arizona.edu/HiBlog/wp-content/uploads/2008/10/visible.thumbnail.png' alt='visible google map example' align=left /></a>
</td>
<td><strong>Visible</strong> = MOC (<a href="http://www.msss.com/mgs/moc/index.html">Mars Orbital Camera</a>) <a href="http://www.msss.com/mgcwg/mgm/">wide-angle map</a>. In this example, the visible map is clouded over by bright haze.  That&#8217;s actually typical for this region &#8211; because it has such a low elevation, clouds form there during most of the year.
</td>
</tr>
<tr>
<td> <a href='http://hirise.lpl.arizona.edu/HiBlog/wp-content/uploads/2008/10/infrared.png' title='IR google map example'><img src='http://hirise.lpl.arizona.edu/HiBlog/wp-content/uploads/2008/10/infrared.thumbnail.png' alt='IR google map example' align=left /></a>
</td>
<td> <strong>Infrared</strong> = THEMIS (<a href="http://themis.asu.edu/">THermal EMission Imaging System</a>) daytime IR &#8211; these maps are high-resolution, so they&#8217;re good for close-in context. They&#8217;re harder to interpret, though, because most people aren&#8217;t used to looking at infrared (IR) images. IR observations measure the temperature of the surface, not albedo (brightness/darkness) like a regular visible-light image. You do see shapes in daytime IR, like you would see in a visible image; shapes are detected because shadows are darker (and thus cooler) than sunlit areas. In addition, though, you can also get an idea of the type of material in an IR image.  For example, dusty areas will be brighter in daytime IR images because they heat up faster during the day. Rocky areas will be darker, because it takes them longer to warm up from the cold night. (<a href="http://www.planetary.org/blog/article/00001347/">This article</a> has a good explanation of this, using White Rock as an example.)
</td>
</tr>
</table>
<p>Using these maps, I was able to figure out that the &#8220;enigmatic terrain&#8221; in the above picture (<a href="http://hirise.lpl.arizona.edu/PSP_009548_1420">PSP_009548_1420</a>) is in the western part of Hellas Basin, which is a large, deep depression in the southern hemisphere of Mars.  I could also tell it&#8217;s part of a larger isolated patch of this type of stuff, which seems to run concentrically along the inside of the basin rim.  In this case I <em>could</em> have figured some of that out from the caption and the coordinates, but this is more fun.  <img src='http://hirise.lpl.arizona.edu/HiBlog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2008/10/03/google-context-maps/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>How Big Are Our Feet?</title>
		<link>http://hirise.lpl.arizona.edu/HiBlog/2007/02/20/how-big-are-our-feet/</link>
		<comments>http://hirise.lpl.arizona.edu/HiBlog/2007/02/20/how-big-are-our-feet/#comments</comments>
		<pubDate>Wed, 21 Feb 2007 03:24:50 +0000</pubDate>
		<dc:creator>HiCommander</dc:creator>
				<category><![CDATA[HiRISE]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Uplink]]></category>
		<category><![CDATA[CCD]]></category>
		<category><![CDATA[coordination]]></category>
		<category><![CDATA[footprint]]></category>
		<category><![CDATA[HiPlan]]></category>
		<category><![CDATA[JMARS]]></category>
		<category><![CDATA[Mars Odyssey]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[screenshot]]></category>
		<category><![CDATA[THEMIS]]></category>

		<guid isPermaLink="false">http://hirise.lpl.arizona.edu/HiBlog/?p=77</guid>
		<description><![CDATA[To give you some idea as to the size of a HiRISE image, I&#8217;ve put together a few screenshots from our planning software, HiPlan. These images compare the HiRISE footprint with that of the the THEMIS instrument aboard Mars Odyssey. These screenshots are shown below as thumbnails; click on a thumbnail to see the screenshot [...]]]></description>
			<content:encoded><![CDATA[<p>To give you some idea as to the size of a HiRISE image, I&#8217;ve put together a few screenshots from our planning software, HiPlan. These images compare the HiRISE footprint with that of the the <a href="http://themis.asu.edu">THEMIS</a> instrument aboard <a href="http://marsprogram.jpl.nasa.gov/odyssey/">Mars Odyssey</a>. These screenshots are shown below as thumbnails; click on a thumbnail to see the screenshot at its actual resolution.</p>
<p>I should note that these are not planned to be actual HiRISE images; I was using HiPlan in test mode while working on the display of the individual HiRISE CCD footprints.</p>
<p>Take a look at this screenshot. It covers a small region of Mars roughly one degree across and slightly less than a degree tall:</p>
<div style="text-align:center">
<a href="http://pirlwww.lpl.arizona.edu/~schaller/HiBlog/crater_1024.jpg"><img src="http://pirlwww.lpl.arizona.edu/~schaller/HiBlog/crater_1024_thumb.jpg" width=450 height=394/></a>
</div>
<p><span id="more-77"></span></p>
<p>The low-resolution background is THEMIS daytime infrared imagery at 256 pixels per degree; it is an amalgamation of several such infrared THEMIS images. This view was displayed in HiPlan at 1024 pixels per degree, so the background looks quite blocky.</p>
<p>The sharper region down the center of the screenshot is the upper portion of a single THEMIS visible spectrum image. It is a much higher-resolution image, so it appears quite a bit sharper than the background. The black border surrounding the visible spectrum image is an artifact of the simplified image processing used in HiPlan; in order to show quickly multiple sets of data overlain atop one another, corners almost literally have to be cut.</p>
<p>The colorful, translucent rectangle cutting across the crater is a typical HiRISE &#8220;footprint&#8221;&#8212;that is, it is the area of Mars that would be imaged by our camera were we actually to take this picture.</p>
<p>You might know that HiRISE consists of 14 individual CCDs, arranged in a row 10 CCDs across with the remaining four positioned in the middle of the array. This arrangement is illustrated in the screenshot by the reddish and greenish rectangles within the blue rectangle.</p>
<p>An additional level of zoom in the planning software shows these red and green rectangles more clearly. This second screenshot covers an area about a half-degree wide and a half-degree high; the image data are shown at 2048 pixels per degree:</p>
<div style="text-align:center">
<a href="http://pirlwww.lpl.arizona.edu/~schaller/HiBlog/crater_2048.jpg"><img src="http://pirlwww.lpl.arizona.edu/~schaller/HiBlog/crater_2048_thumb.jpg" width=450 height=394/></a>
</div>
<p>Each of the red rectangles represents one of the ten red-filter HiRISE CCDs. You probably notice that there are only eight visible. The other two are hidden by the green rectangles.</p>
<p>Each of the green rectangles represents one of the blue-green filter HiRISE CCDs. As mentioned, they&#8217;re covering up the central red-filter CCD rectangles. They&#8217;re also covering up the two near-infrared filter (NIR) CCD rectangles, which would be drawn a translucent white. If I had set these HiRISE images up without the blue-green CCDs active, you&#8217;d see the NIR CCDs clearly.</p>
<p>The next two screenshots form another pair from roughly the same region of Mars. The first is with HiPlan zoomed to 1024 pixels per degree, covering about one degree of width of the surface of Mars:</p>
<div style="text-align:center">
<a href="http://pirlwww.lpl.arizona.edu/~schaller/HiBlog/channel_1024.jpg"><img src="http://pirlwww.lpl.arizona.edu/~schaller/HiBlog/channel_1024_thumb.jpg" width=450 height=394/></a>
</div>
<p>The blue lines running through this screenshot canted slightly to the HiRISE footprint are THEMIS footprints. I&#8217;ve chosen not to have HiPlan fill them in.</p>
<p>The second is the same area zoomed to 2048 pixels per degree; it covers a region about a half-degree across:</p>
<div style="text-align:center">
<a href="http://pirlwww.lpl.arizona.edu/~schaller/HiBlog/channel_2048.jpg"><img src="http://pirlwww.lpl.arizona.edu/~schaller/HiBlog/channel_2048_thumb.jpg" width=450 height=394/></a>
</div>
<p>What about the blue regions at the ends of the HiRISE footprints? In order to coordinate HiRISE observations with those planned by other instruments aboard MRO, we always plan on slightly larger observations than we really take. In addition to making the coordination planning easier, it allows us to change the size of our observation or move it around slightly after the spacecraft-level instructions have been sent, but before our actual instrument instructions are delivered.</p>
<p>Normally, we center our actual observation within the blue planning zone. We could easily adjust it, however. In the case of the second set of screenshots, for instance, we might decide to slide our observation downward towards the couple of small craters near the bottom of the planning zone. We can do so without interfering with the operation of the spacecraft as a whole and without having to re-plan our coordination with the other instruments.</p>
<p>I started this post by claiming it might give you a feel for the size of a HiRISE image. I haven&#8217;t forgotten. If you click on one of the thumbnails above, you will get a full-size rendition of the planning screenshot. Each screenshot is 1024 pixels wide.</p>
<p>Take a look at just one of the red-filter HiRISE CCDs (or one of the blue-green filter CCDs; I&#8217;m not picky). If HiRISE were to take the picture planned here in these screenshots, you could fit two of those screenshots, side-by-side, across that red-filter CCD outline, and you could fit a few dozen down its length.</p>
<p>We&#8217;ll be able to display acquired HiRISE images in HiPlan in the near future, much like we can see acquired THEMIS images, though we&#8217;ll probably never be able to display them at full resolution. They&#8217;re too big!</p>
<p>One final note: HiPlan is built atop an application developed up at ASU called JMARS. Not coincidentally, the THEMIS team uses JMARS to plan their images.</p>
]]></content:encoded>
			<wfw:commentRss>http://hirise.lpl.arizona.edu/HiBlog/2007/02/20/how-big-are-our-feet/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

