 |
|
You are here: NRAO Public Wiki>Main Web>TWikiUsers>JeffMangum>GbtIdl (2011-05-18, JeffMangum)
Edit wiki text
Edit
Attach
Print version
Jeff Mangum's GBTIDL Page
Last Update: JeffMangum - 18 May 2011
Contents
Converting GBT Data to Class
A set of gbtidl and class routines are available which can be used to convert your calibrated GBT data to class format. Note that:- These conversion routines are only meant to be used on calibrated GBT data. In other words, you need to do the basic "ON-OFF" calibration (using, i.e., "getps" in gbtidl) of your spectra and save these calibrated scans to a gbtidl FITS file before proceeding.
- The class macro associated with this package only works with class90.
Frequency and Velocity Scaling in GBTIDL
While trying to figure out how to get a proper frequency/velocity axis in Class from my converted spectra, pestered Bob Garwood exhaustively regarding frequency/velocity scaling in GBTIDL. The following derives from these communications.How are Individual Frequencies and Velocities Assigned to a Given Channel?
Note:- The frequency type for reference_frequency, frequency_interval, reference_channel are pretty much always TOPO for GBT data but GBTIDL could read in data (or write out data) where that isn't the case.
- frequency_interval is the channel spacing (from channel i to [i+1]) in the frequency_type reference frame (TOPO in nearly all cases). abs(frequency_interval) should be equal to bandwidth/nchan. Note, though, that on 2010/05/18 Garwood found a bug in GBTIDL where if one used the /decimate option in any of the smoothing functions that the bandwidth was properly adjusted to reflect the new smoothed bandwidth.
- frequency_resolution is the channel width used when calculating the noise in a spectrum if one has hanning smoothed the input spectrometer spectrum (which is, by default, not smoothed). Should be 1.21*frequency_interval.
- write_ascii always writes spectra by getting the value of the x axis directly from the plotter via getxarray().
- Note that the velocity axis may not be linear with channel depending on the velocity definition being used. And it's the velocity spacing in the doppler tracked reference frame (unless you've chosen some other frame to display in the plotter). Furthermore, the state of the plotter determines the type of x axis used and the same coordinate conversion that the plotter uses are used.
- Frequency axes are always linear.
- Velocity axis in the OPTICAL definition is non-linear by definition. All others are linear.
Velocity Definitions and Coordinate Frames
(From Bob Garwood) The allowed velocity definitions are radio, optical and true. That covers the first 4 characters and is equivalent to RADI, OPTI, and RELA (relativistic or true). The trailing 3 characters are rest frame definitions and the supported ones there are: topocentric (OBS), LSR, LSD, GEO, HEL, BAR, and GAL. When the doppler tracked frame is one of those frames and you display the plot with that frame, the conversion from OBS to that frame is done using the frame velocity written by M&C when the data were taken. If that isn't the case then GBTIDL uses a routine that we borrowed from Arecibo and the accuracy of that calculation is less than what M&C uses so it's not reliable to better than about +- 200 m/s. -- JeffMangum - 2011-03-02IDL and GBTIDL Tips
- Macro Reloading: When you make a change to an IDL macro offline (like in emacs) you need to reload it with .com macroname.
- Error Handling: When an error is encountered in GBTIDL, you are often left at the "procedure level" in IDL. You need to issue the retall command to return to the main level of GBTIDL.
- Getting Help: Use the internal IDL help function. For example, to get a listing of the !g variables, issue the command help,!g,/str.
- Use of getscan: Instead of using the construct get,scan=#, one can use the builtin procedure getscan,#.
- Use of list and summary: Note:
- Use summary for raw data.
- Use list for reduced data. With list, one can use the columns= construct to get formatted output. For example, list,columns=["index","source","scan","longitude","latitude"]. The formatting is currently not very convenient (something that will be fixed in V1.1). Note also that one can use the sort key to sort by a particular parameter. For example, sort="longitude" to sort the list by RA.
- To convince GBTIDL to write rest frequency as the x-axis in write_ascii, do the following:
- You first have to set the plotter so that it's showing the x-axis you want (i.e. rest frequency). write_ascii gets it's values directly from the plotter.
- To display the data in a frame at rest relative to the source velocity as given in the header, use the "Options" menu in the plotter and select "Set Voffset=Vsource".
- To access an SDFITS file which is in a directory with gaps in its name, use the following syntax:
filein,"/Volumes/My Book 2/GBTData/AGBT11A_006_07.raw.acs.fits". In other words:- Enclose the name of the file, including directory, in double-quotes
- Do not include the "\ " characters that one would need to use if accessing this directory from a Unix command line
Documentation
My "User" Comments
-
I was able to do the following process: - Convert my data to FITS
- Load it into GBTIDL
- Display a spectrum ...very quickly in just a few steps. THIS IS A GOOD THING .
- The "User Reference" page uses frames. In Firefox, once a page with frames has been loaded, the frames display never leaves. This means that if one goes to any other documentation page, the frames display stays. It can be undone, but not in a really simple way.
Possible Bugs
- There seems to be some roundoff in the (RA,Dec) values shown on the header section of the plotter. For example, for two scans with (RA,Dec) = (16 02 30.0, -24 22 13) I got first (16 02 29.99, -24 22 13.0), then (16 02 30.01, -24 22 13.0). (SourceForge Request ID 1210037)
- Postscript files produce upside-down figures. (SourceForge Request ID 1209953; Fixed 2005-05-28)
- After several show operations, the Unzoom button on the plotter display stopped working. Had to issue the unzoom command to get the plotter to unzoom.
- Seems I managed to completely lose control of the plotter. Could not even exit it. Explicitly killing the plotter did not help, as a subsequent getfs did not restart it.
- The select procedure seems to have a bug in it. I tried to set the source name selection parameter to L1689N-0N2W, which is valid, but select responded that "No matching indices were found". Perhaps select is using the same character sizes that summary uses? (SourceForge Request ID 1209969; Fixed 2005-05-28)
Feature Requests
- There probably should be a "tolerance" parameter for averaging spectra. As it stands (and I believe that this is a UniPOPS holdover), one can average spectra that are taken at different positions, frequencies, etc. To keep people from making simple mistakes, like averaging spectra taken at different positions, ave should probably have some "tolerance" parameters. For example, a default position tolerance of 0.1 arcsec would prevent averaging spectra at different positions. If one wanted to make an average of map spectra taken at positions +-20 arcsec, then the position tolerance could be set to 20 arcsec. (SourceForge Request ID 1209972)
- It would be useful to be able to change default colors, printers, etc. by setting them in the .gbtidl file. I found several parameter settings in the GUIDE Structure Description, but not all. For example, how does one change the yellow color setting for the gaussian fit result printing on the plotter? By the way, I used the print command to query variables (i.e. print,!g.printer tells me what my printer variable is set to). Note too that help,!g,/str will list all !g variables. (SourceForge Request ID 1209975)
- After using keep to write a summed and calibrated scan, one usually just wants to "get" it thereafter. The get,scan= construct is a bit clumsy. How about a "get" or "getscan" procedure that does a get,scan=? (SourceForge Request ID 1209979; Fixed 2005-05-28)
- Suggested changes to summary : *(SourceForge Request ID 1210045)
- It would be nice to be able to change the information shown by summary . For example, I would like to be able to list for each scan the (RA,Dec) instead of the (Az,El). Note that list can take options, which can allow one to get close to what I am looking for (see the list documentation). (SourceForge Request ID 1209979)
- The full source name is not printed. Would it be possible to set the width of the source name column (or other columns)? Or, perhaps, to make the last character a "*" or something else distinguishable to indicate to the user that the source name is wider than the number of characters alloted for the summary listing? (Fixed 2005-05-28)
- Could procedures like getfs be defaulted to show the next scan in the file? For example, if I getfs,250, then if I could just say getfs to get the next FS scan in the index, that would be a nice shorthand feature to have. (SourceForge Request ID 1209979; Fixed 2005-05-28)
- Postage Stamp Plot: For point-and-shoot maps it is useful to be able to plot spectra on a 2-D ((RA,Dec) or (RA,Dec) offset, for example) display. Many analysis programs that I have used in the past have this function. An example is given below, which was produced using the "map" command in CLASS. (SourceForge Request ID 1209984)
- Header Information: For a spectrum which is the average of N spectra, it would be useful to know which scan numbers went into the average. For example, if scan numbers 1, 2, and 3 where averaged and written to a KEEP file as scan number 1, the header should list scans 1, 2, and 3. (SourceForge Request ID 1210033)
- Plot Annotation: If one sets a baseline region using setregion regions are shown as boxes. If one then does a show the baseline regions, or any other annotations (like a baseline shape drawn with bshape ) are lost. Toggling the annotations using the Options button does not bring back the annotations. It would be useful to be able to turn the baseline regions, or other annotations, back on after a show . (SourceForge Request ID 1209975)
First Try
Decided to make a first attempt at using GBTIDL by running my fingers through the REU 2004 observing project data (H2CO 2cm measurements of L1689N). JimBraatz was a big help in getting me started.Getting the Data
The observing run was done on July 10-11, 2004, but was not given a project number. JimBraatz pointed me to the location of the data:/home/archive/test-data/tape-0002/TCVSTUD_01 /home/archive/test-data/tape-0002/TCVSTUD_02To "fill" these data, I did the following:
- Log in to a GB computer. Use one of the following linux systems to do this:
- despina
- fourier
- thalassa
- euclid
ssh somewhere.gb.nrao.edu
- cd to a scratch directory so that you can avoid quota limitations in your home directory:
cd /home/scratch/jmangum
- Fill directly from the archive data location into this directory:
[jmangum@despina jmangum]$ sdfits -mode=raw -scans=1:500 /home/archive/test-data/tape-0002/TCVSTUD_01 Scan 309 (spectrometer) sampler A13, integration 2, state [SIG, CAL OFF] writt "/home/archive/test-data/tape-0002/TCVSTUD_01/ScanLog.fits" does not contain a valid spectral processor scan within the specified scan list. Scan 239 (DCR) sampler A4, integration 150, state [SIG, CAL ON ] written. [jmangum@despina jmangum]$ [jmangum@despina jmangum]$ sdfits -mode=raw -scans=1:500 /home/archive/test-data/tape-0002/TCVSTUD_02 Scan 189 (spectrometer) sampler A13, integration 2, state [SIG, CAL OFF] writt "/home/archive/test-data/tape-0002/TCVSTUD_02/ScanLog.fits" does not contain a valid spectral processor scan within the specified scan list. Scan 99 (DCR) sampler A4, integration 150, state [SIG, CAL ON ] written.
- Note that:
- The warning is just telling you that there are no spectral processor data in the dataset.
- If you omit the "scans" option, it'll fill everything. It's okay to do so as long as the resulting fits file doesn't exceed about 500M.
- Move the files to the machine that you are going to use GBTIDL on and rename them as desired.
Running GBTIDL
GBTIDL is distributed to all linux systems in CV. JimBraatz advised that I should probably use "gbtidl-test" rather than "gbtidl" since the former now includes many updates, and is close to what will be released as version 1.0. These are the data files:h2co-cont-1.fits h2co-cont-2.fits h2co-spec-1.fits h2co-spec-2.fitsThe "cont" files are DCR (Digital Continuum Receiver) measurements, while the "spec" files are the actual spectrometer measurements.
<manos:GBT>gbtidl-test
IDL Version 6.1 (linux x86 m32). (c) 2004, Research Systems, Inc.
Installation number: 212340.
Licensed for use by: National Radio Astronomy Obser
****************NOTE FOR RedHat Enterprise USERS********************
Some functionality in this IDL release requires the libstdc++
compatiblity libraries to be installed. To check if the libraries
are already installed, execute 'rpm -qa | grep compat', and look for
"compat-libstdc++-<version_number>". If this is not listed, install
the appropriate RPM for your distribution (from your install CD's).
**********************************************************
Starting GBTIDL
Display Device : X
Visual Class : TrueColor
Visual Depth : 24-Bit
Color Table Size: 256
Number of Colors: 16777216
Decomposed Color: 0
GBTIDL is under rapid development until Summer 2005.
Use at your own risk.
Code is changing rapidly and tomorrow's version may be
incompatible with today's. It may not work for extended periods.
Users should not expect any support from the development
personnel at this time.
GBTIDL ->
Following the GBTIDL Users Guide on the GBTIDL Documentation Wiki, I loaded one of my FITS files into GBTIDL:
GBTIDL -> filein,'h2co-spec-1.fits'Note that the first time you load a file into GBTIDL it will create an index file (called "h2co-spec-1.index" in this case), which may take a few moments. Once this index file is created, it can be reused for subsequent runs of GBTIDL with the associated data set.
GBTIDL -> summary
Scan Source Vel Proc Sub RestF nIF nInt nFd Az El
----------------------------------------------------------------------------
240 Lynds134 0.0 Track 0 14.488 1 2 1 179.6 48.8
241 Lynds134 0.0 Track 0 14.488 1 2 1 180.3 48.8
242 L1689N 0.0 Track 0 14.488 1 2 1 180.9 27.2
243 L1689N 0.0 Track 0 14.488 1 2 1 181.3 27.2
244 L1689N 0.0 Track 0 14.488 1 2 1 181.6 27.1
245 L1689N 0.0 Track 0 14.488 1 2 1 181.9 27.1
246 L1689N 0.0 Track 0 14.488 1 2 1 182.3 27.1
247 L1689N 0.0 Track 0 14.488 1 2 1 182.6 27.1
248 L1689N 0.0 Track 0 14.488 1 2 1 182.9 27.1
249 L1689N 0.0 Track 0 14.488 1 2 1 183.2 27.1
250 L1689N-0 0.0 Track 0 14.488 1 2 1 178.5 27.2
251 L1689N-0 0.0 Track 0 14.488 1 2 1 178.9 27.2
252 L1689N-0 0.0 Track 0 14.488 1 2 1 179.2 27.2
253 L1689N-0 0.0 Track 0 14.488 1 2 1 179.6 27.2
254 L1689N-0 0.0 Track 0 14.488 1 2 1 179.9 27.2
255 L1689N-0 0.0 Track 0 14.488 1 2 1 180.2 27.2
256 L1689N-0 0.0 Track 0 14.488 1 2 1 180.9 27.2
257 L1689N-0 0.0 Track 0 14.488 1 2 1 181.2 27.2
258 L1689N-0 0.0 Track 0 14.488 1 2 1 181.5 27.2
< Press Spacebar to continue, ? for help >
257 L1689N-0 0.0 Track 0 14.488 1 2 1 181.2 27.2
258 L1689N-0 0.0 Track 0 14.488 1 2 1 181.5 27.2
259 L1689N-0 0.0 Track 0 14.488 1 2 1 181.8 27.2
260 L1689N-0 0.0 Track 0 14.488 1 2 1 182.1 27.2
261 L1689N-0 0.0 Track 0 14.488 1 2 1 182.7 27.2
262 L1689N-0 0.0 Track 0 14.488 1 2 1 183.0 27.1
263 L1689N-0 0.0 Track 0 14.488 1 2 1 183.3 27.1
264 L1689N-0 0.0 Track 0 14.488 1 2 1 183.6 27.1
265 L1689N-0 0.0 Track 0 14.488 1 2 1 183.9 27.1
266 L1689N-0 0.0 Track 0 14.488 1 2 1 184.7 27.1
267 L1689N-0 0.0 Track 0 14.488 1 2 1 185.0 27.0
268 L1689N-0 0.0 Track 0 14.488 1 2 1 185.3 27.0
269 L1689N-0 0.0 Track 0 14.488 1 2 1 185.6 27.0
270 L1689N-0 0.0 Track 0 14.488 1 2 1 185.9 27.0
271 L1689N-0 0.0 Track 0 14.488 1 2 1 186.5 26.9
272 L1689N-0 0.0 Track 0 14.488 1 2 1 186.8 26.9
273 L1689N-0 0.0 Track 0 14.488 1 2 1 187.1 26.9
274 L1689N-0 0.0 Track 0 14.488 1 2 1 187.4 26.8
275 L1689N-0 0.0 Track 0 14.488 1 2 1 187.7 26.8
276 L1689N-0 0.0 Track 0 14.488 1 2 1 188.6 26.7
277 L1689N-0 0.0 Track 0 14.488 1 2 1 188.9 26.7
278 L1689N-0 0.0 Track 0 14.488 1 2 1 189.2 26.6
279 L1689N-0 0.0 Track 0 14.488 1 2 1 189.5 26.6
< Press Spacebar to continue, ? for help >
278 L1689N-0 0.0 Track 0 14.488 1 2 1 189.2 26.6
279 L1689N-0 0.0 Track 0 14.488 1 2 1 189.5 26.6
280 L1689N-0 0.0 Track 0 14.488 1 2 1 189.8 26.6
281 L1689N-0 0.0 Track 0 14.488 1 2 1 190.8 26.4
282 L1689N-0 0.0 Track 0 14.488 1 2 1 191.1 26.4
283 L1689N-0 0.0 Track 0 14.488 1 2 1 191.4 26.3
284 L1689N-0 0.0 Track 0 14.488 1 2 1 191.7 26.3
285 L1689N-0 0.0 Track 0 14.488 1 2 1 192.0 26.2
286 L1689N-2 0.0 Track 0 14.488 1 2 1 192.9 26.1
287 L1689N-2 0.0 Track 0 14.488 1 2 1 193.2 26.1
288 L1689N-2 0.0 Track 0 14.488 1 2 1 193.5 26.0
289 L1689N-2 0.0 Track 0 14.488 1 2 1 193.8 26.0
290 L1689N-2 0.0 Track 0 14.488 1 2 1 194.1 25.9
291 L1689N-2 0.0 Track 0 14.488 1 2 1 195.3 25.6
292 L1689N-2 0.0 Track 0 14.488 1 2 1 195.6 25.6
293 L1689N-2 0.0 Track 0 14.488 1 2 1 195.9 25.5
294 L1689N-2 0.0 Track 0 14.488 1 2 1 196.3 25.4
295 L1689N-2 0.0 Track 0 14.488 1 2 1 196.6 25.4
296 L1689N-2 0.0 Track 0 14.488 1 2 1 197.0 25.3
297 L1689N-2 0.0 Track 0 14.488 1 2 1 197.3 25.2
298 L1689N-2 0.0 Track 0 14.488 1 2 1 197.6 25.1
299 L1689N-2 0.0 Track 0 14.488 1 2 1 197.9 25.1
300 L1689N-2 0.0 Track 0 14.488 1 2 1 198.2 25.0
< Press Spacebar to continue, ? for help >
287 L1689N-2 0.0 Track 0 14.488 1 2 1 193.2 26.1
288 L1689N-2 0.0 Track 0 14.488 1 2 1 193.5 26.0
289 L1689N-2 0.0 Track 0 14.488 1 2 1 193.8 26.0
290 L1689N-2 0.0 Track 0 14.488 1 2 1 194.1 25.9
291 L1689N-2 0.0 Track 0 14.488 1 2 1 195.3 25.6
292 L1689N-2 0.0 Track 0 14.488 1 2 1 195.6 25.6
293 L1689N-2 0.0 Track 0 14.488 1 2 1 195.9 25.5
294 L1689N-2 0.0 Track 0 14.488 1 2 1 196.3 25.4
295 L1689N-2 0.0 Track 0 14.488 1 2 1 196.6 25.4
296 L1689N-2 0.0 Track 0 14.488 1 2 1 197.0 25.3
297 L1689N-2 0.0 Track 0 14.488 1 2 1 197.3 25.2
298 L1689N-2 0.0 Track 0 14.488 1 2 1 197.6 25.1
299 L1689N-2 0.0 Track 0 14.488 1 2 1 197.9 25.1
300 L1689N-2 0.0 Track 0 14.488 1 2 1 198.2 25.0
301 L1689N-2 0.0 Track 0 14.488 1 1 1 198.8 24.8
302 L1689N-1 0.0 Track 0 14.488 1 2 1 199.1 24.7
303 L1689N-1 0.0 Track 0 14.488 1 2 1 199.4 24.7
304 L1689N-1 0.0 Track 0 14.488 1 2 1 199.7 24.6
305 L1689N-1 0.0 Track 0 14.488 1 2 1 200.0 24.5
306 L1689N-1 0.0 Track 0 14.488 1 2 1 200.3 24.4
307 L1689N-1 0.0 Track 0 14.488 1 2 1 200.6 24.3
308 L1689N-1 0.0 Track 0 14.488 1 2 1 200.9 24.2
309 L1689N-1 0.0 Track 0 14.488 1 2 1 201.1 24.2
GBTIDL -> getfs,240
Scan: 240 units: Ta (K) Tsys: 27.21
GBTIDL ->
This is frequency switched (FS) data, so I used the getfs procedure to get and display the data. When I did this, the plotter window pops up.
If I zoom-in
using the middle-mouse button to select a region from this spectrum, one can see the usual FS measurement structure (i.e. the "emission" features are artefacts due to the FS measurements technique). In this case, the "real" signal is an absorption signal.
Next I wanted to average all FS measurements made at a particular position, each of which was apparently given a different source name.
GBTIDL -> select,source='L1689N' Indices added to stack : 128 GBTIDL -> liststack #INDEX SOURCE SCAN PROCEDURE POL IFNUM FDNUM INT SIG CAL 32 L1689N 242 Track LL 0 0 0 F T 33 L1689N 242 Track LL 0 0 0 T T 34 L1689N 242 Track LL 0 0 0 F F 35 L1689N 242 Track LL 0 0 0 T F 36 L1689N 242 Track LL 0 0 1 F T 37 L1689N 242 Track LL 0 0 1 T T 38 L1689N 242 Track LL 0 0 1 F F 39 L1689N 242 Track LL 0 0 1 T F 40 L1689N 242 Track RR 0 0 0 F T 41 L1689N 242 Track RR 0 0 0 T T 42 L1689N 242 Track RR 0 0 0 F F 43 L1689N 242 Track RR 0 0 0 T F 44 L1689N 242 Track RR 0 0 1 F T 45 L1689N 242 Track RR 0 0 1 T T 46 L1689N 242 Track RR 0 0 1 F F 47 L1689N 242 Track RR 0 0 1 T F 48 L1689N 243 Track LL 0 0 0 F T 49 L1689N 243 Track LL 0 0 0 T T 50 L1689N 243 Track LL 0 0 0 F F 51 L1689N 243 Track LL 0 0 0 T F 52 L1689N 243 Track LL 0 0 1 F T 53 L1689N 243 Track LL 0 0 1 T T 54 L1689N 243 Track LL 0 0 1 F F 55 L1689N 243 Track LL 0 0 1 T F 56 L1689N 243 Track RR 0 0 0 F T 57 L1689N 243 Track RR 0 0 0 T T 58 L1689N 243 Track RR 0 0 0 F F 59 L1689N 243 Track RR 0 0 0 T F 60 L1689N 243 Track RR 0 0 1 F T 61 L1689N 243 Track RR 0 0 1 T T 62 L1689N 243 Track RR 0 0 1 F F 63 L1689N 243 Track RR 0 0 1 T F 64 L1689N 244 Track LL 0 0 0 F T 65 L1689N 244 Track LL 0 0 0 T T 66 L1689N 244 Track LL 0 0 0 F F 67 L1689N 244 Track LL 0 0 0 T F 68 L1689N 244 Track LL 0 0 1 F T 69 L1689N 244 Track LL 0 0 1 T T 70 L1689N 244 Track LL 0 0 1 F F 71 L1689N 244 Track LL 0 0 1 T F 72 L1689N 244 Track RR 0 0 0 F T 73 L1689N 244 Track RR 0 0 0 T T 74 L1689N 244 Track RR 0 0 0 F F 75 L1689N 244 Track RR 0 0 0 T F 76 L1689N 244 Track RR 0 0 1 F T 77 L1689N 244 Track RR 0 0 1 T T 78 L1689N 244 Track RR 0 0 1 F F 79 L1689N 244 Track RR 0 0 1 T F 80 L1689N 245 Track LL 0 0 0 F T 81 L1689N 245 Track LL 0 0 0 T T 82 L1689N 245 Track LL 0 0 0 F F 83 L1689N 245 Track LL 0 0 0 T F 84 L1689N 245 Track LL 0 0 1 F T 85 L1689N 245 Track LL 0 0 1 T T 86 L1689N 245 Track LL 0 0 1 F F 87 L1689N 245 Track LL 0 0 1 T F 88 L1689N 245 Track RR 0 0 0 F T 89 L1689N 245 Track RR 0 0 0 T T 90 L1689N 245 Track RR 0 0 0 F F 91 L1689N 245 Track RR 0 0 0 T F 92 L1689N 245 Track RR 0 0 1 F T 93 L1689N 245 Track RR 0 0 1 T T 94 L1689N 245 Track RR 0 0 1 F F 95 L1689N 245 Track RR 0 0 1 T F 96 L1689N 246 Track LL 0 0 0 F T 97 L1689N 246 Track LL 0 0 0 T T 98 L1689N 246 Track LL 0 0 0 F F 99 L1689N 246 Track LL 0 0 0 T F 100 L1689N 246 Track LL 0 0 1 F T 101 L1689N 246 Track LL 0 0 1 T T 102 L1689N 246 Track LL 0 0 1 F F 103 L1689N 246 Track LL 0 0 1 T F 104 L1689N 246 Track RR 0 0 0 F T 105 L1689N 246 Track RR 0 0 0 T T 106 L1689N 246 Track RR 0 0 0 F F 107 L1689N 246 Track RR 0 0 0 T F 108 L1689N 246 Track RR 0 0 1 F T 109 L1689N 246 Track RR 0 0 1 T T 110 L1689N 246 Track RR 0 0 1 F F 111 L1689N 246 Track RR 0 0 1 T F 112 L1689N 247 Track LL 0 0 0 F T 113 L1689N 247 Track LL 0 0 0 T T 114 L1689N 247 Track LL 0 0 0 F F 115 L1689N 247 Track LL 0 0 0 T F 116 L1689N 247 Track LL 0 0 1 F T 117 L1689N 247 Track LL 0 0 1 T T 118 L1689N 247 Track LL 0 0 1 F F 119 L1689N 247 Track LL 0 0 1 T F 120 L1689N 247 Track RR 0 0 0 F T 121 L1689N 247 Track RR 0 0 0 T T 122 L1689N 247 Track RR 0 0 0 F F 123 L1689N 247 Track RR 0 0 0 T F 124 L1689N 247 Track RR 0 0 1 F T 125 L1689N 247 Track RR 0 0 1 T T 126 L1689N 247 Track RR 0 0 1 F F 127 L1689N 247 Track RR 0 0 1 T F 128 L1689N 248 Track LL 0 0 0 F T 129 L1689N 248 Track LL 0 0 0 T T 130 L1689N 248 Track LL 0 0 0 F F 131 L1689N 248 Track LL 0 0 0 T F 132 L1689N 248 Track LL 0 0 1 F T 133 L1689N 248 Track LL 0 0 1 T T 134 L1689N 248 Track LL 0 0 1 F F 135 L1689N 248 Track LL 0 0 1 T F 136 L1689N 248 Track RR 0 0 0 F T 137 L1689N 248 Track RR 0 0 0 T T 138 L1689N 248 Track RR 0 0 0 F F 139 L1689N 248 Track RR 0 0 0 T F 140 L1689N 248 Track RR 0 0 1 F T 141 L1689N 248 Track RR 0 0 1 T T 142 L1689N 248 Track RR 0 0 1 F F 143 L1689N 248 Track RR 0 0 1 T F 144 L1689N 249 Track LL 0 0 0 F T 145 L1689N 249 Track LL 0 0 0 T T 146 L1689N 249 Track LL 0 0 0 F F 147 L1689N 249 Track LL 0 0 0 T F 148 L1689N 249 Track LL 0 0 1 F T 149 L1689N 249 Track LL 0 0 1 T T 150 L1689N 249 Track LL 0 0 1 F F 151 L1689N 249 Track LL 0 0 1 T F 152 L1689N 249 Track RR 0 0 0 F T 153 L1689N 249 Track RR 0 0 0 T T 154 L1689N 249 Track RR 0 0 0 F F 155 L1689N 249 Track RR 0 0 0 T F 156 L1689N 249 Track RR 0 0 1 F T 157 L1689N 249 Track RR 0 0 1 T T 158 L1689N 249 Track RR 0 0 1 F F 159 L1689N 249 Track RR 0 0 1 T F GBTIDL -> for i=242,249 do begin getfs,i & accum & end Scan: 242 units: Ta (K) Tsys: 32.00 Scan: 243 units: Ta (K) Tsys: 32.16 Scan: 244 units: Ta (K) Tsys: 32.31 Scan: 245 units: Ta (K) Tsys: 32.22 Scan: 246 units: Ta (K) Tsys: 32.02 Scan: 247 units: Ta (K) Tsys: 31.89 Scan: 248 units: Ta (K) Tsys: 31.89 Scan: 249 units: Ta (K) Tsys: 31.86 GBTIDL -> ave % ACCUMAVE: Average of : 8 spectra-- JeffMangum - 25 May 2005
Edit | Attach | Print version | History: r15 < r14 < r13 < r12 | Backlinks | View wiki text | Edit wiki text | More topic actions
Topic revision: r15 - 2011-05-18, JeffMangum
- NRAO Public Wiki
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding NRAO Public Wiki? Send feedback