Index: trunk/doc/design/ippSSDD.tex =================================================================== --- trunk/doc/design/ippSSDD.tex (revision 7783) +++ trunk/doc/design/ippSSDD.tex (revision 8140) @@ -649,5 +649,5 @@ \begin{table}[ht] \begin{center} -\caption{Nebulos Database Tables\label{tab:ImageServerTables}} +\caption{Nebulous Database Tables\label{tab:ImageServerTables}} \begin{tabular}{ll} \hline @@ -4747,6 +4747,8 @@ FITS Images will be used to transport images between the components of -the IPP. Non-standard FITS images representing triangular collections -of pixels may be used to store the static sky images. +the IPP. The Static Sky FITS Images will use standard rectangular +FITS images and mask values to identify pixels which are included in a +specific image. Astrometric transformations will be stored in the +image headers. FITS Tables will be used to store and transport tabular data, @@ -4755,20 +4757,29 @@ different table interactions. -XML files will be used to store and transport data which is not -well-suited to the rectangular form of FITS Tables. Hierarchical data -concepts and variable-length structures fall in this class. Examples -include mosaic astrometry description information and configuration -information. - SQL queries and C wrappers of SQL queries will be used as the direct interface to the databases. -Within IPP and Pan-STARRS in general, process-to-process communication -will be defined through auto-coded APIs which support a limited and -validated communication protocol. The APIs will be coded based on a -table which defines the allowed command set and the grammar to be -used. This mechanism will allow a single code block to define -inter-process communication methods for many Pan-STARRS subsystems, -including, within the IPP, the Scheduler-Controller communications. +\begin{tabular}{lll} +{\bf Interface} & {\bf Data} & {\bf Format} \\ +ippTools : PanTasks & image state info & psMetadataConfig \\ +PanTasks : ippTools & image state updates & ippTools CLI, psMetadataConfig \\ +PanTasks : ppImage & image operations & ppImage CLI, recipe files \\ +ppImage : psphot & detrend images & pmReadout in pmFPA structure \\ +ppImage : psastro & detected objects & pmSources in pmFPA structure \\ +DVO/getstar : psastro & ref object coords & FITS Tables \\ +psphot : DVO/addstar & detection tables & FITS Tables \\ +psastro : DVO/addstar & astrometry & FITS Header \\ +ippTools : ppImage & detrend images & FITS Images, psMetadataConfig \\ +PanTasks : ppMerge & image operations & ppMerge CLI, recipe files \\ +PanTasks : ppStats & image info & ppStats CLI, recipe files \\ +PanTasks : ppNorm & image results & ppNorm CLI, recipe files \\ +DVO : relphot & DVO database & FITS Tables \\ +DVO : relastro & DVO database & FITS Tables \\ +psastro : stac & astrometry & FITS Header \\ +psphot : poisub & psf model & psMetadataConfig \\ +psphot : poisub & detected stars & FITS Table \\ +Static Sky : stac & astrometry & FITS Header \\ + +\end{tabular} \subsection{External Interfaces} @@ -4776,29 +4787,39 @@ This subsection describes the interfaces between the IPP and other Pan-STARRS systems and the external clients. The interfaces are -illustrated in Figure~\ref{fig:overview}. +illustrated in Figure~\ref{fig:overview}. The details of the IPP +interfaces with other external subsystems are specified in the ICDs +between those subsystems. + +\subsubsection{Camera} + +Images are pulled from the Summit Pixel Server, part of the Camera +team's purview, via the Data Store mechanism. The locations of the +files are specified by the Data Store (see the Data Store SDD, +PSDC-940-010). IPP grabs these via {\tt http}. This interface is +described in detail by the Camera-IPP ICD (PSDC-940-003). \subsubsection{OTIS} -The IPP Scheduler may query OTIS for a list of new images and -metadata. The locations of those images in the Summit Pixel Server is -sent back as a table, and all metadata may be sent to the IPP as a -collection of FITS Tables. The IPP also may send quality assessment -information for each FPA and major frame by writing out FITS tables -and notifying OTIS of the presence of the new tables. - -\subsubsection{Camera} - -Images are pulled from the Summit Pixel Server, part of the Camera -team's purview. The locations of the files are sent by OTIS. IPP may -grab these via {\tt http} commands or via {\tt NFS} or another network -file exchange protocol. The IPP notifies OTIS (and Camera) when each -image has been received. +The IPP Scheduler receives metadata from OTIS as a collection of FITS +Tables. The IPP sends quality assessment information for each FPA and +major frame as FITS tables. These metadata tables are exchanged in +both directions using the Data Store mechanism (PSDC-940-010). The +interface is described in detail by the OTIS-IPP ICD (PSDC-940-004). + +\subsubsection{MOPS} + +Data will be sent to MOPS from the IPP as part of the Phase 4 +analysis. The data to be transfered include: +\begin{itemize} +\item Image Metadata tables - to be transferred as FITS tables +\item Transient Detections - to be transferred as FITS tables +\end{itemize} +This interface uses the Data Store mechanism (PSDC-940-010), and is +described in detail by the IPP-MOPS ICD (PSDC-940-005). \subsubsection{PSPS} -Data will be sent to PSPS from the IPP as part of a daily or weekly -analysis process on the Static Sky. The data will be pushed from the -IPP to PSPS when they are available. The data to be transfered -include: +Data is sent to PSPS from the IPP on a regular basis. The data to be +transfered include: \begin{itemize} \item Static Sky images - to be transferred as FITS images or @@ -4808,14 +4829,6 @@ \item Detections \& Object associations - to be transferred as FITS tables. \end{itemize} - -\subsubsection{MOPS} - -Data will be sent to MOPS from the IPP as part of the Phase 4 -analysis. The data will be pushed from the IPP to MOPS when they are -available. The data to be transfered include: -\begin{itemize} -\item Image Metadata tables - to be transferred as FITS tables -\item Orphaned Detections - to be transferred as FITS tables -\end{itemize} +This interface uses the Data Store mechanism (PSDC-940-010), and is +described in detail by the IPP-PSPS ICD (PSDC-940-006). \subsubsection{Other Preferred Client Science Pipelines}