Copyright © 2001 by LMT/GTM
Nov 17, 2001
Revision History | ||
---|---|---|
Revision 1.0 | Nov 30,2001 | MH |
Added kernel figure | ||
Revision | ||
This document describes On the Fly (OTF) mapping at the FCRAO telescope with the SEQUOIA focal plane array receiver. It is designed to guide the user through the OTF data collection program (OTF) and the steps to construct convolved, regridded spectra. For developers of additional tools, a brief description of the otf dat file data structure is provided.
Table of Contents
On the Fly Mapping is a general observing technique to efficiently generate images over large fields with respect to the resolution of the detector. For single dish radio astronomy, the efficiency is gained by the reduced overhead as the telescope is no longer required to start and stop at discrete points to accumulate integration time and a single reference measurement is shared with many on-source observations. There are many excellent reviews and studies of the OTF mapping technique (see Mangum, Emerson, and Greison, in Imaging at Radio through Submillimeter Wavelengths , ASP Conference Series, Vol 217, p. 179, 2000) and documentation at several observatories FCRAO, NRAO, IRAM 30m.
On the Fly Mapping at FCRAO has been developed with the SEQUOIA focal plane array to further augment its imaging capability at mm wavelengths. While FCRAO has long had the capability to share references (MAP program with RAST=1), it still observed in discrete steps with the attendant overhead. The development of OTF mapping was accelerated in the Spring of 2001 in response to the planned removal of the dewar rotation system for the expanded two-dewar SEQUOIA array. Without tracking the astronomical coordinate system (equatorial, galactic, or cometary axes), rapid readouts of the backends would be required to avoid positional inaccuracies as the orientation changes with time. In addition to increased efficiency of the data collection, OTF mapping has the benefit of reducing or eliminating the noise and gain inhomogeneities between pixels of the focal plane array and to provide redundancy in the case of a malfunctioning element. One can expect images with higher fidelity. In this development, we have applied many concepts and results from the implementation of OTF mapping at other single dish telescopes (see above references).
It is assumed that the user has configured the frontend (frequency, LO) and backend spectrometers (bandwidth) and defined the MAIN and REF positions and VLSR for the source.
The OTF program initiates an on the fly mapping sequence given the configuration set up by the OTF keywords (see below). The program is activated from the observing console with the command
START OTF
Like any observing program, to view the OTF keywords and their current values, one simply types the name of the program -- ex.
OTF
While there are many keywords associated with the OTF program, these offer convenient flexibility and ease to construct rather complicated maps including the mosaicing of many small maps to generate a large image. In the FCRAO implementation of OTF mapping, the "scanning direction" is defined as the axis upon which the antenna is moved repeatedly across to construct an image. A "scan" is defined as the set of data taken between two reference measurements for one IF or LO configuration. These data, including the bookend reference observations, are written into a single otf file on the server computer named swift.astro.umass.edu. An OTF map may be comprised of many such scans.
The OTF map is regulated by keywords set by the user. The sensitivity of an OTF map is dependent upon the dump time (TSAM), convolving kernel, antenna speed, and oversampling rate. At FCRAO, we fix the oversampling rate, NOS, to be 4 dumps/FWHM beam size to minimize smearing of the beam along the scanning direction and aliasing in the convolved image. The speed of the antenna, R, with respect to the sidereal rate is
R = BX/(NOS*TSAM) arcminutes/sec
where BX is the OTF keyword which sets the FWHM of the beam in arcminutes, NOS is the oversampling rate set to 4, and TSAM is the integration time per dump of the backends in seconds. As with any mm wave observation, it is imperative that a reference measurement be taken frequently to account for drifts in the receiver and atmosphere. For SEQUOIA, the reference observations should be taken every 1-2 minutes to ensure the highest quality data. The time between references, TBREF is estimated
TBREF = NBREF*(LX+2*XRAMP*BX)/R + 2*T_2REF + (NBREF-1)*T_turn seconds
where T_2REF is the time to slew to the reference position, T_turn is the time to turn the antenna around on each row, LX is the length of a scanned row in arcminutes, XRAMP is the number of beams to extend beyond the map edges to ensure an accurate convolution of points within the mapped area. T_TURN is an increasing function of R as it takes longer to turn the antenna the faster it is moving. If TBREF is too long, the user must either reduce NBREF, LX, or TSAM or some combination of these three parameters with the constraint that NBREF must be an integer value of unity or greater.
The OTF program shares several keywords with the Observatory MAP program but have modified definitions.
KMAP selects map coordinate system and scanning axis for zero degree scanning angle.
ROTANG sets the angle between OTF X,Y axes and the coordinate system that is defined by KMAP parameter. ROTANG is given in units of degrees and it is defined to be the angle, measured counterclockwise, between the Y axis of the map and the Y axis of the coordinate system defined by KMAP. For example, there are three equivalent setups to make the scanning direction along the DEC axis (KMAP 2 ROTANG 0 or KAMP 4 ROTANG 90 or KMAP 4 ROTANG -90). The differences between +90 and -90 is the sign of the Y axis with respect to RA.
BX FWHM of the telescope beam at the observing frequency in arcminutes.
BY FWHM of the telescope beam at the observing frequency in arcminutes.
LX angular extent of the OTF map in the scanning direction in units of arcminutes.
LY angular extent of the OTF map in the perpendicular to the scanning direction in units of arcminutes.
XOFF X Offset of the center of the OTF map from the 0,0 position. The unit of XOFF is LX. Fractional values are legal to overlap contiguous maps.
YOFF Y Offset of the OTF map from the 0,0 position. The unit of YOFF is LY. Fractional values are legal to overlap contiguous maps.
DY the number of BY units to offset before scanning the next row. DY can be postive or negative. If positive, then the rastering starts at the lower left corner and move upward through the map. If negative, the rastering begins at the upper left corner and moves downward.
RAMPX additional angular extent of the OTF map in the scanning direction in units of BX. The optional ramp provides data off the map edges to convolve into the output grid.
RAMPY additional angular extent of the OTF map in the scanning direction in units of BY. The optional ramp provides data off the map edges to convolve into the output grid.
NBREF Number of rows to observe between reference measurements.
With the START OTF command, the antenna moves to the REF position and makes a calibration measurement (unless NCAL=0) which is immediately followed by a reference measurement. The antenna then begins to raster across the source starting at the upper (lower) left corner of the desired map depending if the sign of DY is negative (postive). At each TSAM interval, the MODCOMP sends an interrupt to the spectrometers to dump the accumulated data. It also sends a packet of positional information which gets tagged along with the data. Data are also accumulated as the antenna is turning around to scan across the next row. Once the antenna has traversed NBREF rows, a second reference measurement is taken for this set of data and one otf data file is written for each IF or LO configuration. If the antenna has traversed NCAL rows since the last CAL measurement, a CAL observation is activated followed by another reference observation. If a CAL is not necessary, then the ending reference observation of the previous set is used as the first reference of the subsequent set. The map is completed when the reference pixel in the array has offset LY+2*BY*RAMPY arcminutes from the starting position.
To configure an OTF equatorial map which is 10 x 10 arcminutes on a side with a 3 beam ramp in both the X and Y directions, centered on the (0,0) position of the map, with 4 rows per reference measurement and 8 rows per CAL measurement, offset between rows of 0.5 beams with integration time per dump equal to 0.25 seconds and a reference integration time of 5 seconds:
KMAP 4 ROTANG 0 BX 0.75 BY 0.75 LX 10 LY 10 XOFF 0 YOFF 0 DY .5 RAMPX 3 RAMPY 3 NBREF 4 NCAL 8 TSAM 0.25 TREF 5
To configure a similar map but centered 10 arcminutes to the east,
XOFF 1
To construct an 8'x5' image of a galaxy with a major axis orientation of 25 degrees, 2 beam ramps, 2 rows/off, 4 rows/CAL, 1sec/dump, 0.5 beam steps/row
KMAP 4 ROTANG -65 BX .75 BY .75 LX 8 LY 5 XOFF 0 YOFF 0 RAMPX 2 DX .5 RAMPY 2 NBREF 2 NCAL 4 TSAM 1
Note that there must be sufficient bandwidth in the spectrometer to scan along the major axis of a rotating galaxy.
To make an image of a section of the galactic plane with the Galactic Center as the (0,0) position but the map centered at l=45 degrees, b=-0.25 degrees, scanning along galactic latitude with an angular extent of 10 arcminutes in longitude and 30 arcminutes in latitude and zero ramps
KMAP 6 LX 30 LY 10 XOFF 0.5 YOFF 90
Since KMAP 6 is equivalent to KMAP 5 ROTANG 90, the positive X axis corresponds to negative galactic latitude and the positive Y axis corresponds to positive galactic longitude. Since the offsets are in units of LX and LY, then XOFF=0.5 offsets in galactic latitude by -30*0.5=-15 arcminutes=0.25 degrees and YOFF=90 offsets in galactic latitude by 90*30=2700 arcminutes=45 degrees. This is the center of the 10'x30' longitude x latitude otf map.
The sampling of positions within the mapped region will vary as a function of hour angle. To gauge the spatial coverage of an OTF map which starts at a given hour angle and the resultant sensitivity after the convolution and regridding steps, the user can run the otfsim program on the fcrao or swift workstations. The command line arguments of the otfsim program include many of the OTF keywords, the starting hour angle, and optional arguments to generate a fits file of the convolved rms. To view the set of commands, simply type otfsim. With the basic set of commands, otfsim launches a pgplot window and plots the observed points within the requested coordinate system. If the optional arguments are provided (CELL_SIZE, TSYS, Spatial Filtering function), a real-time convolution of the sensitivity is calculated and a fits file (named "rms.fits") of the convolved rms is generated. This image allows the user to gauge the the degree to which the convolved noise is uniform and to check on the angular extent of the map.
otfsim can be used to prepare for an observing run prior to arriving at the telescope. A statically linked executable of the otfsim program can be downloaded from the fcrao web page (http://www.astro.umass.edu/~fcrao/otfinfo.html). This will run under linux systems only!
The raw otf data files are written by the backend computer to a RAID 0 disk array mounted onto the /RAW directory on the server swift. For the user, this directory and the files have readonly permissions. The capacity of the disk array is 560 Gbytes which should hold approximately 1 month of data depending on the scheduled programs. Each file is archived onto a tape library the day it is taken and deleted from the hard disk array once the capacity of the disk has been observed since the generation of that file (approximately 1 month). Transferring the raw data files back to one's home institution by ftp or scp is strongly discouraged as this will severely limit the network path to the Observatory. If one wishes to bring the raw data back home, they should write a CD (capacity 650 MBytes) or DAT (capacity 4 GBytes) on fcrao or a DDS-4 DAT (capacity 20 Gbytes) on swift. The observer should bring their own archive media. Otherwise, FCRAO supports remote data reduction and access to the raw data.
The Observatory has set up the necessary software on swift to visualize and regrid the raw otf data files into a CLASS file and/or a fits cube. CLASS is the widely used single dish data reduction program developed at the University of Grenoble and IRAM ( CLASS download) which operates upon an ensemble of discrete spectra with a pathway to the construction of data cubes. In the fits output option, a fits cube is generated (velocity,x,y) which can be ported into a wide variety of image processing programs. IDL and IRAF are supported at the telescope. FCRAO encourages the users to perform this data reduction during their observing run! The size of these reduced files is generally small enough to ftp or scp these to their institution.
Modern astronomical instrumentation and data collection methods such as OTF, generate vast volumes of data. In the absence of efficient tools to inspect and manipulate these data, the user can be quickly overwhelmed. It is imperative that the user focuses upon the scientific interpretation of the observations and not struggle with the more pedantic but required steps to process raw data into calibrated, convolved spectra, images, or data cubes. Moreover, the observer requires near real time feedback to the quality of the data in order to make critical decisions at the telescope.
We have developed a suite of tools to inspect, edit, regrid the raw otf data and transform the result into a format and environment for which the user is more familiar (CLASS or fits). These tools can be run via a front-end graphical user interface otftool) under X or at the shell level with a simple command line interface which can readily be inserted into scripts. The advantage of the gui is that all of the procedures are self-contained. However, one is limited to running otftool within the X window environment. The command line versions (otfbase, otfmap) offer the capability of running the data assessment and regridding routines as batch jobs which require no interaction. Although launched at the shell, the program otfedit also requires an X window environment and user interaction.
The FCRAO otftool is an X window based graphical user interface to quickly assess data quality, edit or mask subsets of the otf files which contain questionable data, and convolve and resample the input data onto a regular grid and write the resulting spectra into a CLASS file or fits cube. To launch the program, one simply types otftool at the shell prompt.
Three tabs at the top of the otftool -- Data File Selection, Data Assessment and Regrid Data, set up the environment to gather, evaluate/edit, and regrid the data respectively. A log window at the bottom of the otftool window reports all changes to the environment and input values and display more verbose output during any processing of the data.
The Data File Selection environment facilitates the consolidation of raw otf files to be processed and creates the Input List file required by the Data Assessment and Regrid Data environments. The user sets some basic criteria through which the data files are sorted and filtered. These criteria are Source Name,Starting Scan Number, Ending Scan Number, IF number, and UT Date Interval. One can view the filtered list of file names by left clicking on the Filtered Raw Data List button. To view the names and parameters of the entire set of raw data available on the disk, one left clicks on the All Raw Data button.
Once the list of files are displayed, the user can select all of the files by left clicking on the All button. To select individual files, left click on the file name in the displayed list. One or more files can be selected with consecutive clicks. To enter the highlighted files into the OTF file list, left click on the right arrow button. To remove file names from the list, highlight the file name in the OTF file list window and left click in the left arrow button. To remove all files from the list, left click on the None button.
Finally, one needs to either create an Input File List file or append / overwrite an existing file. Enter the name of the Input File List and left click on the Save List file button. When you subsequently enter the Data Assessment or Regrid Data environments, the Input File List value will already be filled with this file name.
The names of the raw otf files are read into the program and displayed on the right side of the Data Assessment Window. To view the basic header of a given file, click the left mouse button on the name of the file (this highlights the name) and then double click the right mouse button. An auxiliary window pops up to display the header information. The Data Assessment tab displays the parameters which can be set by the user to inspect the quality of the data. These are the Reference Weighting Scheme, Assessment Mode, and baseline parameters.
The Reference Weighting Mode (Equal | Biased) sets how the two bookend reference observations within the file are weighted to each on source spectrum. The equal weighting mode implies that the two reference observations for a given pixel are simply averaged to form a single reference spectrum for all data obtained with that pixel. A biased weighting applies a unique weight to each reference spectrum which reflects its time proximity to the on-source measurement. For a scan with NDUMPS, the reference weighting for the ith dump of the spectrometer is,
Weight for Reference 1 = 1.0-(i-1)/ndumps
Weight for Reference 2 = (i-1)/ndumps
An optional parameter is Set Horn Mask. This allows the user to either include or exclude selected pixels in the file. The default is to include all horns in the file for processing. The sequence of numbers to the right of the Set Horn Mask button is the bit array which reflects the mask (recall that bit arrays are evaluated from right to left such that pixel 1 corresponds to the last digit on the right and pixel 32 corresponds to the first digit on the left). To set the horn mask, left click on the Set Horn Mask button. This pops up an auxiliary window with a check box for each horn. One can quickly reset the mask by clicking on either the Select All Horns or Deselect All Horns buttons. Once the horns are selected, click on the Dismiss button to remove this popup window.
Currently, there is only one mode to gauge the data quality. This is the RMS mode in which the rms of each spectrum contained in each file is calculated. The user needs to set the baseline parameters ( baseline order, number of windows, window intervals, and window units (channels | velocity)) to determine the standard deviation of antenna temperature values in backend channels which lie outside the window intervals. These baseline parameters are applied to each file in the input file list excluding those files for which the user has specfically defined the parameters in the Edit Selected function (see Section 4.1.2) or the command line otfedit program (see Section 4.2.2).
To view the mean rms for each pixel in the array for a selected file in the list, left click on Baseline Selected button. A progress bar appears in the status window to show the progression through the file. To view the statistics over all pixels in all files in the input file list, left click on Baseline All button. Two progress bars appear in the status window - one to show the progression through the file and a second to show the steps through the input file list. When the function has stepped through all dumps of all selected files, an auxiliary window pops up to print a summary of the average rms values in a matrix for each horn and each file. There is an option at the bottom of this auxiliary window to plot the average values for each pixel.
To visualize the raw data and to edit the data on a file by file basis, one can select a file in the input list (click left mouse button on the file name) and left click on the Edit Selected button. Alternatively, select a file and right click on the file name which pops up a window with the choices (HEADER | EXAMINE). Select EXAMINE. The editing/examine option launches a pgplot window which displays a greyscale image of the data from the first selected pixel of the mask with velocity on the x axis and dump index on the y axis. The program then waits for specific keystrokes with the cursor position which allow the user to inspect the data (plot raw spectra) and to define regions of data to be ignored by subsequent analyses or regridding. The keystroke/cursor options are summarized in Table 4.1.
Table 4.1. Keystroke/Cursor Commands
keystroke | Function |
b | Subtract baseline polynomial from each spectrum and redisplay image |
k | Plot rms versus dump index for displayed pixel |
l | Plot line (spectrum) of the image at the cursor position |
m | Set first row boundary at current cursor position for index mask |
n | Display data for next selected pixel of the mask |
p | Display data for previous selected pixel of the mask |
q | Quit edit utility |
r | Reset all index masks for displayed pixel |
R | Reset all index masks for all pixels |
u | Unset index mask at current cursor position for displayed pixel |
w | Set baseline windows for current file |
The user is reminded that the baseline subtraction in only within the memory of the program. The results are not written into the otf file. The baselines are dynamically removed during the regridding step described in Section 4.1.3.
For the "w" keystroke, the user sets one or more windows (Maximum of 5 windows) within which the spectrometer channels are not included in the calculation of baseline polynomials. Two consecutive "w" keystrokes define a window. The "x" keystroke escapes the window utility. Vertical green lines highlight each defined window.
The "m" keystroke enters the mask utility in which the user can set a range of rows/indices which contains suspect data to be excluded from the regridding process. Two consecutive "m" keystrokes define the rows of data between the cursor positions to ignore. The defined region is highlighted with red hashing. Consecutive "u" keystrokes reset the index mask between the two cursor positions. The "r" keystroke resets the entire mask for the displayed pixel and the "R" keystroke resets the mask for the entire file. When reset by the u,r, or R keystrokes, the red hashing disappears.
Since the raw otf data files are readonly and one is discouraged to simply copy these files from the /RAW directory to the user's current directory, the "w", "m", "u", "r", "R" keystrokes create or modify an extension header file (filename.X) in the user's current directory. This file contains the baseline parameters and indice masks defined by the user in this editing step. The baseline parameters override those set by the user within the otftool and are applied to this file only. This extension header is inspected in all subsequent calculations upon the data contained in the file.
On the Fly mapping generates large volumes of data sampled on an irregular grid. Regridding this data takes all of the redundant measurements of the otf map and constructs the end product - convolved spectra on a regular grid. Currently, otftool can write discrete, convolved spectra into a CLASS file or construct a fits data cube to be imported into IRAF, IDL, or other image processing packages. The X and Y limits of the output grid are determined from information contained in the headers of the otf files. The ramp areas are not included in the final grid. The input otf files are generated from one or more setups of the OTF data collection program for a given source. Note that the regridding program checks whether the otf files have the same source name, central position, and alignment of the spectra. If the spectra are misaligned or the files do not share the same (0,0) position, the regridding process aborts. There is a limit to the size of the output grid to be less than 536 Mbytes which is sufficient to hold a 2048 channel x 256 x 256 pixel grid. To construct a larger data cube, the user will need to first make smaller mosaics and recombine these in a later step.
The Regrid Data tab of the otftool displays the menu for both required and optional parameters which affect the construction of convolved, regridded spectra (see Fig 4.2). Several of these parameters are shared with the Data Assessment tab (Input list file, Reference Weighting Scheme, Set Horn Mask, and baseline parameters). These are redisplayed in the Regrid Data window. The user needs to select the Output File Type (FITS | CLASS) and the name of the Output File. These should contain the full name as no default extension (i.e .bur or .fits) is appended. For CLASS output file type, a CLASS file is created if it does not yet exist. If the file already exist, the new spectra are appended. Since the output spectra are a convolution of many spectra with different scan numbers and horns, the observation number is set to the sequence in which it is written into the CLASS file. For each spectrum, a weighted average system temperature and an effective integration time are stored in the header.
Two critical required parameters which need to be set by the user are the Output Cell Size in arcseconds and the Spatial Filtering Kernel. The width of the convolution function is set to be twice the cell size to generate a Nyquist sampled grid . Figure 5 shows the various spatial filter functions and Table 4.2 lists the formula for each function. The default Spatial Filtering Kernel is Jinc*gaussian*Jinc (kopt=1) function.
Table 4.2. Spatial Filter Options
kopt | Function | Comments |
1 | Jinc(2PIx/a)exp(-(2x/b)^2)Jinc(3.831706x/RMAX) | a=1.1, b=4.75, RMAX=3 |
2 | sinc(2PIx/a)exp(-(2x/b)^2) | a=1.1, b=4.75 |
3 | sinc(2PIx/a) | a=1.1 |
4 | exp(-4ln2(x^2) |
There are several optional parameters which affect either the regridding process or simply provide additional information in the output headers.
Flat Field (Yes | No) if flat fielding is selected, the relative beam efficiency for each horn is divided into the spectrum prior to being convolved into the output grid. IT DOES NOT divide by the ABSOLUTE beam efficiency. The data remain in the units of TA*. It is up to the user to convert the data into main beam brightness temperature by dividing the entire convolved set of spectra by the main beam efficiency for the reference pixel. The main beam efficiencies of SEQUOIA on the FCRAO 14m telescope for various frequencies are listed at FCRAO Main Beam Efficiences).
Remove Baseline (Yes | No) if baseline subtraction is selected, a polynomial is calculated for each spectrum based on the baseline parameters (order, number of windows, window intervals) and subtracted prior to the spectrum being convolved into the output grid. This slows the regridding process but removes any offsets, slopes, or curvature in the spectra depending on the selected order. It does NOT subtract a baseline from the final, convolved spectrum. This subtraction should be performed in CLASS or upon the final fits cube in the image processing package.
Noise Weighting (Yes | No) if noise weighting is selected, the spectrum is multiplied by a secondary weight factor in addition to the spatial filtering function. The advantage of noise weighting is that the noise of the final convolved spectrum is not dominated by the input spectra with the highest noise levels. There are two modes of noise weighting:
RMS the noise weighting for a spectrum is 1/rms^2, where rms is the standard deviation of antenna temperature values of the spectrum which lie outside the baseline windows. One needs to define the baseline windows for rms noise weighting. This does not require that a baseline be subtracted from the spectrum. The advantage of this weighting scheme is that baseline slopes or curvatures not subtracted from the spectrum would be reflected in the calcuated rms and a low weighting value would be applied to such rogue spectra.
TSYS the noise weighting for a spectrum is 1/tsys^2 where tsys is the system temperature associated with the data. The advantage of tsys weighting is that it requires no knowledge of window intervals which may contain signal to avoid in the rms calculation.
Include Ramps? (Yes | No) The user can choose to include the construction of spectra which lie in the ramp areas and write these into the output FITS cube of CLASS file. The noise of these spectra are higher since there are fewer number of observations which can be convolved into these positions. However, if coadded with contiguous maps, the noise can be reduced and lessens the requirement to overlap mosaics.
The Set Horn Mask is described in section 4.1.1. When regridding, the mask defined by the Set Horn Mask and the index masks generated from editing the data are both examined to determine if a spectrum is to be convolved into the output grid.
Linename is an optional string parameter which is inserted into the CLASS and fits headers. It is a useful keyword to efficiently sort and gather spectra with the same line name.
Once the required and optional parameters are set, the user initiates the regridding process by left clicking on the Compute OTFMAP button. Two progress bars appear in the Status Window. The first progress bar shows the fraction of the otf file processed and the second progress bar shows the steps through the input file list. When completed, a window pops up to inform the user that the regridding is finished.
The otfmap program is a command line function to regrid OTF data exactly as otftool but without the graphical user interface frontend. Therefore, it is useful to place into shell scripts to process many individual maps in batch mode or if the user does not have an X Window interface or for those who simply do not like GUIs. It operates like any UNIX utility with flags followed by arguments.
Table 4.3. Arguments for otfmap
Flag | Argument | Comment |
-f | input_list_filename | Required |
-o | output_filename | Required |
-t | fits:class | Required |
-wt | equal:biased | Required |
-cell | cell_size (arcsec) | Required |
-mask | horn_1,horn_2,...horn_n, | default=all horns |
-kopt | 1:4 | default=1 |
-base | yes:no | default=no |
-order | order | default=0 |
-windtype | channel:velocity | |
-wind | xl1:xu1,xl2:xu2, ... xl5:xu5 | |
-flatfield | yes:no | default=no |
-rmsweight | yes:no | default=no |
-tsysweight | yes:no | default=no |
-includemargin | yes:no | default=no |
-l | linename |
For example, to regrid the otf data files contained within L1551.lis while removing the first order baselines determined outside of the velocity window of 3 to 8 km/s, flatfielding, tsys noise weighting with output directed to
otfmap -f L1551.lis -t fits -o L1551.fits -cell 25 -wt equal -kopt 1 -flatfield yes -base yes -windtype velocity -wind 3:8 -order 1 tsysweight yes
To regrid only the data in pixel 5 of the array and writing the results into the fits cube L1551-HORN5.fitsotfmap -f L1551.lis -t fits -o L1551-HORN5.fits -cell 25 -wt equal -mask 5 -kopt 1 -flatfield yes -base yes -windtype velocity -wind 3:8 -order 1
One could write a script which successively executes otfmap with a different mask and writing the output to a different file to inspect the consistency of data between array elements.
otfmap -f L1551.lis -t fits -o L1551-HORN1.fits -mask 1 -cell 25 -wt equal
otfmap -f L1551.lis -t fits -o L1551-HORN2.fits -mask 2 -cell 25 -wt equal
...
otfmap -f L1551.lis -t fits -o L1551-HORN16.fits -mask 16 -cell 25 -wt equal
To write the regridded spectra to a CLASS file
otfmap -f L1551.lis -t class -o L1551.bur -cell 25 -wt equal
Table 5.1. Structure of the otf Data File
Data Type | Size (bytes) | Comment |
Header | 11264 | see union OTFHEADER in otf.h |
Reference Data | sizeof(float)*channels | Reference spectrum for pixel 1 |
Reference Data | sizeof(float)*channels | Reference spectrum for pixel 2 |
... | ... | ... |
Reference Data | sizeof(float)*channels | Reference spectrum for last pixel (16/32) |
Main Data | sizeof(float)*channels | Dump 1 spectrum for pixel 1 |
Main Data | sizeof(float)*channels | Dump 1 spectrum for pixel 2 |
... | ... | ... |
Main Data | sizeof(float)*channels | Dump 1 spectrum for last pixel (16/32) |
Main Data | sizeof(float)*channels | Dump 2 spectrum for pixel 1 |
Main Data | sizeof(float)*channels | Dump 2 spectrum for pixel 2 |
... | ... | ... |
Main Data | sizeof(float)*channels | Dump 2 spectrum for last pixel (16/32) |
... | ... | ... |
... | ... | ... |
... | ... | ... |
Main Data | sizeof(float)*channels | Dump NDUMP spectrum for last pixel (16/32) |
Reference Data | sizeof(float)*channels | Reference spectrum for pixel 1 |
... | ... | ... |
Reference Data | sizeof(float)*channels | Reference spectrum for last pixel (16/32) |
Table 5.2. Description of OTF Headers
Header Name | Type | Comment |
utd | double | Universal Date of observation (fractional year) |
f0 | double | Line Frequency (GHz) |
fsky | double | Sky Frequency (GHz) |
azs | double | Azimuth at start of scan (degrees) |
els | double | Elevation at start of scan (degrees) |
XCEN | double | X central coordinate (degrees) |
YCEN | double | Y central coordinate (degrees) |
xvel1 | double | Velocity of first spectrometer channel (km/s) |
xfr1 | double | Frequency of first spectrometer channel (GHz) |
dveldin | double | Velocity spacing between spectrometer channels(km/s) |
dfrdin | double | Frequency spacing between spectrometer channels(GHz) |
fr1 | double | Sky Frequency in center of first reference band (GHz) |
fr2 | double | Sky Frequency in center of second reference band (GHz) |
ddum[19] | double | Reserved Space for future double headers |
tsid | float | Local Sidereal Time of observation (radians) |
utc | float | Universal Time of observation (radians) |
targetrms | float | Target RMS |
tdump | float | integration time per dump (secs) |
telrate | float | Antenna Speed |
epoch | float | Epoch of coordinates |
bw | float | bandwidth of backend (MHz) |
vlsr | float | VLSR (km/s) |
vclsr | float | correction to vlsr (km/s) |
vcsun | float | correction to heliocentric velocity (km/s) |
NOS | float | oversampling rate of otf observation |
otfdatarev | float | Data version tag |
tau | float | opacity (nepers) |
h20mm | float | water vapor (mm) |
pamb | float | ambient atmosspheric pressure |
tamb | float | ambient temperature (K) |
rotang | float | angle of scan with respect to coordinate system |
XSIZE | float | Size of OTF Map in X (scan) direction (arcmin) |
YSIZE | float | Size of OTF Map in Y direction (arcmin) |
XOFFMAP | float | Offset of OTF Map in X direction (units of XSIZE) |
YOFFMAP | float | Offset of OTF Map in Y direction (units of YSIZE) |
XRAMP | float | Length of ramp in X direction (arcmin) |
YRAMP | float | Length of ramp in Y direction (arcmin) |
rdum[9] | float | Reserved Space for future float headers |
iscan | short | Scan number of the otf file |
nhorns | short | Number of pixels in the array |
nchan | short | Number of channels in the spectrometer for each pixel |
nsample | short | Number of dumps in the scan |
kx | short | nature of spectral axis (1=vlsr, 2=vsun) |
ky | short | nature of spectrum units (0=T, 1=TA*) |
klo | short | local oscillator (1=lsb, 2=usb) |
khm | short | lo above (2) or below (1) phase lock |
harm | short | number of harmonic |
krecv | short | Frontend identifier |
khorn | short | Reference Pixel in the array |
calscan | short | scan number of data when last CAL taken |
cfact | short | sky dip calibration factor (units of 0.0001) |
etab | short | Main beam efficiency (units of 0.0001) |
kmap | short | Map coordinate system (1,3=az/el; 2,4=equatorial; 5,6=galactic |
raoff | short | RA offsets to REF position (4 secs of time) |
decoff | short | DEC offsets to REF position (arcminutes) |
fsrate | short | fraction of observing time on signal freq. (unit=0.001) |
stype | short | Freq. switching mode (1=freq. switch; 2=double freq. switch) |
iconf | short | IF/LO configuration index |
tsys[32] | short | system temperature for each horn in array (K) |
gain[32] | short | Relative efficiency of each horn in array with respect to pixel 11 |
DXHORNS[32] | short | X Offset of horn in array with respect to pixel 11 (0.0001 deg) |
DYHORNS[32] | short | Offset of horn in array with respect to pixel 11 (0.0001 deg) |
idum[108] | short | Reserved Space for future short headers |
floatopt[8] | char | string identifying floating point convention of data (INTL or IEEE) |
name[16] | char | Source Name |
bunit[16] | char | Data units |
vlabel[16] | char | Velocity label |
xlabel[16] | char | X coordinate label |
ylabel[16] | char | Y coordinate label |
cdum[40] | char | Reserved Space for future char headers |
ANGLE[1024] | short | angle of the map coordinate system to AZ/EL |
XOFF[1024] | float | X offset of reference pixel from (0,0) |
YOFF[1024] | float | Y offset of reference pixel from (0,0) |
Table 5.3. Description of OTF Extension Headers
Extension Header Name | Type | Comment |
MASK[1024] | long | mask bit array for each dump of the scan |
iscan | short | Scan number of the otf file |
order | short | Baseline order of Chebychev polynomial |
w1[5] | short | lower bound of baseline windows |
w2[5] | short | upper bound of baseline windows |
nwind[5] | short | number of baseline windows defined by user |
modified | short | flag to tell program whether values have been modified |
idum[108] | short | Reserved Space for future short headers |