Changeset 650 for trunk/admin


Ignore:
Timestamp:
06/02/05 09:22:29 (19 years ago)
Author:
mar637
Message:

added priority 1 estimates

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/admin/requirements2.tex

    r647 r650  
    300300produce plots of publishable quality.}
    301301
    302 \subrequirement{Histogram plots}{Not started}{1}{}{}{} {As well as line
     302\subrequirement{Histogram plots}{Not started}{1}{0.5d}{}{} {As well as line
    303303plots, there needs to be an option to plot spectra in ``Histogram''
    304304mode}
     
    307307The user must be able to specify:
    308308
    309 \subrequirement{Line Thickness}{Started}{1}{}{}{}{}
    310 
    311 \subrequirement{Character size}{Not started}{1}{}{}{}{}
    312 
    313 \subrequirement{Colours}{Started}{1}{}{}{}{}
    314 
    315 \subrequirement{Line styles}{Not started}{1}{}{}{}{}
     309\subrequirement{Line Thickness}{Started}{1}{0.1d}{}{}{}
     310
     311\subrequirement{Character size}{Not started}{1}{0.1d}{}{}{}
     312
     313\subrequirement{Colours}{Started}{1}{0.75d}{}{}{}
     314
     315\subrequirement{Line styles}{Not started}{1}{0.5d}{}{}{}
    316316
    317317\subrequirement{Position of axis ticks}{Done1}{2}{}{}{}{}
     
    321321need basic.}
    322322
    323 \subrequirement{Non-interactive hard copies}{Not started}{1}{}{}{}
     323\subrequirement{Non-interactive hard copies}{Not started}{1}{2d}{}{}
    324324{It must be possible to produce hard copiers without an interactive
    325325(i.e X11) plotter starting}.
     
    402402FITs file, for user specific analysis.}
    403403
    404 \requirement{Plot line catalog overlays}{Not started}{1}{}{}{} {Line markers overlays,
     404\requirement{Plot line catalog overlays}{Not started}{1}{3d}{}{} {Line markers overlays,
    405405read from a catalogue should be optionally available. This would
    406406include the full Lovas catalogue, the JPL line catalogue and radio
     
    418418components}
    419419
    420 \requirement{Plot residual data}{Started}{1}{}{}{}
     420\requirement{Plot residual data}{Started}{1}{0.5d}{}{}
    421421{It should be possible to plot the residual data with or without
    422422subtraction of fit functions. This includes plotting the spectra with
     
    500500\requirement{Read PSRFITS}{Deferred}{}{}{}{}{PSRFIT for pulsar spectroscopy.}
    501501
    502 \requirement{Read online data}{Not started}{1}{}{}{}
     502\requirement{Read online data}{Not started}{1}{0.1d}{}{}
    503503{For online analysis, the software should be able to read an rpfits
    504504file which is is still currently open for writing by the telescope
     
    525525Python, SuperMongo etc.}
    526526
    527 \requirement{Header writing}{Started}{1}{}{}{}
     527\requirement{Header writing}{Started}{1}{0d}{}{}
    528528{The exported data should retain as much header data as possible. It
    529529should also be possible to request specific data be written in the
     
    535535$\S$\ref{sec:issues} for a list of currently known issues.}
    536536
    537 \requirement{Append output files}{Not started}{1}{}{}{} {It must be possible
     537\requirement{Append output files}{Not started}{1}{3d}{}{} {It must be possible
    538538to append spectra to existing output files, specifically sdfits and
    539539asap output files.}
     
    631631polarisation products should be fit independently.}
    632632
    633 \requirement{Export fit parameters}{Not started}{1}{}{}{}
     633\requirement{Export fit parameters}{Not started}{1}{1d}{}{}
    634634{There should be an easy way of exporting the fit parameter from
    635635multiple spectra, e.g. as an ASCII table.}
     
    641641components or the amplitude ratio etc.)}
    642642
    643 \subrequirement{Specific constrained fitting}{Not started}{1}{}{}{}
     643\subrequirement{Specific constrained fitting}{Not started}{1}{4d}{}{}
    644644{Before arbitrary constrained fitting is available, support for
    645645specific cases, such as the NH$_3$ hyperfine transition, should e
     
    668668subtracted from the data (e.g. baseline polynomials).}
    669669
    670 \requirement{Gaussian line area}{Not started}{1}{}{}{}
     670\requirement{Gaussian line area}{Not started}{1}{0.2d}{}{}
    671671{Optionally the area under a fitted Gaussian should be calculated for
    672672the user.}
     
    749749disrupt the reference/source sequence.
    750750
    751 \requirement{Spectra flagging}{Started}{1}{}{}{}
     751\requirement{Spectra flagging}{Started}{1}{1d}{}{}
    752752{The user must be able to set an entire spectra or part thereof
    753753(individual polarisation, IF etc) as being invalid.}
    754754
    755 \requirement{Channel flagging}{Started}{1}{}{}{}
     755\requirement{Channel flagging}{Started}{1}{0.5d}{}{}
    756756{The user must be able to indicate an individual spectral point or
    757757range of spectral points are invalid. This should be applied to an
    758758individual spectra, or set of spectra.}
    759759
    760 \subrequirement{Flagged channel plotting}{???}{1}{}{}{} {When plotting data
     760\subrequirement{Flagged channel plotting}{Done1}{1}{}{}{} {When plotting data
    761761with flagged spectral channels, the plotting should left a gap (blank)
    762762in the plotted data|}.
     
    806806integration or rms.}
    807807
    808 \subrequirement{Average spectra with velocity shift}{Not started}{1}{}{}{}
     808\subrequirement{Average spectra with velocity shift}{Not started}{1}{0.2d}{}{}
    809809{If the velocity of the spectra to be averaged is different, the data
    810810should be aligned in velocity. The user should be able to turn this
     
    870870displayed and analysed using other functions (max, rms etc).}
    871871
    872 \requirement{Spectral calculator}{Started}{1}{}{}{}
     872\requirement{Spectral calculator}{Started}{1}{?}{}{}
    873873{Complex experiment specific processing can often be done using a
    874874series of the simple of basic functions. A spectral calculator options
     
    883883``split'' into separate spectra.
    884884
    885 \requirement{Slice data}{Not started}{1}{}{}{} {It must be possible to
     885\requirement{Slice data}{Not started}{1}{10d}{}{} {It must be possible to
    886886take multi IF, multibeam or polarisation data and split out the a
    887887splice of individual spectral portions to form self contained
    888888spectra.}
    889889
    890 \requirement{Slice spectral channels}{Not started}{1}{}{}{} {It must be
     890\requirement{Slice spectral channels}{Not started}{1}{0d}{}{} {It must be
    891891possible to select a range of spectral channels to form self contained
    892892spectra. The channel selection may be different for different IFs.}
    893893
    894 \requirement{Merge scantables}{Not started}{1}{}{}{}
     894\requirement{Merge scantables}{Not started}{1}{5d}{}{}
    895895{It must be possible to append rows from one scantable onto another}
    896896
     
    907907%two dual polarisation measurements.}
    908908
    909 \requirement{Support polarimetry}{Started}{1}{}{}{}
     909\requirement{Support polarimetry}{Started}{1}{?}{}{}
    910910{All functions on the data (calibration, sky subtraction spectral
    911911mathematics) must support arbitrary, multiple polarisation (linear,
     
    975975together).
    976976
    977 \requirement{Spectra selection}{Started}{1}{}{}{}
     977\requirement{Spectra selection}{Started}{1}{0d}{}{}
    978978{The software needs an easy-to-use mechanism to select either
    979979individual or multiple spectra for viewing, parallel processing
    980980etc.}
    981981
    982 \requirement{Beam/IF selection}{Started}{1}{}{}{}
     982\requirement{Beam/IF selection}{Started}{1}{0d}{}{}
    983983{An easy-to-use mechanism to select individual IFs, beams or
    984984polarisations is needed.}
     
    995995available as a plot overlay.}
    996996
    997 \requirement{Auto-identify reference spectra}{Not started}{1}{}{}{}
     997\requirement{Auto-identify reference spectra}{Not started}{1}{5d+}{}{}
    998998{When performing sky subtraction on many spectra simultaneously, the
    999999software should have a mechanism for identifying ``on'' and ``off''
     
    10191019\subsection{Plugins}
    10201020
    1021 \requirement{Plugins}{Started}{1}{}{}{}
     1021\requirement{Plugins}{Started}{1}{?}{}{}
    10221022{The package should support ``plugins'', user definable
    10231023functions for specific processing. The plugin code must have full
     
    11811181position etc) the data is being presented as.}
    11821182
    1183 \requirement{Positional Reference Frame}{Not started}{1}{}{}{} {The user
     1183\requirement{Positional Reference Frame}{Not started}{1}{0.2d}{}{} {The user
    11841184should be able to specify the reference frame (Epoch,Equinox etc) for
    11851185which is used for exporting data, simple mapping output etc. J2000,
     
    11961196retained. The user may wish to enter some specific values by hand.
    11971197
    1198 \requirement{View and edit header data}{Started}{1}{}{}{}
     1198\requirement{View and edit header data}{Started}{1}{?}{}{}
    11991199{All header data should be viewable and editable by the user. This
    12001200includes changes such as scaling the given Tsys values.}
     
    12691269\section{Installation}
    12701270
    1271 \requirement{Easy installation}{Started}{1}{}{}{}
     1271\requirement{Easy installation}{Started}{1}{?}{}{}
    12721272{It must be possible for astronomers to install the software at their
    12731273own institute with either a moderate amount of OS experience or some
    12741274help from the local system administrators. This includes installation
    1275 on a central ``NFS'' server as well as local desk-tops.}
    1276 
    1277 \requirement{Linux Support}{Started}{1}{}{}{}
     1275on a central ``NFS'' server as well as local desktops.}
     1276
     1277\requirement{Linux Support}{Started}{1}{3d}{}{}
    12781278{The software must run on major flavours of Linux
    12791279(Fedora/Redhat, Debian, etc).}
    12801280
    1281 \subrequirement{Solaris Support}{Started}{1}{}{}{}
     1281\subrequirement{Solaris Support}{Started}{1}{?}{}{}
    12821282{The software must run on Solaris}
    12831283
     
    12901290software.}
    12911291
    1292 \requirement{MacOS/X support}{Not started}{1}{}{}{}
     1292\requirement{MacOS/X support}{Not started}{1}{3+d}{}{}
    12931293{The software should run on MacOS/X}
    12941294
Note: See TracChangeset for help on using the changeset viewer.