Changeset 537
- Timestamp:
- 03/08/05 11:44:21 (20 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/cookbook.tex
r534 r537 42 42 \item Epping - use hosts {\tt draco} or {\tt hydra} 43 43 \item Narrabri - use host {\tt kaputar} 44 \item Parkes - use host ***44 \item Parkes - use host {\tt bourbon} 45 45 \item Mopra - use host {\tt minos} 46 46 \end{itemize} … … 204 204 \subsubsection {Contents} 205 205 206 A scantable has header information and data . Itis actually an AIPS++207 Table and it is stored in Memory when you are ma ipulating it with ASAP.206 A scantable has header information and data (a scantable is actually an AIPS++ 207 Table and it is stored in Memory when you are manipulating it with ASAP. 208 208 You can store it to disk and then browse it with the AIPS++ 209 Table browser (if you know how to do that !).209 Table browser if you know how to do that !). 210 210 211 211 The data are stored in columns (the length of a column is the number of … … 252 252 ASAP> scans.summary() # Brief listing 253 253 ASAP> scans.summary(verbose=True) # Include frequency information 254 ASAP> print scan # Equivalent to brief summary function call254 ASAP> print scan # Equivalent to brief summary function call 255 255 \end{verbatim} 256 256 … … 803 803 \begin{itemize} 804 804 \item[ASAP] This is the internal format used for ASAP. It is the only 805 format that allows the user to restore the data, fits etc without805 format that allows the user to restore the data, fits etc. without 806 806 loosing any information. As mentioned before, the ASAP scantable 807 807 is just an AIPS++ Table (a memory-based table). … … 810 810 or any other AIPS++ tool. 811 811 812 \item[SDFITS] The Single Dish FITS format. This format has been812 \item[SDFITS] The Single Dish FITS format. This format was 813 813 designed to for interchange between packages, but few packages 814 814 actually can read it.
Note:
See TracChangeset
for help on using the changeset viewer.