IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Feb 16, 2006, 8:57:51 AM (20 years ago)
Author:
eugene
Message:

changes leading to CDR

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/design/ippSSDD.tex

    r6167 r6434  
    1 %%% $Id: ippSSDD.tex,v 1.7 2006-01-22 09:54:47 eugene Exp $
    21\documentclass[panstarrs]{panstarrs}
    32
     
    1110\project{Pan-STARRS Image Processing Pipeline}
    1211\organization{Institute for Astronomy}
    13 \version{00}
    14 \docnumber{PSDC-430-011}
     12\version{DR.02}
     13\docnumber{PSDC-430-014}
    1514
    1615% allow paragraphs to be listed in TOC for now
     
    2322\RevisionsStart
    2423% version     Date         Description
    25 DR.01     & 2004.01.01 & First draft  \\ \hline
    26 DR.02     & 2004.03.05 & Second draft \\ \hline
    27 DR.03     & 2004.03.25 & Section reorganization \\ \hline
    28 DR.04     & 2004.04.13 & Most sections fleshed out \\ \hline
    29 DR.05     & 2004.04.29 & Reorganization for consistency \\ \hline
    30 DR.06     & 2004.10.21 & Major revision in prep of PDR \\ \hline
     24DR.01     & 2006.01.19 & First draft release to CDR committee \\ \hline
     25DR.02     & 2006.01.22 & Second draft release to CDR committee \\ \hline
    3126\RevisionsEnd
    3227
     
    9691achieve the requirements specified by the Pan-STARRS PS-1 IPP Software
    9792Requirements Specification (SRS; PSDC-430-005).  The requirements flow
    98 begun in the SGS and SCD and continued in the SRS is used to guide the
    99 design presented here.
     93which began in the SGS and Pan-STARRS system SCD, and continued in the
     94IPP SRS and the IPP SCD, is used to guide the design presented here.
    10095
    10196\subsection{Requirements Definitions}
     
    135130PSDC-430-007  &   Pan-STARRS IPP PSLib Supplementary Design Requirements Specification \\ \hline
    136131PSDC-430-010  &   Pan-STARRS IPP Perl Code Conventions \\ \hline
     132PSDC-430-011  &   Pan-STARRS IPP System Concept Definition \\ \hline
    137133PSDC-430-012  &   Pan-STARRS IPP Modules Supplementary Design Requirements Specification \\ \hline
    138134PSDC-430-014  &   Pan-STARRS IPP PS-1 Cluster Support \\ \hline
     
    140136Posix Standard & Open Group Based Specifications Issue 6, IEEE Std 1003.1, 2003 \\
    141137\DocumentsEnd
    142 
    143 \tbd{add the other subsystem SDDs}
    144138
    145139\section{Subsystem Overview}
     
    232226\subsection{System Design Decisions}
    233227
    234 \tbd{add discussion of the AP survey and other survey projects}
    235 
    236228Since Pan-STARRS is a survey project, all data from the telescopes
    237229will be uniformly analyzed by the Pan-STARRS Image Processing Pipeline
     
    263255elements.
    264256
    265 \subsection{Analysis Tasks and Stages}
    266 
    267 \tbd{this discussion is confusing, and even more so in the context of
    268   the PanTasks definition of a 'task'}.
    269 
    270 Specific programs are required to perform the processing steps listed
    271 above.  These can be divided into well-defined analysis stages, each
    272 of which operates on a particular unit of data, such as a single OTA
    273 image or a collection of astronomical objects.  Analysis tasks
    274 representing the different analysis stages are performed on the IPP
    275 computer cluster.  Note the distinction between the generic analysis
    276 {\em stage} and a specific analysis {\em task}.  An analysis stage
    277 represents a type of analysis which is performed, such as the basic
    278 image calibration and object detection analysis.  An analysis task is
    279 a particular realization of an analysis stage, e.g., the analysis of
    280 OTA number 61 from exposure 654321 to produce a specific set of output
    281 data products.  The analysis stages are discussed in detail in
    282 Section~\ref{sec:AnalysisStages}.
     257\subsection{Analysis Stages, Programs, and Libraries}
     258
     259The processing steps listed above can be divided into well-defined
     260analysis stages, each of which operates on a particular unit of data,
     261such as a single OTA image or a collection of astronomical objects.
     262The different analysis stages defined by the IPP are discussed in
     263Sections~\ref{sec:AnalysisStages} - \ref{sec:MiscStages}.  The
     264analysis defined by these analysis stages is further divided into
     265specific programs which perform the particular operation.  Some
     266analysis stages are primarily defined by a single programs; others
     267require multiple programs and substages.  It is also possible for a
     268single program to be involved in multiple analysis stages.  The major
     269IPP analysis programs are discussed in some detail in
     270Section~\ref{sec:AnalysisPrograms}.  Other important programs in the
     271collection called \code{ippTools} are used to define the analysis
     272stages and their interrelationships (Section~\ref{sec:ipptools}).  The
     273IPP software hierarchy is further divided into \code{psModules}
     274(representing complex analysis operations, often astronomical in
     275nature) and \code{psLib}, the data and analysis foundation library
     276(Section~\ref{sec:SoftwareHierarchy}).
     277
     278Analysis tasks representing the different analysis stages are
     279performed on the IPP computer cluster.  Note the distinction between
     280the generic analysis {\em stage} and a specific analysis {\em task}.
     281An analysis stage represents a type of analysis which is performed,
     282such as the basic image calibration and object detection analysis.  An
     283analysis task is a particular realization of an analysis stage, e.g.,
     284the analysis of OTA number 61 from exposure 654321 to produce a
     285specific set of output data products.  The analysis stages are
     286discussed in detail in Section~\ref{sec:AnalysisStages}.
    283287
    284288A particular stage may process individual images, collections of
     
    507511monitor the age of images and delete them on some schedule.  This
    508512functionality currently resides in the IPP Scheduler
    509 (Section~\ref{sec:scheduler}).
     513(Section~\ref{sec:pantasks}).
    510514
    511515As shown in Figure~\ref{fig:Nebulous}, Nebulous consists of the
     
    521525\begin{center}
    522526\resizebox{4.5in}{!}{\includegraphics{pics/ImageServer}}
    523 \caption{The components of the IPP Image Server.}
    524 \label{fig:ImageServer}
     527\caption{The components of Nebulous, the IPP Image/File Server.}
     528\label{fig:Nebulous}
    525529\end{center}
    526530\end{figure}
     
    11061110detection data, the {\tt Regions} table allows for multiple computers
    11071111to serve the database tables.  The region file specifies the machine
    1108 which stores the specific table.  Figure~\ref{fig:APDBRegions}
     1112which stores the specific table.  Figure~\ref{fig:DVOskyregions}
    11091113illustrates schematically the subdivision of the sky and the
    11101114association between different levels of the hierarchy with different
     
    15821586
    15831587\subsection{PanTasks : the IPP Scheduler}
     1588\label{sec:pantasks}
    15841589
    15851590PanTasks is the IPP tool which manages the sequencing of data analysis
     
    21482153\begin{center}
    21492154\includegraphics[scale=0.85,angle=-90]{pics/pantasks.05.ps}
    2150 \caption{\label{queues} pcontrol job states.  Transitions labeled Ux
     2155\caption{\label{JobStates} pcontrol job states.  Transitions labeled Ux
    21512156  are issued by the pcontrol user (including PanTasks).  Transitions
    21522157  labeled Px are initiated by pcontrol.  Transitions labeled Tx are
     
    22502255\begin{center}
    22512256\includegraphics[scale=0.85,angle=-90]{pics/pantasks.07.ps}
    2252 \caption{\label{queues} PanTasks queues and MDDB tables}
     2257\caption{\label{Pclient} Pclient monitor loop.}
    22532258\end{center}
    22542259\end{figure}
     
    31263131%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    31273132
    3128 \section{System Design : Miscellaneous Tasks}
     3133\section{System Design : Miscellaneous Analysis Stages}
     3134\label{sec:MiscStages}
    31293135
    31303136This section discusses additional operations which are performed by
     
    31713177
    31723178\section{Software Hierarchy}
     3179\label{sec:SoftwareHierarchy}
    31733180
    31743181In order to facilitate testing and development, and to encourage
     
    32293236\subsection{IPP Analysis Programs}
    32303237
    3231 \tbd{clean this up}
    3232 
    32333238The major IPP processing tasks are organized into stages, which
    32343239consist of multiple modules.  Each stage represents a collection of
     
    32403245images from multiple telescopes and search for transients).
    32413246
    3242 \section{Top-Level IPP Analysis Routines}
     3247\section{Top-Level IPP Analysis Programs}
     3248\label{sec:AnalysisPrograms}
    32433249
    32443250The IPP uses a handful of high-level analysis routines which perform
     
    39043910
    39053911\section{IPPTools}
     3912\label{sec:ipptools}
    39063913
    39073914PanTasks is the IPP tool which manages the sequencing of data analysis
     
    54015408
    54025409\section{AP Database Table Contents}
    5403 \label{sec:APDBTableContents}
     5410\label{sec:DVOTableContents}
    54045411
    54055412\begin{table}[bh]
     
    57005707\begin{table}[bh]
    57015708\begin{center}
    5702 \caption{Database Hosts\label{tab:APDBHosts}}
     5709\caption{Database Hosts\label{tab:DVOHosts}}
    57035710\begin{tabular}{lll}
    57045711\hline
Note: See TracChangeset for help on using the changeset viewer.