Changeset 646

Timestamp:

06/01/05 13:02:12 (19 years ago)

Author:

phi196

Message:

support for 7 fields

File:

• trunk/admin/requirements2.tex (modified) (74 diffs)

trunk/admin/requirements2.tex

@@ -5 +5 @@
 \usepackage{smartref}
 \usepackage{longtable}
-%\usepackage{arrayjob}
-%\usepackage{multido}
-\usepackage[dvips]{graphicx}
-
-\def\complete{no}
+
+\def\complete{yes}
 
 % Adjust the page size
@@ -54 +51 @@
 % Also Deferred, Obsolete
 
-% Requirement comment
+% Requirement command
 %  Summary
 %  Status
 %  Priority
+%  Time estimate
+%  Percent complete
+%  Completion date
 %  Text
 
@@ -64 +64 @@
 %\newcounter{numreq}
 
-\newcommand{\requirement}[4]{
+\newcommand{\requirement}[7]{
   \ifthenelse{\equal{\complete}{yes}}
-             {\dorequirement{#1}{#2}{#3}{#4}}
-             {\ifthenelse{\equal{#2}{Done1} \or \equal{#2}{Deferred}
+             {\dorequirement{#1}{#2}{#3}{#4}{#5}{#6}{#7}}
+             {\ifthenelse{\equal{#2}{Done1} 
+                 \or \equal{#2}{Deferred}
+                 \or \equal{#2}{Removed}
                  \or \equal{#2}{Obsolete}}{}
-               {\dorequirement{#1}{#2}{#3}{#4}}}
+               {\dorequirement{#1}{#2}{#3}{#4}{#5}{#6}{#7}}}
 }
 
-
-\newcommand{\dorequirement}[4]{
+\newcommand{\subrequirement}[7]{
+  \ifthenelse{\equal{\complete}{yes}}
+             {\dosubrequirement{#1}{#2}{#3}{#4}{#5}{#6}{#7}}
+             {\ifthenelse{\equal{#2}{Done1} 
+                 \or \equal{#2}{Deferred}
+                 \or \equal{#2}{Obsolete} 
+                 \or \equal{#2}{Removed}}{}
+               {\dosubrequirement{#1}{#2}{#3}{#4}{#5}{#6}{#7}}}
+}
+
+
+\newcommand{\dorequirement}[7]{
 
   \setcounter{subrequirement}{0}
@@ -81 +93 @@
     \stepcounter{requirement}
     {\bf \showreqcounter\ \bf #1} \\ 
-    #4 \\
+    #7 \\
     \hspace*{1cm} \status{#2}{#3}
   \end{minipage}
 
-  \typeout{REQUIREMENT: \showreqcounter & #1 & #2 & #3 :ENDREQ}
+  \typeout{REQUIREMENT: \showreqcounter & #1 & #2 & #3 & #4 & #5 & #6 :ENDREQ}
 }
 
-\newcommand{\extendedrequirement}[4]{
+\newcommand{\extendedrequirement}[7]{
   \setcounter{subrequirement}{0}
 
@@ -95 +107 @@
     \stepcounter{requirement}
     {\bf \showreqcounter\  #1}
-    #4 
+    #7 
     \hspace*{1cm} \status{#2}{#3}
   \end{minipage}
 
-  \typeout{REQUIREMENT: \showreqcounter & #1 & #2 & #3 :ENDREQ}
+  \typeout{REQUIREMENT: \showreqcounter & #1 & #2 & #3 & #4 & #5 & #6 :ENDREQ}
 }
 
-\newcommand{\subrequirement}[4]{
+\newcommand{\dosubrequirement}[7]{
   \hspace*{2mm}\begin{minipage}{\textwidth-2mm}
     \setlength{\parindent}{-2mm}
     \stepcounter{subrequirement}
     {\bf \showsubreqcounter\ \bf #1} \\ 
-    #4 \\
+    #7 \\
     \hspace*{1cm} \status{#2}{#3}
   \end{minipage}
 
-  \typeout{REQUIREMENT: \showsubreqcounter & #1 & #2 & #3 :ENDREQ}
-}
-
-\newcommand{\oldrequirement}[2]{
-  \hspace*{2mm}\begin{minipage}{\textwidth-2mm}
-    \setlength{\parindent}{-2mm}
-    \showreqcounter\ #1 \\ 
-    \hspace*{1cm} {\em Priority #2}
-  \end{minipage}
-}
-
-\newcommand{\oldextendedrequirement}[2]{
-  \hspace*{2mm}\begin{minipage}{\textwidth-2mm}
-    \setlength{\parindent}{-2mm}
-    \showreqcounter\ #1 
-    \hspace*{1cm} {\em Priority #2}
-  \end{minipage}
+  \typeout{REQUIREMENT: \showsubreqcounter & #1 & #2 & #3  & #4 & #5 & #6 :ENDREQ}
 }
 
@@ -146 +142 @@
 ASAP has been written to replace the venerable single-dish software
 {\tt spc} for processing of single dish spectral line data from all
-ATNF observatories. Version 1.0 of ASAP was released in ****. This
-document reflects an update of the initial requirements document. Some
-new requirements have been added and the requirement priorities have
-been reassessed for the next development cycle.
+ATNF observatories. Version 1.0 of ASAP was released in March
+2005. This document reflects an update of the initial requirements
+document. Some new requirements have been added and the requirement
+priorities have been reassessed for the next development cycle.
 
 \section{Scope}
@@ -219 +215 @@
 \smallskip
 
-\requirement{Simple interface}{Deferred}{}{It should be simple,
+\requirement{Simple interface}{Deferred}{}{}{}{}{It should be simple,
 intuitive and uncluttered. Specifically, use of many windows
 simultaneously should be discouraged, as should hiding functionality
 behind layers of dialog boxes.}
 
-\requirement{Integrated plotter}{Deferred}{}{The plotting window
+\requirement{Integrated plotter}{Deferred}{}{}{}{}{The plotting window
 should be a major component of the GUI control, not a separate
 isolated window.}
 
-\requirement{Minimal controls}{Deferred}{}{The interface should use
+\requirement{Minimal controls}{Deferred}{}{}{}{}{The interface should use
   minimal ``always visible'' controls, with use of pull down menus and
   maybe a toolbar for frequency used functions. }
 
-\requirement{Keyboard shortcuts}{Deferred}{}{Keyboard shortcuts should
+\requirement{Keyboard shortcuts}{Deferred}{}{}{}{}{Keyboard shortcuts should
 be available.}
 
-\requirement{GUI user preferences}{Deferred}{}{Most user preferences
+\requirement{GUI user preferences}{Deferred}{}{}{}{}{Most user preferences
 (i.e. keywords in the CLI) should be presented in a popup, tabbed,
 dialog box.}
 
-\requirement{GUI line fitting}{Deferred}{}{When performing line
+\requirement{GUI line fitting}{Deferred}{}{}{}{}{When performing line
 profile fitting, a spreadsheet type window should be viewable which
 shows the current parameter values (amplitude, velocity etc) for each
@@ -251 +247 @@
 implemented in ipython using a objected oriented command approach.
 
-\requirement{Virtual CLI}{Obsolete}{}{While the GUI should be the main
+\requirement{Virtual CLI}{Obsolete}{}{}{}{}{While the GUI should be the main
 interface for new users and for basic manipulation, some tasks can be
 more efficiently performed using a CLI. A virtual CLI could be
 integrated as part of the GUI.}
 
-\requirement{CLI keyword/argument}{Obsolete}{}{The CLI should have a
+\requirement{CLI keyword/argument}{Obsolete}{}{}{}{}{The CLI should have a
 keyword/argument form and never prompt the user for specific values
 (the user should be able to change values which are retained until
 they wants to change them again).}
 
-\requirement{CLI case insensitive}{Obsolete}{}{The CLI should be case
+\requirement{CLI case insensitive}{Obsolete}{}{}{}{}{The CLI should be case
 insensitive and accept minimum matching and short forms of
 keywords.}
 
-\requirement{CLI available routines}{Done1}{}{The user must be able to
+\requirement{CLI available routines}{Done1}{}{}{}{}{The user must be able to
 quickly and easily see from the command line the available routines
 and keywords which affect it, so they can see which parameters may
@@ -272 +268 @@
 \subsection{Scripting}
 
-\requirement{Scripting}{Done1}{1}{It must be possible to run the
+\requirement{Scripting}{Done1}{1}{}{}{}{It must be possible to run the
 software in a scripting mode. This would be to process large amounts
 of data in a routine manner and also to automatically reproduce
@@ -279 +275 @@
 the same.}
 
-%\requirement{Scripts from History}{Duplicate}{}{It would be worthwhile
+%\requirement{Scripts from History}{Duplicate}{}{}{}{}{It would be worthwhile
 %having a method to auto-generate scripts (for reduction or plotting)
 %from current spectra history, or some similar method.}
@@ -288 +284 @@
 GUI and software interface.
 
-\requirement{High quality plots}{Done1}{}{It must be able to
+\requirement{High quality plots}{Done1}{}{}{}{}{It must be able to
 produce plots of publishable quality.}
 
-\subrequirement{Histogram plots}{Not started}{1} {As well as line
+\subrequirement{Histogram plots}{Not started}{1}{}{}{} {As well as line
 plots, there needs to be an option to plot spectra in ``Histogram''
 mode}
@@ -298 +294 @@
 The user must be able to specify:
 
-\subrequirement{Line Thickness}{Started}{1}{}
-
-\subrequirement{Character size}{Not started}{1}{}
-
-\subrequirement{Colours}{Started}{1}{}
-
-\subrequirement{Line styles}{Not started}{1}{}
-
-\subrequirement{Position of axis ticks}{Done1}{2}{}
-
-\subrequirement{Hard Copies}{Done1}{1}{Producing hard copies
+\subrequirement{Line Thickness}{Started}{1}{}{}{}{}
+
+\subrequirement{Character size}{Not started}{1}{}{}{}{}
+
+\subrequirement{Colours}{Started}{1}{}{}{}{}
+
+\subrequirement{Line styles}{Not started}{1}{}{}{}{}
+
+\subrequirement{Position of axis ticks}{Done1}{2}{}{}{}{}
+
+\subrequirement{Hard Copies}{Done1}{1}{}{}{}{Producing hard copies
 in postscript and .png format. Other formats may be added on an as
 need basic.}
 
-\subrequirement{Non-interactive hard copies}{Not started}{1} 
+\subrequirement{Non-interactive hard copies}{Not started}{1}{}{}{} 
 {It must be possible to produce hard copiers without an interactive
 (i.e X11) plotter starting}.
 
-\subrequirement{Scriptable plotting}{Done1}{1} {All aspects of
+\subrequirement{Scriptable plotting}{Done1}{1}{}{}{} {All aspects of
 the plotter (zooming etc) must be setable from the command line for
 scripting}
 
-\requirement{Arbitrary plots}{Not started}{3}
+\requirement{Arbitrary plots}{Not started}{3}{}{}{}
 {It must be possible to flexibly select the data to plot (e.g. Tsys vs
 time etc as well as plots such as amplitude vs channel number or
@@ -326 +322 @@
 scans could be plotted on a scatter plot (e.g. Tsys vs elevation)}
 
-\requirement{Overlay spectra}{Done1}{}{It must be possible to overlay
+\requirement{Overlay spectra}{Done1}{}{}{}{}{It must be possible to overlay
   multiple spectra on a single plot using different colours and/or
   different line styles. (Including multiple stokes data and multiple
   IFs).[[CHECK]]}
 
-\requirement{Plot individual spectra}{Done1}{}{It must be possible to
+\requirement{Plot individual spectra}{Done1}{}{}{}{}{It must be possible to
   plot either the individual integrations (in either a stacked
   fashion, or using a new subplot per integration)}
 
-\subrequirement{Auto-average integrations for plotting}{Not started}{2}
+\subrequirement{Auto-average integrations for plotting}{Not started}{2}{}{}{}
 {It should be possible to optionally auto-average integrations of a
 scan for plotting (for data thats has not already been scan averaged)}
 
-\requirement{Plotter multi-panelling}{Done1}{1}
+\requirement{Plotter multi-panelling}{Done1}{1}{}{}{}
 {It must be possible to multi-panel spectra in an n$\times$m size
 grid. It must be possible to easily change the number of plots per
 page, ie define the ``n'' and ``m'' values.}
 
-\subrequirement{Step between plots}{Not started}{1}
+\subrequirement{Step between plots}{Not started}{1}{}{}{}
 {If more spectra than can fit on the plot matrix are to be plotted,
 then it must be possible to step back and forth between the viewable
@@ -350 +346 @@
 single plot on the pages at a time.}
 
-\requirement{Multi-panel: change \# panels}{Not started}{2} 
+\requirement{Multi-panel: change \# panels}{Not started}{2}{}{}{} 
 {When using multi-panelling, the plotter should automatically update
 the plot when the plot matrix dimensions (``n'' and ``m'' are changed)}
 
-\requirement{Plotter interactive zooming}{Done1}{}{It must be possible
+\requirement{Plotter interactive zooming}{Done1}{}{}{}{}{It must be possible
   to interactively zoom the plot (channel range selection and
   amplitude of the spectra etc.)  This includes both GUI control of
@@ -360 +356 @@
   factor or directly specifying the zoom bounds. }
 
-\requirement{Zoomed subplot}{Not started}{2}
+\requirement{Zoomed subplot}{Not started}{2}{}{}{}
 {On a single plot, it should be possible to plot the full spectrum and
 a zoomed copy of the data (using a different lie style) to see weak
 features. The user must be able to specify the zoom factor.}
 
-\requirement{Offset plots}{Not started}{2}{Optionally when stacking
+\requirement{Offset plots}{Not started}{2}{}{}{}{Optionally when stacking
   multiple spectral plots in one subwindow, a (user definable) offset
   in the ``y'' direction should be added to each subsequent
   spectra.}
 
-\requirement{Plotter auto-update}{Not started}{3} 
+\requirement{Plotter auto-update}{Not started}{3}{}{}{} 
 {The plotter should automatically update to reflect user processing,
 either from the CLI or GUI. The user should have to option to turn
 this feature off if they so wish.}
 
-\requirement{Waterfall plot}{Not started}{3}
+\requirement{Waterfall plot}{Not started}{3}{}{}{}
 {It should be possible to plot individual integrations (possibly from
 multiple scans) in a ``waterfall'' plot. This is an image based
@@ -383 +379 @@
 this image should be supported. }
 
-\requirement{Waterfall editing}{Not started}{3} 
+\requirement{Waterfall editing}{Not started}{3}{}{}{} 
 {When plotting ``waterfall'' plots, it should be possible to
 interactively select regions or points and mark them as invalid
@@ -389 +385 @@
 time/velocity of the pixel beneath the cursor.}
 
-\requirement{Export waterfall to FITS}{Not started}{3} 
+\requirement{Export waterfall to FITS}{Not started}{3}{}{}{} 
 {It should be possible to export the ``waterfall'' plot images as a
 FITs file, for user specific analysis.}
 
-\requirement{Plot overlays}{Not started}{1} {Line markers overlays,
+\requirement{Plot overlays}{Not started}{1}{}{}{} {Line markers overlays,
 read from a catalogue should be optionally available. This would
 include the full Lovas catalogue, the JPL line catalogue and radio
@@ -400 +396 @@
 of the lines in any specific catalogue (to avoid clutter).}
 
-\subrequirement{Plot overlays}{Not started}{2}
+\subrequirement{Plot overlays}{Not started}{2}{}{}{}
 {Simple user definable catalogue should be definable for plot overlays}
 
-\requirement{Plot fitted functions}{Done1}{}
+\requirement{Plot fitted functions}{Done1}{}{}{}{}
 {Optionally plot fitted functions (e.g line profiles or baseline
 fit). If multiple components (e.g. Gaussian) have been fit, it should
@@ -409 +405 @@
 components}
 
-\requirement{Plot residual data}{Started}{1}
+\requirement{Plot residual data}{Started}{1}{}{}{}
 {It should be possible to plot the residual data with or without
 subtraction of fit functions. This includes plotting the spectra with
@@ -416 +412 @@
 subtracted but profile fits not subtracted.}
 
-\requirement{Plot header data}{Not started}{2} {Basic header data
+\requirement{Plot header data}{Not started}{2}{}{}{} {Basic header data
 (source name, molecule, observation time, Tsys, elevation, parallactic
 angle etc) should be optionally shown, either on the plot or next to
@@ -423 +419 @@
 for example).}
 
-\subrequirement{User define header plot positions}{Not started}{3}
+\subrequirement{User define header plot positions}{Not started}{3}{}{}{}
 {The user should be able to define where on the plot the header info
 would appear.}
 
-\requirement{Realtime cursor position}{Done1}{} 
+\requirement{Realtime cursor position}{Done1}{}{}{}{} 
 {Optionally, relevant data such as the current mouse position should
 be displayed (maybe with a mode to display an extended cross,
 horizontal or vertical line at the current cursor position).}
 
-\requirement{Plot annotations}{Not started}{2}{The user should be able
+\requirement{Plot annotations}{Not started}{2}{}{}{}{The user should be able
   to define simple annotations. This would include text overlay and
   probably simple graphics (lines, arrows etc).}
@@ -446 +442 @@
 The plotter should be used to set the following values:
 
-\requirement{Interactive channel selection}{Deferred}{1}{Range of
+\requirement{Interactive channel selection}{Deferred}{1}{}{}{}{Range of
  spectral channels needed for specific tasks (ie the channel mask)
  (See requirement \reqref{ref:chansel})}
 
-\requirement{Interactive line fitting}{Deferred}{1}{Initial
+\requirement{Interactive line fitting}{Deferred}{1}{}{}{}{Initial
 Gaussian parameters (velocity, width, amplitude) for profile
 fitting.}
 
-\requirement{Plotter change fit values}{Deferred}{1}
+\requirement{Plotter change fit values}{Deferred}{1}{}{}{}
 {Change the parameter values of existing line profile
 fits, or channel ranges used for baseline fits.}
@@ -477 +473 @@
 The software must be able to read (import) the following file formats.
 
-\requirement{Read rpfits}{Done1}{}{The rpfits file format produced by
+\requirement{Read rpfits}{Done1}{}{}{}{}{The rpfits file format produced by
   all current ATNF correlators.}
 
-\requirement{Read sdfits}{Done1}{}{SDFITS (currently written by {\tt SPC}).}
-
-\requirement{Read simple FITS}{Not started}{2}{Simple ``image'' FITS
+\requirement{Read sdfits}{Done1}{}{}{}{}{SDFITS (currently written by {\tt SPC}).}
+
+\requirement{Read simple FITS}{Not started}{2}{}{}{}{Simple ``image'' FITS
 (used by CLASS}
 
-\requirement{Read historic formats}{Not started}{3}
+\requirement{Read historic formats}{Not started}{3}{}{}{}
 {Historic ATNF single dish formats (Spectra, SPC, SLAP). Possibly a
 set of routines to translate these formats to SDFITs would suffice.}
 
-\requirement{Read PSRFITS}{Deferred}{}{PSRFIT for pulsar spectroscopy.}
-
-\requirement{Read online data}{Not started}{1}
+\requirement{Read PSRFITS}{Deferred}{}{}{}{}{PSRFIT for pulsar spectroscopy.}
+
+\requirement{Read online data}{Not started}{1}{}{}{}
 {For online analysis, the software should be able to read an rpfits
 file which is is still currently open for writing by the telescope
 backend processor.}
 
-\requirement{Handle Doppler data}{Done1}{1}{Data which has been
+\requirement{Handle Doppler data}{Done1}{1}{}{}{}{Data which has been
 observed in either a fixed frequency or Doppler tracked fashion needs
 to be handled.}
@@ -502 +498 @@
 The software should be able to export the data in the following formats.
 
-\requirement{Write SDFITS}{Done1}{}{Single Dish FITS.}
-
-\requirement{Write simple FITS}{Done1}{}
+\requirement{Write SDFITS}{Done1}{}{}{}{}{Single Dish FITS.}
+
+\requirement{Write simple FITS}{Done1}{}{}{}{}
 {Simple ``image'' FITS (as used by CLASS). It must be possible to to
 export multiple spectra simultaneously, using default file name and
 postfix.}
 
-\requirement{}{Removed}{}{In a format which can be imported by other popular
-    packages such as Class. }
-
-\requirement{Write ASCIIs}{Done1}{}
+\requirement{}{Removed}{}{}{}{}{}{In a format which can be imported by other popular
+    packages such as Class.
+
+\requirement{Write ASCIIs}{Done1}{}{}{}{}
 {Simple ASCIIs format, suitable for use with programs such as Perl,
 Python, SuperMongo etc.}
 
-\requirement{Header Writing}{Not started}{1}
+\requirement{Header Writing}{Not started}{1}{}{}{}
 {The exported data should retain as much header data as possible. It
 should also be possible to request specific data be written in the
 desired form (B1950 coordinates, optical velocity definition etc).}
 
-\requirement{Import corrections}{Done1}{}
+\requirement{Import corrections}{Done1}{}{}{}{}
 {The import function should apply relevant corrections (especially
 those which are time dependent) to specific telescopes. See
 $\S$\ref{sec:issues} for a list of currently known issues.}
 
-\requirement{Append output files}{Not started}{1} {It must be possible
+\requirement{Append output files}{Not started}{1}{}{}{} {It must be possible
 to append spectra to existing output files, specifically sdfits and
 asap output files.}
@@ -538 +534 @@
 techniques.
 
-\requirement{Quotient Spectra}{Done1}{}
+\requirement{Quotient Spectra}{Done1}{}{}{}{}
 {\label{ref:skysub} Position switched sky subtraction should be
 implemented using the algorithm \medskip\reqeqn{T_{ref} \times
@@ -544 +540 @@
 \times \frac{S}{R} - T_{ref}} -- preserves continuum\medskip}
 
-\requirement{Arbitrary reference}{Not started}{2}
+\requirement{Arbitrary reference}{Not started}{2}{}{}{}
 {The user should be able to specify an arbitrarily complex
 reference/source order (which repeats), which can then be used to make
 perform multiple sky subtractions in parallel.}
 
-\requirement{Frequency switching}{Not started}{2}
+\requirement{Frequency switching}{Not started}{2}{}{}{}
 {Frequency switched sky subtraction should be supported. (Ref. Liszt,
 1997, A\&AS, 124, 183) }
@@ -557 +553 @@
 %sky subtraction algorithms will need to be investigated.}{3}
 
-\requirement{Pulsar off pulse quotient}{Deferred}{3}
+\requirement{Pulsar off pulse quotient}{}{}{}{Deferred}{3}
 {For pulsar binned data, the (user specified) off pulse bins can be
 used as the reference spectra. Due to potentially rapid amplitude
@@ -568 +564 @@
 for one beam is obtained while the other is observing the target source.
 
-\requirement{Multibeam MX mode}{Not started}{2}
+\requirement{Multibeam MX mode}{Not started}{2}{}{}{}
 {For multibeam systems, it must be possible to perform sky subtraction
 with the source and reference in an alternate pair of beams}
@@ -580 +576 @@
 free channels.
 
-\requirement{Baseline removal}{Done1}{}
+\requirement{Baseline removal}{Done1}{}{}{}{}
 {The software must be able to do baseline removal by fitting a n'th
 order polynomials to the line free channels using a least squares
 method.}
 
-\requirement{Standing wave ripples}{Not started}{3}
+\requirement{Standing wave ripples}{Not started}{3}{}{}{}
 {Removal of standing wave ripples should be done by fitting a Sine
 function to the line free channels.}
 
-\requirement{Robust fitting}{Not started}{3} 
+\requirement{Robust fitting}{Not started}{3}{}{}{} 
 {``Robust'' fitting functions should be available, which are more
 tolerant to RFI.}
 
-\requirement{Auto-baseline}{Done1}{}
+\requirement{Auto-baseline}{Done1}{}{}{}{}
 {Automatic techniques for baselining should be investigated.}
 
@@ -602 +598 @@
 parameters.
 
-\requirement{Gaussian fitting}{Done1}{}
+\requirement{Gaussian fitting}{Done1}{}{}{}{}
 {The software must be able to do multi-component Gaussian fitting of
 the spectra. The initial amplitude, width and velocity of each
@@ -608 +604 @@
 be fit should be easily set.}
 
-\requirement{Chi squared}{Done1}{}
+\requirement{Chi squared}{Done1}{}{}{}{}
 {The reduce Chi squared (or similar statistic) of the fit should given
 to the user, so that they can easily see if adding extra components
@@ -618 +614 @@
 %along with the data.}{1}
 
-\requirement{Fit multipol data}{Done1}{}
+\requirement{Fit multipol data}{}{}{}{Done1}{}
 {For multiple polarisation data, the individual stokes parameters or
 polarisation products should be fit independently.}
 
-\requirement{Export fits}{Not started}{1}
+\requirement{Export fits}{Not started}{1}{}{}{}
 {There should be an easy way of exporting the fit parameter from
 multiple spectra, e.g. as an ASCII table.}
 
-\requirement{Constrained fitting}{Not started}{1}
+\requirement{Constrained fitting}{Not started}{1}{}{}{}
 {It should be also possible to do constrained fitting of multiple
 hyperfine components, e.g. the NH$_3$ hyperfine components. (The
@@ -632 +628 @@
 components or the amplitude ratio etc.)}
 
-\requirement{Edit fits parameters}{Done1}{}
+\requirement{Edit fits parameters}{Done1}{}{}{}{}
 {It must be possible to alter the line profile fit parameter values by
 hand at any stage.}
 
-\requirement{Fix fit parameters}{Done1}{}
+\requirement{Fix fit parameters}{Done1}{}{}{}{}
 {It must be possible to ``fix'' particular values of the line profile
 parameters, so that only subset of lines or (say) the width of a line
 is fit.}
 
-\requirement{Arbitrary line fitting}{Done1}{}
+\requirement{Arbitrary line fitting}{Done1}{}{}{}{}
 {The software should allow hooks for line profile shapes other than
 Gaussian to be added in the future, possible user specified.}
 
-\requirement{Save fit parameters}{Done1}{}
+\requirement{Save fit parameters}{Done1}{}{}{}{}
 {The fitting parameters for functions which have been fit to the data
 (e.g. for baseline removal or Gaussian fits) should be retained as an
 integral part of the data and stored permanently on disk.}
 
-\requirement{Undo subtracted fits}{Not started}{3}
+\requirement{Undo subtracted fits}{Not started}{3}{}{}{}
 {It should be possible to ``undo'' functions which have been
 subtracted from the data (e.g. baseline polynomials).}
 
-\requirement{Gaussian line area}{Not started}{1} 
+\requirement{Gaussian line area}{Not started}{1}{}{}{} 
 {Optionally the area under a fitted Gaussian should be calculated for
 the user.}
@@ -677 +673 @@
 if the flux units are Kelvin or Janskys. 
 
-\requirement{Gain-elevation}{Done1}{}
+\requirement{Gain-elevation}{Done1}{}{}{}{}
 {Gain elevation corrections should be implemented using a elevation
 dependent polynomial. The polynomial coefficients will be telescope
@@ -683 +679 @@
 dependence.}
 
-\requirement{User gain polynomial}{Done1}{}
+\requirement{User gain polynomial}{Done1}{}{}{}{}
 {The user may wish to supply their own gain polynomial.}
 
-\requirement{K-Jy conversion}{Done1}{}
+\requirement{K-Jy conversion}{Done1}{}{}{}{}
 {When required by the user, the spectral units must be converted from
 Kelvin to Jansky. At higher (3mm) frequencies this conversion is often
@@ -695 +691 @@
 and time dependent)}
 
-\requirement{Scale Tsys}{Done1}{}
+\requirement{Scale Tsys}{Done1}{}{}{}{}
 {In some cases the recorded Tsys values will be wrong. There needs to
 be a mechanism to scale the Tsys value and the spectrum if the Tsys
@@ -701 +697 @@
 factor).}
 
-\requirement{Opacity}{Done1}{}
+\requirement{Opacity}{Done1}{}{}{}{}
 {The data may need to be corrected for opacity effects, particularly
 at frequencies of 20~GHz and higher. The opacity factor to apply is
@@ -713 +709 @@
 with a time-stamp would be one possibility.}
 
-\requirement{Tsys variation with freq}{Not started}{3}
+\requirement{Tsys variation with freq}{Not started}{3}{}{}{}
 {For wideband, multibit observations, the software should have the
 option to handle Tsys which varies across the band. The exact
@@ -735 +731 @@
 disrupt the reference/source sequence.
 
-\requirement{Spectra flagging}{Started}{1}
+\requirement{Spectra flagging}{Started}{1}{}{}{}
 {The user must be able to set an entire spectra or part thereof
 (individual polarisation, IF etc) as being invalid.}
 
-\requirement{Channel flagging}{Started}{1}
+\requirement{Channel flagging}{Started}{1}{}{}{}
 {The user must be able to indicate an individual spectral point or
 range of spectral points are invalid. This should be applied to an
 individual spectra, or set of spectra.}
 
-\subrequirement{Flagged channel plotting}{???}{1} {When plotting data
+\subrequirement{Flagged channel plotting}{???}{1}{}{}{} {When plotting data
 with flagged spectral channels, the plotting should left a gap (blank)
 in the plotted data|}.
 
-\subrequirement{Flagged channel interpolatin}{Not started}{2} 
+\subrequirement{Flagged channel interpolatin}{Not started}{2}{}{}{} 
 {When plotting or processing data (e.g. quotient spectra), the users
 should be able to request that the values for flagged data are
@@ -754 +750 @@
 points.}
 
-\requirement{Plot average flux vs time}{Not started}{3}
+\requirement{Plot average flux vs time}{Not started}{3}{}{}{}
 {The user should be able to plot the average spectral flux across the
 band, or part of the band, as a function of time and interactively
@@ -760 +756 @@
 IBLED in classic aips).}
 
-\requirement{Robust Fitting}{Duplicate}{2}
+\requirement{Robust Fitting}{Duplicate}{2}{}{}{}
 {Where relevant, fitting routines etc should have the option of
 selecting RFI tolerant (``robust'') algorithms. This will require
@@ -766 +762 @@
 approach.}
 
-\requirement{Birdie finder}{Not started}{2}
+\requirement{Birdie finder}{Not started}{2}{}{}{}
 {A routine to automatically find birdies or RFI corrupted data and
 indicate the data as invalid would be useful.}
 
-\requirement{Handle flagged data}{Done1}{}
+\requirement{Handle flagged data}{Done1}{}{}{}{}
 {Other routines must be able to cope with portions of data which are
 marked as invalid.}
@@ -786 +782 @@
 The spectral manipulations which should be available are:
 
-\requirement{Add spectra}{Done1}{}{Add or subtract multiple spectra.}
-
-\requirement{Average spectra}{Done1}{1}
+\requirement{Add spectra}{Done1}{}{}{}{}{Add or subtract multiple spectra.}
+
+\requirement{Average spectra}{Done1}{1}{}{}{}
 {Averaging multiple spectra, with optional weighting based on Tsys,
 integration or rms.}
 
-\subrequirement{Average spectra with velocity shift}{Not started}{1}
+\subrequirement{Average spectra with velocity shift}{Not started}{1}{}{}{}
 {If the velocity of the spectra to be averaged is different, the data
 should be aligned in velocity. The user should be able to turn this
 feature on or off.}
 
-\requirement{Robust averaging}{Not started}{2}
+\requirement{Robust averaging}{Not started}{2}{}{}{}
 {Various robust averaging possibilities (e.g. median averaging,
 clipped means etc) should be possible.}
 
-\requirement{Data re-binning}{Done1}{}
+\requirement{Data re-binning}{Done1}{}{}{}{}
 {Re-sampling or re-binning of the data to a lower (or higher) spectral
 resolution (i.e. change the number of spectral points). The
 re-sampling factor may not necessarily be an integer.}
 
-\requirement{Velocity shift}{Done1}{} 
+\requirement{Velocity shift}{Done1}{}{}{}{} 
 {It must be possible to shift the data in ``frequency/velocity''. This
 should include channel, frequency and velocity shifts of an arbitrary
 amount.}
 
-\requirement{Spectra smoothing}{Done1}{}
+\requirement{Spectra smoothing}{Done1}{}{}{}{}
 {Spectral smoothing of the data. Hanning, Tukey, boxcar and Gaussian
 smoothing of variable widths should be possible.}
 
-\requirement{Spectra scaling}{Done1}{}{Scaling of the spectra.}
-
-\requirement{Spectra statistics}{Done1}{}
+\requirement{Spectra scaling}{Done1}{}{}{}{}{Scaling of the spectra.}
+
+\requirement{Spectra statistics}{Done1}{}{}{}{}
 {Calculate basic statistical values (maximum, minimum, rms, mean) on a
 range of spectral points. The range may not be contiguous. The
@@ -823 +819 @@
 optionally used for weighted averaging of spectra.}
 
-\requirement{Line flux}{Not started}{2}
+\requirement{Line flux}{Not started}{2}{}{}{}
 {It must be possible to calculate the flux integral over a range of
 channels. The units should be Jy.km/s (or Kelvin.km/s). The channel
 range for the calculation should be specific via the GUI or CLI.}
 
-\requirement{Line width}{Not started}{2}
+\requirement{Line width}{Not started}{2}{}{}{}
 {It must be possible to calculate the numerical ``width'' of a line
 (full width at half maximum type measurement). This should be
@@ -840 +836 @@
 specified ``maximum value''.}
 
-\requirement{Change rest frequency}{Done1}{}
+\requirement{Change rest frequency}{Done1}{}{}{}{}
 {The user must be able to easily change the rest-frequency to which
 the velocity is referenced.}
 
-\requirement{FFT filtering}{Not started}{3}
+\requirement{FFT filtering}{Not started}{3}{}{}{}
 {FFT filtering for high- and lowpass filtering and tapering.}
 
-\requirement{FFT to/from autocorrelation function}{Not started}{3}
+\requirement{FFT to/from autocorrelation function}{Not started}{3}{}{}{}
 {It should be possible to FFT the data to and from power spectra to
 the autocorrelation function.}
 
-\requirement{Cross correlation}{Not started}{3}
+\requirement{Cross correlation}{Not started}{3}{}{}{}
 {The user may wish to compute the cross correlation function of two
 spectra. The result should be a standard ``spectra'', which can be
 displayed and analysed using other functions (max, rms etc).}
 
-\requirement{Spectral calculator}{Started}{1}
+\requirement{Spectral calculator}{Started}{1}{}{}{}
 {Complex experiment specific processing can often be done using a
 series of the simple of basic functions. A spectral calculator options
@@ -869 +865 @@
 ``split'' into separate spectra.
 
-\requirement{Splice data}{Not started}{1}
+\requirement{Splice data}{Not started}{1}{}{}{}
 {It must be possible to take multi IF, multibeam or polarisation data
 and split out the individual spectral portions to form self contained
 spectra.}
 
-\requirement{Splice spectral channels}{Not started}{1} {It must be
+\requirement{Splice spectral channels}{Not started}{1}{}{}{} {It must be
 possible to select a range of spectral channels to form self contained
 spectra. The channel selection may be different for different IFs.}
 
-\requirement{Merge scantables}{Not started}{1}
+\requirement{Merge scantables}{Not started}{1}{}{}{}
 {It must be possible to append rows from one scantable onto another}
 
@@ -893 +889 @@
 %two dual polarisation measurements.}
 
-\requirement{Support polarimetry}{Done1}{}
+\requirement{Support polarimetry}{Done1}{}{}{}{}
 {All functions on the data (calibration, sky subtraction spectral
 mathematics) must support arbitrary, multiple, polarisation (linear,
 circular \& stokes and single, dual \& cross polarisations.}
 
-\requirement{Calculate stokes I}{Done1}{}
+\requirement{Calculate stokes I}{Done1}{}{}{}{}
 {It must be possible to calculate stokes I from single or dual
 polarisation observations.}
 
-\requirement{Average mixed pol data}{Not started}{2}
+\requirement{Average mixed pol data}{Not started}{2}{}{}{}
 {Average a mixture of dual polarisation and single polarisation data
 and form average stokes I (e.g. for a long observation of a source, in
 which one polarisation is missing for some time.}
 
-\requirement{Calculate stokes}{Done1}{}
+\requirement{Calculate stokes}{Done1}{}{}{}{}
 {Full stokes parameters should be obtained from dual pol (linear or
 circular) observations where the cross polarisation products have been
@@ -922 +918 @@
 %angle, Iu and Ip and the unpolarised and linearly polarised
 %intensity. {\em Stolen from SPC. I need to write this in more useful
-%language. Is this technique likely to be used anymore?.}}{3}
-
-\requirement{Compute stokes V without crosspol}{Not started}{2}
+%language. Is this technique likely to be used anymore?.}}{}{}{}{3}
+
+\requirement{Compute stokes V without crosspol}{Not started}{2}{}{}{}
 {If dual circular polarisation measurements are taken, without
 computing the cross products, the software should still be able to
 compute stokes I and V.}
 
-\requirement{Polarisation leakages}{Not started}{3}
+\requirement{Polarisation leakages}{Not started}{3}{}{}{}
 {The software should be able to calculate leakage terms from a
 calibrator source and correct the data either before or after
 conversion to Stokes. (ref. Johnston, 2002, PASA, 19, 277)}
 
-\requirement{Calibrate position angle}{Not started}{3}
+\requirement{Calibrate position angle}{Not started}{3}{}{}{}
 {The software should be able to determine absolute position angle from
 a calibrator source and correct the data either before or after
 conversion to Stokes.}
 
-\requirement{Zeeman splitting}{Not started}{3}
+\requirement{Zeeman splitting}{Not started}{3}{}{}{}
 {Zeeman splitting factors should be derived from (previous) profile
 fitting and the left and right circular polarisations. The velocity
@@ -961 +957 @@
 together).
 
-\requirement{Spectra selection}{Started}{1}
+\requirement{Spectra selection}{Started}{1}{}{}{}
 {The software needs an easy-to-use mechanism to select either
 individual or multiple spectra for viewing, parallel processing
 etc.}
 
-\requirement{Beam/IF selection}{Started}{1}
+\requirement{Beam/IF selection}{Started}{1}{}{}{}
 {An easy-to-use mechanism to select individual IFs, beams or
 polarisations is needed.}
 
-\requirement{Interactive channel selection}{Duplicate}{1}
+\requirement{Interactive channel selection}{Duplicate}{1}{}{}{}
 {\label{ref:chansel} The range of spectral points to use for baseline
 removal, statistical calculations, RFI editing, analysis etc must be
@@ -981 +977 @@
 available as a plot overlay.}
 
-\requirement{Auto-identify reference spectra}{Not started}{1}
+\requirement{Auto-identify reference spectra}{Not started}{1}{}{}{}
 {When performing sky subtraction on many spectra simultaneously, the
 software should have a mechanism for identifying ``on'' and ``off''
@@ -991 +987 @@
 source'' should be accommodated.}
 
-\requirement{Select source via header values}{Started}{1}
+\requirement{Select source via header values}{Started}{1}{}{}{}
 {The software should be able to select sets of sources based on simple
 regular expression type filtering (wild cards) on a range of header
 values. }
 
-\subrequirement{Select on source name}{Done1}{1}
+\subrequirement{Select on source name}{Done1}{1}{}{}{}
 {The use should be able to select dana on source name, e.g G309$*$ or
 G309$*$w}
 
-\subrequirement{Select on molecule}{Done1}{2}
+\subrequirement{Select on molecule}{Done1}{2}{}{}{}
 {The use should be able to select data on molecule name, e.g. NH3$*$.}
 
 \subsection{Plugins}
 
-\requirement{Plugins}{Started}{1}
+\requirement{Plugins}{Started}{1}{}{}{}
 {The package should support ``plugins'', user definable
 functions for specific processing. The plugin code must have full
 access (read/write) to the spectra data and headers.}
 
-\requirement{Plugins can reduce dimensions}{Not started}{2}
+\requirement{Plugins can reduce dimensions}{Not started}{2}{}{}{}
 {Plugins need to be able to create ``derived'' spectra with reduced
-  dimensions (i.e.. less beams, IFs, polarisations or spectral
+  dimensions (i.e. less beams, IFs, polarisations or spectral
   channels)}
 
-\requirement{Simulated data}{Not stated}{3} 
+\requirement{Simulated data}{Not stated}{3}{}{}{} 
 {The user should be able to create new spectra which the software
 treats the same as the original data. This includes full specification
@@ -1022 +1018 @@
 \subsection{Pipelining}
 
-\requirement{Pipelining}{Done1}{}
+\requirement{Pipelining}{Done1}{}{}{}{}
 {Some sort of pipelining mode is required. This would involve doing a
 quotient spectra, applying appropriate calibration and possibly
@@ -1035 +1031 @@
 \subsection{Miscellaneous functionality}
 
-\requirement{Position fitting}{Not started}{2}
+\requirement{Position fitting}{Not started}{2}{}{}{}
 {The software should be able to take a simple ``grid'' of observations
 (normally a set of observations in a cross pattern on the sky) and,
@@ -1042 +1038 @@
 simple ASCIIs form.}
 
-\requirement{Kinematic distance}{Not started}{3}
+\requirement{Kinematic distance}{Not started}{3}{}{}{}
 {The kinematic distance of a source should be calculated using basic
 Galactic rotation models. Multiple Galactic rotation models must be
 supported and a mechanism for easily adding more.}
 
-\requirement{Plot sigma errors on spectra}{Not started}{3}
+\requirement{Plot sigma errors on spectra}{Not started}{3}{}{}{}
 {For 1420 MHz observations of HI, the rms (Tsys) values vary
 significantly across the band. The software should be able to compute
@@ -1054 +1050 @@
 spectra.}
 
-\requirement{Simple Mapping}{Not started}{3}
+\requirement{Simple Mapping}{Not started}{3}{}{}{}
 {It should be possible to take a selection of calibrated spectra which
 are then passed to the ``Gridzilla'' program to produce an image
@@ -1062 +1058 @@
 \section{Help}
 
-\requirement{Built in help}{Done1}{} 
+\requirement{Built in help}{Done1}{}{}{}{} 
 {There should be built-in and web-based documentation, which can be
 easily kept up-to-date}
 
-\requirement{Cookbook}{Done1}{}
+\requirement{Cookbook}{Done1}{}{}{}{}
 {A short and simple end-to-end cookbook for basic data analysis should
 be available.}
 
-\requirement{Programmers Documentation}{Not started}{2}
+\requirement{Programmers Documentation}{Not started}{2}{}{}{}
 {There should be documentation aimed at astronomers wishing to write
 there own scripts, detailing the methods needed and how to get low
@@ -1077 +1073 @@
 \section{Data and meta-data}
 
-\requirement{Handle multi dimensional data}{Done1}{}
+\requirement{Handle multi dimensional data}{Done1}{}{}{}{}
 {The software must be capable of handling multi-IF (potentially dozens
 of IFs) and multi-beam data with arbitrary polarisation (e.g. single
 pol, dual pol, full stokes etc).}
 
-\requirement{Handle pulsar data}{Deferred}{}
+\requirement{Handle pulsar data}{Deferred}{}{}{}{}
 {The software should handle pulsar binned data for pulsar absorption
 experiments.}
@@ -1088 +1084 @@
 \subsection{History}
 
-\requirement{History}{Done1}{}
+\requirement{History}{Done1}{}{}{}{}
 {A user viewable history of data processing steps should be kept as
 part of the data. Where possible this should be retained when data is
 imported from other packages.}{
 
-\requirement{Convert history to script}{Not started}{2}
+\requirement{Convert history to script}{Not started}{2}{}{}{}
 {It should be possible to use the history information to create
 template pipeline scripts for batch processing.}
@@ -1099 +1095 @@
 \subsection{Multiple IFs}
 
-\requirement{Transparently handle multi-IF data}{Done1}{}
+\requirement{Transparently handle multi-IF data}{Done1}{}{}{}{}
 {If multiple IFs are present (currently Tidbinbilla can produce two
 IFs and the new wideband spectrometer for Mopra may have dozens of
@@ -1109 +1105 @@
 of separate ``container'').}
 
-\requirement{IFs with different number of spectral channels}{Not started}{2}
+\requirement{IFs with different number of spectral channels}{Not started}{2}{}{}{}
 {Separate IFs may have a different number of spectral channels.}
 
 \subsection{Multibeam}
 
-\requirement{Handle multibeam data}{Done1}{}
+\requirement{Handle multibeam data}{Done1}{}{}{}{}
 {Basic handling of multibeam data should be possible (ie in general
 each beam will be treated as a separate observation, but all within
@@ -1120 +1116 @@
 individual beams or all beams in parallel.}
 
-\requirement{Multibeam simultaneous reference/signal}{Not started}{3}
+\requirement{Multibeam simultaneous reference/signal}{Not started}{3}{}{}{}
 {The use of a single beam observing a source and the rest of the beams
 as reference beams for sky-subtraction should be investigated.}
@@ -1126 +1122 @@
 \subsection{Robust fitting}
 
-\requirement{Retain raw correlator integrations}{Done1}{}
+\requirement{Retain raw correlator integrations}{Done1}{}{}{}{}
 {If robust fitting using median filtering is used, then the individual
 integrations from the observations should {\em not} be averaged when
@@ -1135 +1131 @@
 \subsection{Coordinate frames and units}
 
-\requirement{Flexible coordinate frames}{Done1}{}
+\requirement{Flexible coordinate frames}{Done1}{}{}{}{}
 {Coordinate frames and unit selection and handling needs to be
 flexible and relatively transparent to the user (i.e. if the users
@@ -1141 +1137 @@
 reference frame in which the data was observed).}
 
-\requirement{Specific reference frames}{Done1}{}
+\requirement{Specific reference frames}{Done1}{}{}{}{}
 {At a minimum the following reference frames and conventions should be
 handled: \setlength{\parindent}{0pt}
@@ -1157 +1153 @@
 \anitem{Flux}{ Jansky, Kelvin (mJy etc).}}
 
-\requirement{Data units and frames properly labelled}{Done1}{}
+\requirement{Data units and frames properly labelled}{Done1}{}{}{}{}
 {All data should be internally labelled with the appropriate
  coordinate frame and units. If this information is ambiguous for some
@@ -1163 +1159 @@
  should not have to worry about it again.}
 
-\requirement{Current reference frames clear to user}{Done1}{}
+\requirement{Current reference frames clear to user}{Done1}{}{}{}{}
 {It should be clear to the user what coordinate frame (velocity,
 position etc) the data is being presented as.}
 
-\requirement{Positional Reference Frame}{Not started}{1} {The user
+\requirement{Positional Reference Frame}{Not started}{1}{}{}{} {The user
 should be able to specify the reference frame (Epoch,Equinox etc) for
 which is used for exporting data, simple mapping output etc. J2000,
@@ -1173 +1169 @@
 in what the data was recorded.}
 
-\requirement{Non-conformist Positional Reference Frame}{Not Started}{2} 
+\requirement{Non-conformist Positional Reference Frame}{Not started}{2}{}{}{} 
 {Non-confirmist positional frames such as Az-El should be supported.}
 
@@ -1182 +1178 @@
 retained. The user may wish to enter some specific values by hand.
 
-\requirement{View and edit header data}{Started}{1}
+\requirement{View and edit header data}{Started}{1}{}{}{}
 {All header data should be viewable and editable by the user. This
 includes changes such as scaling the given Tsys values.}
 
-\requirement{Missing header data}{Done1}{}
+\requirement{Missing header data}{Done1}{}{}{}{}
 {Missing header data should be handled gracefully, i.e. the software
 should fill the values with ``blanks'' and be able to continue to
 process the data if possible.}
 
-\requirement{User add missing header data}{Not started}{2}
+\requirement{User add missing header data}{Not started}{2}{}{}{}
 {The user must be able to add missing header data, which is not
 present in the RPFITs file. It must be possible to add the same header
 data to multiple scans simultaneously.}
 
-\extendedrequirement{Itemised header items}{Started}{1}
+\extendedrequirement{Itemised header items}{Started}{1}{}{}{}
 {The following header data would be required per scan:
 \begin{itemize}
@@ -1219 +1215 @@
 }
 
-\extendedrequirement{IF header items}{Started}{1}
+\extendedrequirement{IF header items}{Started}{1}{}{}{}
 {\label{req:if}
 The following header data is required for each IF, beam etc:
@@ -1234 +1230 @@
 }
 
-\requirement{Pretty print formula}{Not started}{3}
+\requirement{Pretty print formula}{Not started}{3}{}{}{}
 {The molecular formula could be stored with embedded superscripted and
 subscripted symbols for ``pretty'' printing on the plotted, but
@@ -1245 +1241 @@
 \vspace{\parskip}
 
-\requirement{Multiple rest frequencies per IF}{Not started}{2}
+\requirement{Multiple rest frequencies per IF}{Not started}{2}{}{}{}
 {The software should optionally support multiple lines per IF, by
 storing a set of rest frequencies per IF, rather than a single
@@ -1255 +1251 @@
 \section{Installation}
 
-\requirement{Easy installation}{Started}{1}
+\requirement{Easy installation}{Started}{1}{}{}{}
 {It must be possible for astronomers to install the software at their
 own institute with either a moderate amount of OS experience or some
@@ -1261 +1257 @@
 on a central ``NFS'' server as well as local desk-tops.}
 
-\requirement{Linux Support}{Started}{1}
+\requirement{Linux Support}{Started}{1}{}{}{}
 {The software must run on major flavours of Linux
 (Fedora/Redhat, Debian, etc).}
 
-\subrequirement{Solaris Support}{Started}{1}
+\subrequirement{Solaris Support}{Started}{1}{}{}{}
 {The software must run on Solaris}
 
-\requirement{Run on laptop}{Done1}{}
+\requirement{Run on laptop}{Done1}{}{}{}{}
 {It must be possible for users to install the software on their
 laptops and run with no network connection.}
 
-\requirement{Easy upgrade}{Done1}{}
+\requirement{Easy upgrade}{Done1}{}{}{}{}
 {It should be relatively easy to upgrade to the latest version of the
 software.}
 
-\requirement{MacOS/X support}{Not started}{1}
+\requirement{MacOS/X support}{Not started}{1}{}{}{}
 {The software should run on MacOS/X}
 
-\requirement{Windows support}{Not started}{3}
+\requirement{Windows support}{Not started}{3}{}{}{}
 {It would be desirable for the software to run on Windows.}
 
@@ -1324 +1320 @@
 \begin{itemize}
 \item All 20-GHz data is calibrated in flux units of Kelvin.
+\item Elevation is not written into the rpfits file.
 \end{itemize}