C-WAYS Resolution Worksheet

Introduction

The spatial resolution of various instruments and missions is and will be a very important thing for us to consider in the course of assessing the literature studies of our regions, as well as doing our project with WISE and Spitzer data.

For a general introduction, please start with the main text already on the wiki for Resolution. Please also look at the examples lower on that page, but you don't need to actually do the one that suggests that you go download data, etc. The skills you might have gained from that specific example will be stuff that we will either do as part of this worksheet, or as part of our Summer visit.

We will be primarily using Goddard's Skyview to retrieve FITS images for this worksheet. You need a FITS viewer too, I suggest you use DS9 which you can download hereDS9. (see FITS explanation below).

Each of you should be assigned as a primary person for a BRC target - there are two per BRC so we have at least one check on each person's numbers. (Since there are 5 core educators, and 3 BRCs, we have room for one more 'primary' -- Mark Legassie??). If you finish doing this for 'your' target, or want to continue exploration of one of the others, or another target entirely (e.g. your favorite Messier object), please go ahead and do so!

The formal center positions we have been using are:

• BRC 27: 07:03:59 -11:23:09
• BRC 34: 21:33:32 +58:04:33
• BRC 38: 21:40:42 +58:16:13

Skyview basics and other things to note

We will be using Goddard's Skyview. There is documentation linked from that front page. We will use the full Query form, not Quick View and not Non-Astronomer's page.

If, in the future, you need to find this, you will probably need to google "Goddard Skyview" as there is at least one other software package called Skyview (including one at IPAC that is mentioned more than once here in this wiki) that does something else entirely.

DO I NEED TO MAKE A YOUTUBE SCREENCAPTURE MOVIE TO GO HERE??

Skyview pulls together some huge number of surveys in one place and makes them accessible to you in an easy, fast interface. It will resample and regrid and remosaic all sorts of surveys for you, from gamma rays to the radio. I don't know exactly if it conserves flux (e.g., if one can still do photometry off of the mosaics it provides); I would err on the side of caution and NOT use this for anything other than morphology, e.g., do science by eye with the mosaics, and you can use them for distance measurements, but don't do photometry on these mosaics.

Skyview will always spawn the same second window for the results. The first time you call it, it will spawn a second browser tab or window (depending on your local configuration), and then, if you don't close that second tab or window explicitly, the next search results will go into that same window, even if it's hidden below where you are currently working. It will make it seem as if nothing has happened when you submit your search request.

Skyview will give you a JPG right away, and allow you to download both the JPG and the FITS file (click on "FITS" to download it). Slightly more information on FITS format is elsewhere on the wiki. The most important thing is that JPGs (and for that matter GIFs or PNGs) are "lossy compressed" files, which means that images in those formats actually LOSE INFORMATION, particularly in comparison to the FITS file. JPGs are just fine for images you take of your kids with digital cameras - you rarely ever see evidence of the loss of information. (As an aside - you might see evidence of it if you take a picture of something with high contrast, or a sharp edge somewhere in the image. If you look at the jpeg up close, you will see 'ringing' of the sharp edge, which looks kind of like blurring. The wiki page on lossy compression above has an example of loss of information with pngs.)

So, what this means is: any time you are doing science, whether that is using your eye to see small details in the image, or measuring distances, or doing photometry, you always want to be using the FITS file, never a JPG, PNG, or GIF.

Therefore, you need software capable of reading FITS files. There is some information on using a variety of packages here, but you might as well start to get comfortable with using ds9, since that's what we will be using later on in the project. It's free, and available for just about any platform. There are at least 2 tutorials on using ds9 developed by NITARP students on the wiki for doing some specific things - search in the wiki on ds9 - and more from the rest of the web, including some listed at the bottom of this page.

You can ask for more than one survey at the same time, but it uses the same 'common options' you specify on the query page.

One last word of advice. When you go to download the FITS file, the default filename is related to the process id on the server, e.g., it won't mean anything to you 10 minutes after you download it. In the process of doing these exercises, you should rename the images straightaway to be something that you can understand later on.

Exploring POSS images

Go get a big mosaic, 5 deg, of your chosen region in DSS. DSS, which stands for "Digital Sky Survey", was an all-sky survey conducted using photographic plates at the Palomar Observatory. POSS is another abbreviation for this, e.g., Palomar Observatory Sky Survey. The images you are using, though, are electronic scans of those POSS plates, knitted together afterwards (hence, technically DSS rather than just plain POSS). There are two generations of these scans (DSS1 and DSS2), and two (often 3) colors -- red, blue, and IR. These are the original photographic bandpasses, not Johnson bands. Let Skyview use the default number of pixels (300).

