Surface Brightness Map

surface brightness map, 60 µm, 20 iterations

This map represents the actual IRAS infrared sky as processed by the MCM algorithm. Intensity is in units of mega-Janskys per steradian.

Coverage Map

coverage map, 60 µm

The coverage map give the sum of the weighted detector response at each image pixel over all detector samples. The actual number of detectors contributing to a particular pixel is roughly twice the value of that pixel in the coverage map. Examination of the coverage map can indicate non-uniformities in detector coverage.

Correction Factor Variance Map

correction factor variance map, 60 µm, 20 iterations

The correction factor variance map gives the statistical variance about the mean correction factor (computed for each detector) for that pixel.

The MCM algorithm iteratively approximates the real sky by correcting the intensity in each pixel so that the simulated scan data are maximally similar to the actual scan data. If all the detectors agreed exactly on what the flux of a given pixel should be, all the correction factors would be one and the correction factor variance at that pixel would be zero.

For a typical default-processed source with good signal to noise, the correction factor variances at iteration 20 should be between 0.001 and 0.01. Areas with relatively large correction factor variance either indicates the presence of data which do not agree with the majority of the scans (a "bad" scan, for example, or 3rd HCON calibration differences) or noisy or saturated regions. Alternatively, the source may not yet be as resolved as is possible with the MCM. A high correction factor variance may indicate the field would benefit from further iteration.

Photometric Noise Map

photometric noise map, 60 µm, 20 iterations

The photometric noise map indicates the internal photometric error of the detector samples resulting from the averaging of those that overlap, and is essentially the standard deviation of contributions to each pixel. It does not include absolute errors such as calibration errors. These maps can thus be used to show the relative noise across an image, but not the absolute level of the photometric noise.

Beam Sample Maps

beam sample map, 60 µm, 20 iterations

Spike Plus Background Model Input Maps

spike and background model for 60 µm.
This is an example of an input map using the smoothed background option.

The beam sample maps are a fairly sophisticated tool for estimating the achieved resolution in the HIRES maps. The beam sample maps make use of the simulation capability of YORIC, which allows the generation of modeled detector scans for an arbitrary input image.

For the beam sample maps, the input image is a pattern of spikes of user-specified integrated flux density planted on top of either a smoothed version of the 20-iteration HIRES image of the input field or a flat background. By default, either 25 spikes in a 5 by 5 grid (1 degree square field) or 81 spikes in a 9 by 9 grid (2 degree square field) with a height of 10 Jy are used. You may specify the positions and/or height of the spikes and doing so will provide optimal results. An option to plant spikes where a point source filter detects point-like structure is also available. One spike plus background model map is generated per band.

Once the spike plus background model input map has been generated, simulated unenhanced scan data for it are generated. These data are then passed through YORIC as if they were real IRAS scans, and the resulting maps are output, once for each surface brightness map, as the beam sample maps. A two-dimensional gaussian fit is made to each spike location and the results reported in the beam width report. The resolution of the spikes at a given iteration should be a good indication of the resolution of a real point source of that flux at that location in the HIRES map. However, there are many reasons why some variation might occur and the beam sample maps should be interpreted carefully.

Detector Track Map

detector track map, 60 µm

This is a map which indicates which detector's center hit each pixel. If the center of a detector "footprint" (two dimensional modeled response function) hit a pixel, its ID is recorded in that pixel. If more than one detector hits a given pixel, the last to cross is kept. If no detector center hit the pixel, the value zero is kept.

<-- Previous Section   Next Section -->
(HIRES Target Selection Criteria) (HIRES Processing Options)