Changeset 650 for trunk

Timestamp:

06/02/05 09:22:29 (20 years ago)

Author:

mar637

Message:

added priority 1 estimates

File:

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

trunk/admin/requirements2.tex

@@ -300 +300 @@
 produce plots of publishable quality.}
 
-\subrequirement{Histogram plots}{Not started}{1}{}{}{} {As well as line
+\subrequirement{Histogram plots}{Not started}{1}{0.5d}{}{} {As well as line
 plots, there needs to be an option to plot spectra in ``Histogram''
 mode}
@@ -307 +307 @@
 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{Line Thickness}{Started}{1}{0.1d}{}{}{}
+
+\subrequirement{Character size}{Not started}{1}{0.1d}{}{}{}
+
+\subrequirement{Colours}{Started}{1}{0.75d}{}{}{}
+
+\subrequirement{Line styles}{Not started}{1}{0.5d}{}{}{}
 
 \subrequirement{Position of axis ticks}{Done1}{2}{}{}{}{}
@@ -321 +321 @@
 need basic.}
 
-\subrequirement{Non-interactive hard copies}{Not started}{1}{}{}{} 
+\subrequirement{Non-interactive hard copies}{Not started}{1}{2d}{}{} 
 {It must be possible to produce hard copiers without an interactive
 (i.e X11) plotter starting}.
@@ -402 +402 @@
 FITs file, for user specific analysis.}
 
-\requirement{Plot line catalog overlays}{Not started}{1}{}{}{} {Line markers overlays,
+\requirement{Plot line catalog overlays}{Not started}{1}{3d}{}{} {Line markers overlays,
 read from a catalogue should be optionally available. This would
 include the full Lovas catalogue, the JPL line catalogue and radio
@@ -418 +418 @@
 components}
 
-\requirement{Plot residual data}{Started}{1}{}{}{}
+\requirement{Plot residual data}{Started}{1}{0.5d}{}{}
 {It should be possible to plot the residual data with or without
 subtraction of fit functions. This includes plotting the spectra with
@@ -500 +500 @@
 \requirement{Read PSRFITS}{Deferred}{}{}{}{}{PSRFIT for pulsar spectroscopy.}
 
-\requirement{Read online data}{Not started}{1}{}{}{}
+\requirement{Read online data}{Not started}{1}{0.1d}{}{}
 {For online analysis, the software should be able to read an rpfits
 file which is is still currently open for writing by the telescope
@@ -525 +525 @@
 Python, SuperMongo etc.}
 
-\requirement{Header writing}{Started}{1}{}{}{}
+\requirement{Header writing}{Started}{1}{0d}{}{}
 {The exported data should retain as much header data as possible. It
 should also be possible to request specific data be written in the
@@ -535 +535 @@
 $\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}{3d}{}{} {It must be possible
 to append spectra to existing output files, specifically sdfits and
 asap output files.}
@@ -631 +631 @@
 polarisation products should be fit independently.}
 
-\requirement{Export fit parameters}{Not started}{1}{}{}{}
+\requirement{Export fit parameters}{Not started}{1}{1d}{}{}
 {There should be an easy way of exporting the fit parameter from
 multiple spectra, e.g. as an ASCII table.}
@@ -641 +641 @@
 components or the amplitude ratio etc.)}
 
-\subrequirement{Specific constrained fitting}{Not started}{1}{}{}{}
+\subrequirement{Specific constrained fitting}{Not started}{1}{4d}{}{}
 {Before arbitrary constrained fitting is available, support for
 specific cases, such as the NH$_3$ hyperfine transition, should e
@@ -668 +668 @@
 subtracted from the data (e.g. baseline polynomials).}
 
-\requirement{Gaussian line area}{Not started}{1}{}{}{} 
+\requirement{Gaussian line area}{Not started}{1}{0.2d}{}{} 
 {Optionally the area under a fitted Gaussian should be calculated for
 the user.}
@@ -749 +749 @@
 disrupt the reference/source sequence.
 
-\requirement{Spectra flagging}{Started}{1}{}{}{}
+\requirement{Spectra flagging}{Started}{1}{1d}{}{}
 {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}{0.5d}{}{}
 {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}{Done1}{1}{}{}{} {When plotting data
 with flagged spectral channels, the plotting should left a gap (blank)
 in the plotted data|}.
@@ -806 +806 @@
 integration or rms.}
 
-\subrequirement{Average spectra with velocity shift}{Not started}{1}{}{}{}
+\subrequirement{Average spectra with velocity shift}{Not started}{1}{0.2d}{}{}
 {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
@@ -870 +870 @@
 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
@@ -883 +883 @@
 ``split'' into separate spectra.
 
-\requirement{Slice data}{Not started}{1}{}{}{} {It must be possible to
+\requirement{Slice data}{Not started}{1}{10d}{}{} {It must be possible to
 take multi IF, multibeam or polarisation data and split out the a
 splice of individual spectral portions to form self contained
 spectra.}
 
-\requirement{Slice spectral channels}{Not started}{1}{}{}{} {It must be
+\requirement{Slice spectral channels}{Not started}{1}{0d}{}{} {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}{5d}{}{}
 {It must be possible to append rows from one scantable onto another}
 
@@ -907 +907 @@
 %two dual polarisation measurements.}
 
-\requirement{Support polarimetry}{Started}{1}{}{}{}
+\requirement{Support polarimetry}{Started}{1}{?}{}{}
 {All functions on the data (calibration, sky subtraction spectral
 mathematics) must support arbitrary, multiple polarisation (linear,
@@ -975 +975 @@
 together).
 
-\requirement{Spectra selection}{Started}{1}{}{}{}
+\requirement{Spectra selection}{Started}{1}{0d}{}{}
 {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}{0d}{}{}
 {An easy-to-use mechanism to select individual IFs, beams or
 polarisations is needed.}
@@ -995 +995 @@
 available as a plot overlay.}
 
-\requirement{Auto-identify reference spectra}{Not started}{1}{}{}{}
+\requirement{Auto-identify reference spectra}{Not started}{1}{5d+}{}{}
 {When performing sky subtraction on many spectra simultaneously, the
 software should have a mechanism for identifying ``on'' and ``off''
@@ -1019 +1019 @@
 \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
@@ -1181 +1181 @@
 position etc) the data is being presented as.}
 
-\requirement{Positional Reference Frame}{Not started}{1}{}{}{} {The user
+\requirement{Positional Reference Frame}{Not started}{1}{0.2d}{}{} {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,
@@ -1196 +1196 @@
 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.}
@@ -1269 +1269 @@
 \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
 help from the local system administrators. This includes installation
-on a central ``NFS'' server as well as local desk-tops.}
-
-\requirement{Linux Support}{Started}{1}{}{}{}
+on a central ``NFS'' server as well as local desktops.}
+
+\requirement{Linux Support}{Started}{1}{3d}{}{}
 {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}
 
@@ -1290 +1290 @@
 software.}
 
-\requirement{MacOS/X support}{Not started}{1}{}{}{}
+\requirement{MacOS/X support}{Not started}{1}{3+d}{}{}
 {The software should run on MacOS/X}