Q1.1 : Can you find tile boundaries in your large image? Find and note the ra/dec of a corner. (note that ds9 updates the coordinates at the top of the window as you move your mouse around in the image.) (I confess I did not try this for each of our BRCs; if you can't find one, or are not sure, try another one of the BRCs, or try a larger size image.)

Q1.2 : How many arcseconds/arcminutes/degrees are there per pixel in this image? (What do I mean by that? Most pixels are square, so rather than measuring the diagonal as you would a TV screen, measure along both sides; you ought to get the same number for both sides.) Calculate what you think it should be from size and number of pixels (watch your units!), then find the corresponding value in the FITS image header. In ds9, go to 'File' (at the top of the ds9 window, or the buttons in the top middle), and pick "view fits header" or "header". Make a note of what header keyword is used, and what units it's in.

Q1.3 : Go back to Skyview and ask for a smaller image, 1 degree on a side, also with the default 300 px. How big are those pixels in arcseconds/arcminutes/degrees?

Q1.4 : Go back to Skyview and ask for a much smaller image, 0.1 degree, still with the default 300 px. How big are those pixels -- what do I mean by pixels? What size are the individual pixels in the image as returned to you, and what size are the pixels you can see in the image itself by eye? You will need to zoom in, probably a lot. You will need to find a way to measure distances on images, and unfortunately, ds9 doesn't provide an easy way to do this. As our first but certainly not last example of "astronomers using whatever software you are most familiar with to do the job", you are more than welcome to use your own favorite FITS viewer (if yours has an easy way to do this). Otherwise, you will have to do this by hand. Note that as you move your mouse around on the image in ds9, it will give you an updated readout of the ra and dec in the top. You can change this from hh:mm:ss ddd:mm:ss format to decimal degrees for both ra and dec by picking from the "wcs" menu at the top, either 'degrees' or 'sexagesimal'. Make a note of the RA/Dec of the pixel corners and calculate the distance along the sides of a pixel as you see it in the image (as opposed to that in the FITS header). Technically, to be absolutely correct, because you are calculating distances on a sphere, in order to do this, you need to do spherical trigonometry. This matters because the angle subtended by 1 hour of RA on the celestial equator is much larger than that subtended by 1 hour of RA near the celestial pole. However, over these relatively small distances, it should be mostly fine to simply subtract the ra and dec to get a reasonable estimate of the size of the pixels. It does make a difference, though. See this excerpt from someone's class notes with some really nice graphics and explanations of why you need to do this, and how to do it right. (hint: For the distances we'll consider here, you need a cosine of the declination. I won't make you do the full spherical trig for distances more than a degree.) For the ambitious, anticipating skills you'll need downstream from this worksheet, try programming a spreadsheet to do this for you, given two ra,dec position pairs. (Bonus: how much of a difference does it make if you leave out the cos(dec) term? How much does it matter for one of the other BRCs?)

OK, returning to my question above - What size are the individual pixels in the image as returned to you, and what size are the pixels you can see in the image itself by eye? Skyview did exactly what you asked it to do, and gave you an image 300 pixels across. What is the native resolution of the DSS image?

The original POSS spatial resolution was set by the seeing at Palomar that night, plus the size of the silver grains. When it got scanned, during the digitization process, the resolution becomes the size of the pixels you see there.

Q1.5 : Now, let's be careful. Normally, to 'believe' a detection of anything, astronomers require that it be seen in more than 1 pixel. If something is seen in just 1 pixel, it's hard to tell if it's a single hot pixel, or a cosmic ray, or a real detection. Thus, spatial resolution, if cited without a "per pixel", is most frequently quoted as certainly more than 1 pixel, often approaching 2 pixels. What this physically means is BOTH the following two questions: (1) "How many pixels have to be affected before I believe it is a real detection?" and (2) "How close do two sources have to be before I can no longer distinguish them as two individual sources?" (Real life numbers: the quoted resolution of IRAC is ~2 arcsec, but the native pixel size is 1.2 arcsec, and standard mosaics have the pixels resampled to be 0.6 arcsec.) The quoted resolution of the DSS is 1.7 arcsec per pixel. How does this match with what you calculated above?

Q1.6 : What happens if you ask it for a 300 px image without an image size specified (again for that same position, DSS). How big is that image you get in degrees?

Q1.7 : The four most important parameter choices Skyview gives you are:

• center position
• survey (wavelength)
• image size in pixels
• image size in degrees

Skyview will happily and without complaint or warning resample the pixels to whatever scale you want. So, now we are coming to THE MAIN POINT of doing this exercise...: what do you need to do to get 'native pixel' resolution out of Skyview for DSS images? For any other survey? There are several different possible answers to this. Can you think of more than one? You will need this for the next section!

Q1.8 : Questions to aid in pulling all of this together: You can ask Skyview to resample images to any spatial resolution, but is it adding information to the image? What are the physical limitations of any given image you select?

Moving into the IR

STILL WORKING ON THIS

Get an 'orientation' IRAS image, same size as big POSS above. look for corresponding features between POSS and IRAS. we will come back to the physics of what is bright and why, but for now, convince yourself you have, indeed, obtained the same chunk of sky, covering the same region, and make a note of the differences for later consideration.

Get a smaller IRAS image. Get same area in MSX (if available), WISE, 2MASS. Try it "all at once" to see impact of using same parameters for each pull. try it individually.

Go get a 300 px native resolution image for each; stack them up in ds9. what area is covered by IRAS? 2mass? for a laugh, try COBE too.

Go find/derive the native resolution for each of these; get corresponding full-res image of same patch of sky, size is your choice (pick smallish if you don't have much RAM). stack them up and look for correspondences. for a laugh, try COBE too.

Finder Chart IRSA tool

STILL WORKING ON THIS

go get a tiny patch of sky using finder chart at the center position of your BRC target. ask it for DSS and 2mass. (i don't think any of these have sloan coverage.) download the fits. are these native pixel scale? check to be sure. load them into ds9 with one of your other images from above. use ds9's tiles/view and snap to coordinates. what does this same patch look like in iras bands?

variations in spatial resolution, depth of observation (total integration time), and real physical differences in the objects (with time of observation as well as wavelength!) account for the differences you see in these comparisons.

YouTube video on using Finder Chart: http://www.youtube.com/watch?v=4RHS497XeHQ developed for last year's gang. we too will be using finder chart eventually for exactly this purpose, but for now, take away from this how to use finder chart, and how to get multiple fits images into your ds9 at once. this video doesn't include the "align all to wcs" trick.

these are unresampled images, so ok for photometry.

Postscript: Slight improvements are sometimes possible

STILL WORKING ON THIS

HiRes discussion. http://irsa.ipac.caltech.edu/IRASdocs/hires_over.html