What data do I have?

Journal software is available to aid with book-keeping of observation files.¹ If you are reducing your data at the Joint Astronomy Centre you may need to read Appendix to find where the data are stored.

sculog will give a summary of all NDF files in a directory (the directory is the current working directory and, if set, the directory specified by the DATADIR environment variable (§)).

% sculog
 
 Enter starting observation number [0] 94
 Enter final observation number [last] 95
-Log for directory: /jcmt_sw/scuba/sun216
                    /scuba/observe/apr25/dem
94      JUPITER             PHOTOM        1997:4:25     17:43:39.99893
   RA: 21 26  1.54 Dec: -15 42 52.0 (J2000) Observed centre: PLANET
   Mean airmass: 1.2310825  Bolometers:   H7                Filter: 450N:850
   Throw:    60 arcsec  AZ  Integrations: 4      Measurements: 1
   Accept: not used         DATA_KPT: DEMOD              Gain: 1
   Observation file: jupiter_h7.obs             Data file: apr25_dem_0094
 
---------
 
95                 SKYDIP        1997:4:25     17:46:26.99799
   Bolometers:   SHORT_DC,LONG_DC                Filter: 450N:850
   Max EL: 80   Min EL: 15  Integrations: 20     Measurements: 10
   Accept: NO               DATA_KPT: DEMOD              Gain: 1
   Observation file: scuba_skydip.obs           Data file: apr25_dem_0095
---------

In most cases sculog provides far too much information and a one line summary is more desirable. obssum² is provided for this purpose:

% obssum -demod
 
 Enter starting observation number [0] 92
 Enter final observation number [last] 98
-Log for directory: /jcmt_sw/scuba/sun216
                    /scuba/observe/apr25/dem
 
 #    HST    Obsmode   Source   Meas/Int Airmass  Filter  Bolometers
---- -----   --------- -------  -------- ------- -------- ----------
92   07:33   PHOTOM    JUPITER     1/4   1.229 450N:850N G4
93   07:36   PHOTOM    JUPITER     1/4   1.229 450N:850N G3
94   07:43   PHOTOM    JUPITER     1/4   1.231 450N:850N H7
95   07:46   SKYDIP    SKY        10/20        450N:850N SHORT_DC,LONG_DC
96   07:54   POINTING  uranus      1/2   1.337 450N:850N LONG
97   07:57   MAP       uranus      1/1   1.407 450N:850N SHORT,LONG
98   08:45   POINTING  uranus      1/2   1.488 450N:850N LONG

In this example a summary listing has been requested for observations 92 through 98 from the $DATADIR directory (there were no demodulated data files in my current directory). The `-demod' flag indicated that I am only interested in raw demodulated data (i.e. files containing `_dem_' in their names). sculog (and obssum) supports many more options and these are detailed in §.

Alternatively, listings of certain observations can be obtained by using the more specialized listing programs photsum, mapsum, pointsum and skysum. pointsum lists pointing observations, photsum lists photometry observations (and, in fact, skydip observations), mapsum lists map observations and skysum lists skydip observations. Using photsum instead of sculog on the data used above gives:

% photsum --begin=92 --end=98
 #    HST    Source   Meas/Int  Am   Filter  SubInst Signal   S/N   Tau  Seeing
---  -----   -------  -------- ---- -------- ------- ------  -----  ---  ------
92   07:33   JUPITER     1/4   1.23 450N:850 LONG   7.85e+00 2841.  0.074 0.161
93   07:36   JUPITER     1/4   1.23 450N:850 LONG   6.34e+00 1257.  0.074 0.161
94   07:43   JUPITER     1/4   1.23 450N:850 LONG   5.97e+00 936.4  0.074 0.423
                                             SHORT  9.26e-01 164.
**************
95   07:46   SKYDIP     10/20       450N:850 SHORT:  1.756          0.074 0.423
                                             LONG    0.310

In this case I specify the range of observations on the command line and the format of the listing has changed from that returned by sculog. Note that the signal and signal-to-noise are now provided³ - this is only the case if RO files are catalogued since the demodulated data files do not contain results (the column is left blank if no reduced data is found).

On the other hand, mapsum gives this output:

% mapsum --begin=92 --end=100
 #    HST    Source   Meas/Int  Am   Filter    Mode   Thr Crd  PA   Tau  Seeing
---  -----   -------  -------- ---- -------- -------- --- --- ----  ---  ------
**************
95   07:46   SKYDIP     10/20       450N:850 SHORT:  1.756          0.074 0.423
                                             LONG    0.310
--------------
97   07:57   uranus      1/1   1.41 450N:850 RASTER   40  SC     0  0.074 0.423

pointsum can be used to list pointing data:

% pointsum --begin=50 --end=98
 #    LST    Source  Meas/Int Az  El  Filter  Inst   Uaz  Uel   Tau  Seeing Hum
---  -----   ------- -------- --- -- -------  ----   ---  ---   ---  ------ ---
51   19:32   jupiter    1/1   140 45 450N:850 LONG  -1.6 -9.5  0.074 0.344  14%
62   20:06   jupiter    1/1   150 49 450N:850 LONG  -2.1 -10.  0.074 0.351  14%
83   20:56   jupiter    1/1   168 53 450N:850 LONG  -1.8 -11.  0.074 0.242  15%
96   21:47   uranus     1/2   203 48 450N:850 LONG  -2.7 -11.  0.074 0.423  14%
98   22:38   uranus     1/2   218 42 450N:850 LONG  -3.0 -9.6  0.074 0.984  20%

Note that UAZ and UEL indicate the offsets before the pointing observation and that the time is now quoted as LST instead of HST since this is the format expected by change_pointing.

In all cases the output can be stored in a file using standard unix redirection so long as the search path is fully specified (either with the `-all' flag or with `-begin=' and `-end=') so that the programs are not waiting for input. e.g.:

% obssum -all > summary.txt