The NEWSTAR program NMAP makes maps (images) from the uv-data in a SCN-file, and stores them in a WMP-file. The input data may be combined in many different ways, to produce maps that range from simple to quite exotic. As a by-product, antenna patterns may be calculated (and stored in the same .WMP file), for use in NCLEAN.
The program NMAP also allows the user to manipulate maps in a .WMP file, and to convert them to other formats.
A .WMP file may contain various kinds of maps that are related in some way, i.e. different frequency channels, polarisations, pointing centres (mosaicking), antenna patterns, CLEAN residuals, and even gridded uv-data. Each image in a .WMP file consists of a 2-dimensional array of pixel values, withj a header containing descriptive information. A 'hypercube' of images in a .WMP file can have maps of different sizes. For more information about the structure of the .WMP file, see the .WMP file description.
The program NMAP offers the following main options:
An overview of the user interface for the MAKE option is shown in figure and its companion figure.
Overview of NMAP's map-making interface.
FIGURE
.]
See figure for the QMAPS and QDATS branches; by default, these branches are bypassed.
(The rightmost column in the diagram is irrelevant for map-making in NMAP.)
The program NMAP produces (multiple) images of the following types:
NB: Note that parallel dipoles (++) are assumed here. Observations with `crossed' dipoles (+x) require linear combinations of all four polarisations. This can be done in the map plane (see NMAP option FIDDLE_OPTION).
It is also possible to store uv-data in a WMP file, for display purposes. The uv-data is `gridded' (convolved onto a rectangular grid).
Overview of the optional detailed-question sequences of the map-making interface. This diagram expands the QMAPS and QDATAS stubs in FIGURE .]figure.
At this point, the data are either stored in the WMP file as gridded uv-data (usually for display purposes), or Fouries transformed into an image.
The following is an example of making a `normal' map (and its antenna pattern), using the program defaults. This is usually sufficient to get a satisfactory result. Experienced users may experiment with some of the more advanced options.
**** Put new script here ****
The more advanced map-making options are hidden behind the NMAP keyword QMAPS. If skipped, the (context-sensitive) default values will give a satisfactory result in most cases. Their values will be printed in the NMAP log-file. For more information on each of these keywords, see the on-line Help text (type `?'), which is also printed in the `Summary of NMAP keywords' in this Cookbook.
**** Put new script here ****
The more advanced data-selection options are hidden behind the NMAP keyword QDATA. If skipped, the (context-sensitive) default values will give a satisfactory result in most cases. Their values will be printed in the NMAP log-file. For more information on each of these keywords, see the on-line Help text (type `?'), which is also printed in the `Summary of NMAP keywords' in this Cookbook.
QDATAS (More data handling details?) = NO:
(To be added later).
Overview of NMAP's map-handling interface. } FIGURE .]{The NMAP keyword FIDDLE_OPTION offers the user a wide range of possibilities to perform oparations on maps in WMP files:
All relevant data are copied from the first (or only) input map. If 2 maps are required (ADD,AVER,POL,ANGLE) all pairs of SETS_1and SETS_2will produce an output map. SUM will average all SETS_1maps. MOSCOM will produce a single output map from all specified input maps. The others will produce an output for each SETS_1. BEAM, DEBEAM and FACTOR will overwrite the input maps. F is a specified multiplication factor.
There are two separate NMAP options (W16FITS and W32FITS.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.