Index: trunk/doc/release.2015/ps1.datasystem/datasystem.tex
===================================================================
--- trunk/doc/release.2015/ps1.datasystem/datasystem.tex	(revision 40695)
+++ trunk/doc/release.2015/ps1.datasystem/datasystem.tex	(revision 40696)
@@ -1,12 +1,7 @@
-% \documentclass[preprint2]{emulateapj} % works for 2-column
 \documentclass[iop,floatfix]{emulateapj}
-% \documentclass[iop,floatfix,onecolumn]{emulateapj}
-% \documentclass[12pt,preprint]{aastex}
 % \documentclass[10pt,preprint]{aastex} % use for 1-column
-% \documentclass[preprint]{aastex}
 % \pdfoutput=1
 
 %\RequirePackage{deluxetable} -- included by aastex?
-%\RequirePackage{nsfprop} % defines \subsubsubsection but breaks 2-col
 \RequirePackage{color}
 \RequirePackage{code}
@@ -15,4 +10,6 @@
 \usepackage[T1]{fontenc}% (2) specify encoding
 
+% these options allow the code to swap between figure types & versions:
+
 % online version may use color, but print version needs b/w
 \def\plotmode{col}
@@ -22,6 +19,5 @@
 \def\plotext{ps}
 
-%\def\picdir{/home/eugene/chipresid.20140404}
-\def\picdir{/data/pikake.2/eugene/chipresid.20140404}
+\def\picdir{figures}
 
 % Pick a terse version of the title here;
@@ -232,17 +228,4 @@
 to reduce this large number of exposures.  
 
-% Finally,
-% Section~\ref{sec:discussion} presents a discussion of some of the
-% lessons learned in the creation of the IPP, and its utility in
-% reducing data from other cameras and telescopes.
-
-%% {\color{red} {\em Note: These papers are being placed on arXiv.org to
-%%     provide crucial support information at the time of the public
-%%     release of Data Release 1 (DR1). We expect the arXiv versions to
-%%     be updated prior to submission to the Astrophysical Journal in
-%%     January 2017. Feedback and suggestions for additional information
-%%     from early users of the data products are welcome during the
-%%     submission and refereeing process.}}
-
 \section{Overview of Pan-STARRS Data Processing}
 \label{sec:overview}
@@ -277,5 +260,5 @@
   ingests the calibrated measurements from the IPP, MOPS, and others
   and generates a high-availability database with web-based
-  interactions for public consumption \citep[][]{flewelling2017}.
+  interactions for public consumption (Paper VI).
 
 \end{itemize}
@@ -301,6 +284,4 @@
 emphasis on the analysis, calibration, and database ingest stages.
 The MOPS is described in detail by \cite{2013PASP..125..357D}.
-
-% the summit systems are described by \note{REF?}.
 
 \begin{figure*}[htbp]
@@ -361,10 +342,10 @@
 Petrosian aperture photometry, etc).  The results of the stack
 photometry analysis are used to drive a forced-photometry analysis of
-the warp images.  These analysis steps are discussed in detail by
-\citet[][]{magnier2017.analysis}.  The data products from the camera,
-stack, and forced-warp photometry analysis stages are ingested into
-the internal calibration database (DVO, the Desktop Virtual
-Observatory) and used for photometric and astrometric calibrations
-\citet[see Section~\ref{sec:DVO} and][]{magnier2017.calibration}.
+the warp images.  These analysis steps are discussed in detail in
+Paper IV.  The data products from the camera, stack, and forced-warp
+photometry analysis stages are ingested into the internal calibration
+database (DVO, the Desktop Virtual Observatory) and used for
+photometric and astrometric calibrations (see Section~\ref{sec:DVO}
+and Paper V).
 
 \subsection{Data Access and Distribution}
@@ -384,6 +365,5 @@
 (PV1 \& PV2), the data were ingested into the PSPS database system and
 made available to the PS1SC community through a web portal based at
-the IfA as well as the MAST portal \citep[see][for full
-  details]{flewelling2017}.
+the IfA as well as the MAST portal (see Paper VI for full details).
 
 \section{IPP Data Processing Stages}
@@ -401,11 +381,4 @@
 \hline
 {\bf Stage} & {\bf Primary Table} & {\bf Secondary Table(s)} & {\bf Key} \\% & {\bf Notes} \\
-%%D \begin{deluxetable}{llll}
-%%D   \tablecolumns{5}
-%%D   \tablewidth{0pc}
-%%D   \tablecaption{GPC1 Database Schema Outline}
-%%D   \tablehead{\colhead{Stage} & \colhead{Primary Table} & \colhead{Secondary Table} & \colhead{Key}} % & \colhead{Notes}}
-%%D   \startdata
-%\hline
   \ippstage{summitcopy}   & \ippdbtable{pzDataStore}  &                                  & \\% & Lists locations to check for new exposures.\\
                           & \ippdbtable{summitExp}    & \ippdbtable{summitImfile}        & \ippdbcolumn{summit_id} \\% & Exposures available at the telescope.\\
@@ -445,9 +418,7 @@
                           & \ippdbtable{lapRun}       & \ippdbtable{lapExp}              & \ippdbcolumn{lap_id} \\% & \\
   \ippstage{remote}       & \ippdbtable{remoteRun}    & \ippdbtable{remoteComponent}     & \ippdbcolumn{remote_id} \\% & \\
-%%D \enddata
 \hline
 \end{tabular}
 \label{tab:database_schema}
-%%D \end{deluxetable}
 \end{center}
 \end{table*} 
@@ -602,5 +573,5 @@
 For GPC1, the \ippstage{registration} stage is also the stage at which
 the \ippprog{burntool} analysis is run.  This analysis is more
-completely described in \citet{waters2017}.  In brief, the
+completely described in Paper III.  In brief, the
 \ippprog{burntool} program identifies bright sources on the image, and
 identifies persistence trails that result from the incomplete transfer
@@ -653,33 +624,15 @@
 not been as critical of a requirement as originally expected.
 
-%% In the \ippstage{chip} stage,
-%% the individual OTA image files are processed independently in parallel
-%% within the data processing cluster.  \note{move this to kihei
-%%   discussion?} Within the processing computer cluster, most of the
-%% data storage resources are in the form of computers with large raids
-%% as well as substantial processing capability.  The processing system
-%% attempts to locate one copy of specific raw registered data on
-%% pre-defined computers that have been set as storage targets for that
-%% OTA.  The processing system is aware of this data localization and
-%% attempts to target the processing for each OTA to the machine on which
-%% the data for that detector is stored.  The output products are then
-%% primarily saved back to the same machine.  This ``targetted'' processing
-%% was an early design choice to minimize the system wide network load
-%% during processing.  In practice, as computer disks filled up at
-%% different rates, the data has not been localized to a very high
-%% degree.  
-
 The actual image processing is performed by the \ippprog{ppImage}
 program.  This program reads the raw data into memory and applies the
-detrend corrections \citep[see][]{waters2017} to each cell in the OTA
-(stored as different extensions in the FITS file format), and then
-mosaics the cells into a single contiguous \ippstage{chip} stage
-image.  This step also creates in memory additional images to hold the
-mask data, which indicates which pixels may not be valid, and the
-variance image, constructed as the Poissonian noise on the number of
-electrons detected based on the original pixel value and the detector
-gain.  A background model is then fit across the image and subtracted
-to remove the expected contribution from the sky
-\citep[see][]{waters2017} for details.
+detrend corrections (see Paper III) to each cell in the OTA (stored as
+different extensions in the FITS file format), and then mosaics the
+cells into a single contiguous \ippstage{chip} stage image.  This step
+also creates in memory additional images to hold the mask data, which
+indicates which pixels may not be valid, and the variance image,
+constructed as the Poissonian noise on the number of electrons
+detected based on the original pixel value and the detector gain.  A
+background model is then fit across the image and subtracted to remove
+the expected contribution from the sky (see Paper III for details).
 
 With the image calibration procedure finished, object identification
@@ -689,5 +642,5 @@
 this analysis, removing the need to write out and re-read the image
 data.  The details of the detection and characterization of the
-sources in the image are provided in \citet{magnier2017.analysis}.  
+sources in the image are provided in Paper IV.
 
 The results of the image processing are then written to disk,
@@ -715,23 +668,4 @@
 in which case an entry for this exposure is added to the \ippdbtable{camRun}
 table, and processing continues.
-
-%% The \ippstage{chip} processing stage consists of: reading the raw image into
-%% memory, applying the detrending steps \citep[see][]{waters2017},
-%% stiching the individual OTA cells into a single chip image, detection
-%% and characterization of the sources in the image
-%% \citep[see][]{magnier2017b}, and output of the various data products.
-%% These include the detrended chip image, variance image, and mask
-%% image, as well as the FITS catalog of detected sources.  The PSF model
-%% and background model are also saved, along with a processing log.  A
-%% selection of summary metadata describing the processing results are
-%% saved and written to the processing database along with the completion
-%% status of the process.  Finally, binned chip images are generated (on
-%% two scales, binned by 16 and 256 pixels) for use in the visualization
-%% system of the processing monitor tool. \note{describe elsewhere?}
-
-%% The database structure for the \stage{chip} stage mimics that of raw
-%% data, with a \ippdbtable{chipRun} characterizing the processing of a
-%% single exposure, mapping to a set of \ippdbtable{chipProcessedImfile}
-%% entries for each OTA via a common \ippdbcolumn{chip_id}.  
 
 \subsection{Camera Calibration}
@@ -755,11 +689,10 @@
 to help guarantee a solution in the case of a modest pointing error.
 The guess astrometry is used to match the reference catalog to the
-observed stellar positions in the focal plane coordinate system
-\citep[see][]{magnier2017.calibration}.  Early on in the PS1SC
-mission, the nightly processing (PV0) used a reference catalog based
-on a combination of external catalogs (2MASS, Tycho, USNO).  Later, 
-reference catalogs based on Pan-STARRS data was used.  For the $3\pi$ PV3 analysis,
-the reference catalog was based on Pan-STARRS data from the PV2
-analysis \citep[see][for more details]{magnier2017.calibration}.
+observed stellar positions in the focal plane coordinate system.
+Early on in the PS1SC mission, the nightly processing (PV0) used a
+reference catalog based on a combination of external catalogs (2MASS,
+Tycho, USNO).  Later, reference catalogs based on Pan-STARRS data was
+used.  For the $3\pi$ PV3 analysis, the reference catalog was based on
+Pan-STARRS data from the PV2 analysis (see Paper V for more details).
 
 Once an acceptable match is found, the astrometric calibration of the
@@ -787,7 +720,7 @@
 so a fixed color transformation is used to generate synthetic w-band
 photometry from the \rps\ \& \ips\ photometry.  For more details, see
-\cite{magnier2017.calibration}.  The result of these calibrations is
-stored as a single multi-extension FITS table containing the results
-from each OTA as a separate extension.
+Paper V.  The result of these calibrations is stored as a single
+multi-extension FITS table containing the results from each OTA as a
+separate extension.
 
 In addition to the astrometric and photometric calibrations, the
@@ -884,5 +817,5 @@
 \ippstage{chip} stage images (including the variance images and the
 updated masks) to the \ippprog{pswarp} program.  For details on the
-warping algorithm, see \cite{waters2017}.  The outputs of this program
+warping algorithm, see Paper III.  The outputs of this program
 are the geometrically transformed images (signal, variance, and mask)
 containing all input pixels warped to the common skycell pixel grid,
@@ -892,8 +825,4 @@
 extraction tools at the MAST archive at STScI as part of the DR2 data
 release.
-
-%% A catalog is
-%% also generated containing the locations of sources from the input
-%% catalog that fall within area of the \ippstage{warp}.
 
 When the \ippstage{warp} jobs have completed, an entry for the skycell
@@ -928,12 +857,11 @@
 generated for the nightly groups and for the full depth using all
 exposures, producing ``deep stacks''.  In addition, a ``best seeing''
-set of stacks have been produced using image quality cuts described by
-\citet[][Paper VII]{huber2017}.  We have also generated out-of-season
-stacks for the Medium Deep fields, in which all images {\em not} from a
-particular observing season for a field are combined into a stack.
-These later stacks are useful as deep templates when studying
-long-term transient events in the Medium Deep fields as they are not
-(or less) contaminated by the flux of the transients from a given
-season.
+set of stacks have been produced using image quality cuts described in
+Paper VII.  We have also generated out-of-season stacks for the Medium
+Deep fields, in which all images {\em not} from a particular observing
+season for a field are combined into a stack.  These later stacks are
+useful as deep templates when studying long-term transient events in
+the Medium Deep fields as they are not (or less) contaminated by the
+flux of the transients from a given season.
 
 When a given set of \ippstage{stack} stage processing is defined,
@@ -951,5 +879,5 @@
 and catalogs to the \ippprog{ppStack} program, which performs the
 image combinations.  Input warps are combined based on a weighting
-defined by the median variance for each image; see~\cite{waters2017}
+defined by the median variance for each image; see~Paper III
 for details on the stack combination algorithm.  In addition to the
 standard image, mask, and variance produced at other stages,
@@ -987,17 +915,17 @@
 The input images are passed to the \ippprog{psphotStack} program which
 does the analysis.  The stack photometry algorithms are described in
-detail in \cite{magnier2017.analysis}.  In short, sources are detected
-in all 5 filter images down to the $5\sigma$ significance.  The
-collection of detected sources is merged into a single master list.
-If a source is detected in at least two bands, or only in \yps{} band,
-then a PSF model is fitted to the pixels of the other bands in which
-the source was not detected.  This forced photometry results in lower
-significance measurements of the flux at the positions of objects
-which are thought to be real sources, by virtue of triggering a
-detection in at least two bands.  The relaxed limit for \yps{} band is
-included to allow for searches of \yps{} dropout objects: it is known
-that faint, high-redshift quasars may be detected in \yps{} band only.
-Sources detected only in \yps{} band are therefore more likely to have
-a higher false-positive rate than the other stack sources.  The
+detail in Paper IV.  In short, sources are detected in all 5 filter
+images down to the $5\sigma$ significance.  The collection of detected
+sources is merged into a single master list.  If a source is detected
+in at least two bands, or only in \yps{} band, then a PSF model is
+fitted to the pixels of the other bands in which the source was not
+detected.  This forced photometry results in lower significance
+measurements of the flux at the positions of objects which are thought
+to be real sources, by virtue of triggering a detection in at least
+two bands.  The relaxed limit for \yps{} band is included to allow for
+searches of \yps{} dropout objects: it is known that faint,
+high-redshift quasars may be detected in \yps{} band only.  Sources
+detected only in \yps{} band are therefore more likely to have a
+higher false-positive rate than the other stack sources.  The
 parameters of the PSF model are allowed to vary with position in the
 skycell.  The PSF model is also used to convolve the analytical galaxy
@@ -1085,8 +1013,4 @@
 in question is large compared to the FWHM of the PSF.
 
-%% The IPP team initially explored the option of convolving each input
-%% warp to a single target PSF chosen to match the worst of the input
-%% images for a given stack.  
-
 The IPP analysis solves this problem by using the sources
 detected in the stack images and performing forced photometry on the
@@ -1109,22 +1033,4 @@
 stage image products along with the \ippstage{skycal} catalog to the
 \ippprog{psphotFullForce} program.
-
-%% In this program, the positions of sources are loaded from the input
-%% catalog.  PSF stars are pre-identified from the stack image and a PSF
-%% model generated for each \ippstage{warp} image based on those stars,
-%% using the same stars for all warps to the extent possible (PSF stars
-%% which are excessively masked on a particular image are not used to
-%% model the PSF).  The PSF model is fitted to all of the known source
-%% positions in the warp images.  Aperture magnitudes, Kron magnitudes,
-%% and moments are also measured at this stage for each warp.  Note that
-%% the flux measurement for a faint, but significant, source from the
-%% stack image may be at a low significance (less than the $5\sigma$
-%% criterion used when the photometry is not run in this forced mode) in
-%% any individual warp image; the flux may even be negative for specific
-%% warps.  When combined together, these low-significance measurements
-%% will result in a signficant measurement as the signal-to-noise
-%% increases by the square root of the number of measurements.  The
-%% individual warp measurements are combined together to generate
-%% averages values within DVO.
 
 The convolved galaxy models are also re-measured on the
@@ -1180,15 +1086,15 @@
 images, from a \ippstage{warp} and a \ippstage{stack} of some variety,
 or from a pair of \ippstage{stack} stage images.  During the PS1
-survey, pairs of exposures, called TTI pairs \citep[see Survey
-  Strategy in][]{chambers2017}, were obtained for each pointing within
-a $\approx$ 1 hour period in the same filter, and to the extent
-possible with the same orientation and boresite position.  The
-standard PS1 nightly processing generated difference images from the
-resulting pairs of \ippstage{warp} images.  The nightly processing
-generated \ippstage{stack} images for the Medium Deep fields, and
-these were combined with a template reference \ippstage{stack} image
-to generate ``stack-stack diffs'' each night they were observed.  For
-the PV3 $3\pi$ processing, the entire collection of \ippstage{warp}
-stage images for the survey were combined with images generated by the
+survey, pairs of exposures, called TTI pairs (see Survey Strategy in
+Paper I), were obtained for each pointing within a $\approx$ 1 hour
+period in the same filter, and to the extent possible with the same
+orientation and boresite position.  The standard PS1 nightly
+processing generated difference images from the resulting pairs of
+\ippstage{warp} images.  The nightly processing generated
+\ippstage{stack} images for the Medium Deep fields, and these were
+combined with a template reference \ippstage{stack} image to generate
+``stack-stack diffs'' each night they were observed.  For the PV3
+$3\pi$ processing, the entire collection of \ippstage{warp} stage
+images for the survey were combined with images generated by the
 \ippstage{stack} processing to generate ``warp-stack diffs'', for
 eventual public released.
@@ -1221,5 +1127,5 @@
 (flux in the minuend is higher than the subtrahend) or as a negative
 source (flux in the subtrahend is higher).  The algorithm used for PSF
-matching is described in \citet{waters2017}.  Upon completion of these
+matching is described in Paper III.  Upon completion of these
 jobs, statistics about the processing are written to an entry in the
 \ippdbtable{diffSkyfile} table.  An \ippmisc{advance} checks for the
@@ -1256,8 +1162,4 @@
 Table~\ref{tab:DVO_schema} lists the full collection of database
 tables used by DVO.
-
-%Figure~\ref{fig:DVO_schema}
-%illustrates the schematic relationship between these types of
-%measurements.
 
 In the most basic implementation, a collection of measurements for
@@ -1274,26 +1176,4 @@
 measurements and a many-to-one relationship between the measurements
 and the derived astronomical objects.
-
-% 
-%% These tables fall into one of several classes:
-%% those which store information about the average properties of
-%% astronomical objects; those which store information about individual
-%% measurements; those which store information about the images; those
-%% which store supporting information (metadata).
-
-%% DVO includes two major classes of database tables: those containing
-%% information about astronomical objects in the sky and those containing
-%% other supporting information.  The object-related tables are
-%% partitioned on the basis of position in the sky: objects within a
-%% region bounded by lines of constant RA,DEC are contained in a specific
-%% file.  The boundaries and the associated partition names are stored in
-%% one of the supporting tables, \ippdbtable{SkyTable}.  This table
-%% contains the definitions of the boundaries for each sky region
-%% (\ippdbcolumn{R_MIN}, \ippdbcolumn{R_MAX}, \ippdbcolumn{D_MIN},
-%% \ippdbcolumn{D_MAX}), the name of the sky region, an ID
-%% (\ippdbcolumn{INDEX}, equal to the sequence number of the region in
-%% the table), and index entries to enable navigation within the table.
-%% The regions are defined in a hierarchical sense, with a series of
-%% levels each containing a finer mesh of regions covering the sky.
 
 \subsubsection{DVO Schema}
@@ -1426,17 +1306,5 @@
 magnitude.  While these photometric distance modulus measurements are
 not extremely precise, they provide a constraint on the distance which
-is used in our analysis of the astrometry
-\citep[see][]{magnier2017.calibration}.
-
-%% Similarly to the \ippdbtable{Measure} table, the fields
-%% \ippdbcolumn{objID}, \ippdbcolumn{catID}, and \ippdbcolumn{averef}
-%% define links from the \ippdbtable{Lensing} table to the
-%% \ippdbtable{Average} table.  In a similar fashion, the fields
-%% \ippdbtable{Average}.\ippdbcolumn{lensingOffset} and
-%% \ippdbtable{Average}.\ippdbcolumn{Nlensing} are the index into the
-%% sorted \ippdbtable{Lensing} table entries.  \note{discuss failure of
-%%   the Lensing to Measure indexing}
-
-% \note{Average used above but defined below}
+is used in our analysis of the astrometry (see Paper V).
 
 \paragraph{Object Tables}
@@ -1530,12 +1398,4 @@
 across the different IPP stages.
 
-%% Data from GPC1 (and other cameras processed by the IPP) are loaded
-%% into DVO in units \code{smf} files generated by the \ippstage{camera}
-%% calibration stage (see section \ref{sec:camera} below).  As
-%% described above, these files contain all measurements from a complete
-%% exposure, with measurements from each chip grouped into separate FITS
-%% tables.  When these measurements are loaded into the
-%% \ippdbtable{Measure} and similar tables, 
-
 \paragraph{Other Tables} 
 
@@ -1544,5 +1404,5 @@
 determined by the photometry calibration analysis and the astrometric
 flat-field corrections determined by the astrometry calibration
-analysis \citep[see][]{magnier2017.calibration}.
+analysis (see Paper V).
 
 \subsubsection{Sky Partition}
@@ -1686,6 +1546,6 @@
 allows valid joins between tables to select the different kinds of
 attributes of the same astronomical objects.  This 64-bit integer ID
-is constructed based on the coordinates of the object, as described by
-\cite[][]{flewelling2017}.  In short, the digits of the right
+is constructed based on the coordinates of the object, as described in
+Paper VI.  In short, the digits of the right
 ascension and declination coordinates are used to define a single
 64-bit integer with spatial resolution of roughly 3 milliarcseconds.
@@ -1761,17 +1621,17 @@
 Upon completion of the processing of each stage, the results of the
 photometry analysis are stored in a large number of individual catalog
-files as described in \cite{magnier2017.analysis}.  The data from
-these files are loaded into a DVO database to define the astronomical
-objects and to allow for calibration analysis.  The program which
-loads the data into the DVO database is called \ippprog{addstar}, and
-is associated with the the \ippstage{addstar} processing stage.  The
-measurement catalogs generated by the \ippstage{camera},
-\ippstage{skycal}, \ippstage{fullforce}, and \ippstage{diff} stages
-are loaded into DVOs in this fashion, although not every measurement
-in each catalog are included in the master DVO that is constructed.
-For a particular re-processing version, a single master DVO is
-constructed for the positive image stages (\ippstage{camera},
-\ippstage{skycal}, \ippstage{fullforce}) and a separate one is
-constructed for the difference image analysis stage results.
+files as described in Paper IV.  The data from these files are loaded
+into a DVO database to define the astronomical objects and to allow
+for calibration analysis.  The program which loads the data into the
+DVO database is called \ippprog{addstar}, and is associated with the
+the \ippstage{addstar} processing stage.  The measurement catalogs
+generated by the \ippstage{camera}, \ippstage{skycal},
+\ippstage{fullforce}, and \ippstage{diff} stages are loaded into DVOs
+in this fashion, although not every measurement in each catalog are
+included in the master DVO that is constructed.  For a particular
+re-processing version, a single master DVO is constructed for the
+positive image stages (\ippstage{camera}, \ippstage{skycal},
+\ippstage{fullforce}) and a separate one is constructed for the
+difference image analysis stage results.
 
 The construction of the master DVO is performed in a hierarchical
@@ -1818,6 +1678,6 @@
 Once the master DVO database has been constructed, high-quality
 astrometric and photometric calibrations can be calculated.  The
-details of the calibration analysis are discussed in
-\cite{magnier2017.calibration}.  We present a brief summary here.
+details of the calibration analysis are discussed in Paper V.  We
+present a brief summary here.
 
 Astrometric calibration consists of measuring and correcting
@@ -1832,5 +1692,5 @@
 a function of position in the camera (essentially an astrometric
 flat-field correction), as a function of the brightness of the star
-(the so-called Koppenh\"offer effect, see~\citealt{magnier2017.calibration}), and as
+(the so-called Koppenh\"ofer effect, see~Paper V), and as
 a function of airmass and color (differential chromatic refraction).
 Once the systematic errors have been measured, they are applied back
@@ -1865,6 +1725,4 @@
 the Medium Deep fields.
 
-%%  (listed in Table~\ref{tab:flat-field-seasons}) XXX add this table
-
 After the \"ubercal analysis of the photometric periods is completed,
 the determined zero points, airmass corrections, and flat-field terms
@@ -1884,5 +1742,5 @@
 flat-field correction addresses photometric variations due to spatial
 variations in the PSF due to the optics and low-level effects on the
-chips \citep[see][]{magnier2017.calibration}.  After the systematic corrections
+chips (see Paper V).  After the systematic corrections
 have been determined and applied back to the database, a final
 relative photometry analysis pass is performed.
@@ -1898,5 +1756,5 @@
 database starts once the PS1 photometry and astrometry measurements
 have been calibrated within the DVO system.  The construction takes
-place in several stages, described in detail by \cite{flewelling2017}.
+place in several stages, described in detail in Paper VI.
 We summarize those steps here.
 
@@ -2148,6 +2006,4 @@
 \end{figure}
 
-%\code{ls /tmp} 
-
 \subsubsection{Pantasks scripts: ippTasks}
 
@@ -2194,6 +2050,4 @@
 \ippmisc{DONE}, and removes them from the book, as these represent
 jobs that have finished.
-
-% \note{the manipulation above takes place in the task.exit subscript}
 
 The associated \ippmisc{run} task generates jobs constructed from the
@@ -2342,5 +2196,5 @@
 used for the warp tessellation.  A \ippdbcolumn{projection_cell} is a
 unit of sky defined to be a square four degrees on each side which has
-a single tangent plane projection \citep[][see]{waters2017}.
+a single tangent plane projection (Paper III).
 Once this
 entry is defined, it is populated with all exposures (stored in the
@@ -2420,15 +2274,4 @@
 data to that instance.
 
-% The basic user commands to interact
-% with Nebulous are to 1) create a new storage object and associated
-% instance; 2) add a new instance to an existing storage object; 3)
-% remove (cull) an instance; 4) delete a storage object; and 5) find a
-% file associated with a given storage objects.  Note that these user
-% commands do not affect the files on disk \note{true for cull?}
-% (exception: the create function will create an empty file if one does
-% not exist).  They only change the state of the Nebulous database; it
-% is the responsibility of the user program to read and write data to a
-% file and to create the copies, etc.
-
 For the Nebulous users, the identifier of a storage object is a unique
 string with the form of a UNIX file path: e.g. a/b/c/file.  When a
@@ -2547,14 +2390,12 @@
 Requests to this server may restrict to the latest by time.  Each row
 in the listing includes basic information about the exposure: an
-exposure identifier \citep[e.g., o5432g0123o; see][for
-  details]{chambers2017}, the date and time of the exposure, the
-telescope commanded pointing, the filter and exposure time, and the
-observation comment for that exposure.  The row also provides a link
-to a listing of the chips associated with that exposure.  This listing
-includes a link to the individual chip FITS files as well as an md5
-checksum.  Systems which are allowed access may download the raw chip
-FITS files via http requests to the provided links.
-
-% \note{add a discussion of gpc1 filenames?}
+exposure identifier (e.g., o5432g0123o; see Paper I for details), the
+date and time of the exposure, the telescope commanded pointing, the
+filter and exposure time, and the observation comment for that
+exposure.  The row also provides a link to a listing of the chips
+associated with that exposure.  This listing includes a link to the
+individual chip FITS files as well as an md5 checksum.  Systems which
+are allowed access may download the raw chip FITS files via http
+requests to the provided links.
 
 The IPP also uses datastores to provide access to its own data
@@ -2666,13 +2507,12 @@
 isolation of source objects is included, providing the organization of
 detections that is used in the \ippprog{psphot} photometry analysis
-\citep{magnier2017.analysis}.  The PSF matching required for \ippstage{stack}
-and \ippstage{diff} stage image combinations is as well.  The
-unification of configuration options between config files on disk and
-the options specified on the command line is handled by
-\ippmisc{psModules} functions, as is the construction of data
-structures in memory to represent the astronomical camera based on the
-header information in the input file.  The functions to generate and
-apply the detrend corrections to the data are also provided by this
-library.
+(Paper IV).  The PSF matching required for \ippstage{stack} and
+\ippstage{diff} stage image combinations is as well.  The unification
+of configuration options between config files on disk and the options
+specified on the command line is handled by \ippmisc{psModules}
+functions, as is the construction of data structures in memory to
+represent the astronomical camera based on the header information in
+the input file.  The functions to generate and apply the detrend
+corrections to the data are also provided by this library.
 
 \section{IPP Hardware Systems}
@@ -2688,8 +2528,8 @@
 by the University of Hawaii.  This site was chosen based on the
 original development funding provided by the Air Force Research Labs
-\citep[see][for more details]{chambers2017}.  Once the Air Force
-funding stopped being a significant driver for Pan-STARRS, the cluster was
-physically moved from the MHPCC to a similar nearby computing center
-located at the Maui Research and Technology Center.
+(see Paper I for more details).  Once the Air Force funding stopped
+being a significant driver for Pan-STARRS, the cluster was physically
+moved from the MHPCC to a similar nearby computing center located at
+the Maui Research and Technology Center.
 
 The computing cluster is comprised of three main types of computers,
@@ -2792,21 +2632,4 @@
 \end{table*}
 
-%%\begin{deluxetable}{lcc}
-%%  \tablecolumns{3}
-%%  \tablewidth{0pc}
-%%  \tablecaption{Cost values for remote processing}
-%%  \tablehead{\colhead{IPP Stage}&\colhead{$t_\mathrm{task}$ (s)}&\colhead{$S_\mathrm{task}$}}
-%%  \startdata
-%%  \ippstage{chip} & 150 & 2 \\
-%%  \ippstage{camera} & 1700 & 2 \\
-%%  \ippstage{warp} & 110 & 2 \\
-%%  \ippstage{stack} & 1500 & 6 \\
-%%  \ippstage{staticsky} & 7200 & 6 \\
-%%%  \ippstage{diff} & 300 & 2 \\
-%%  \ippstage{fullforce} & 300 & 2
-%%  \enddata
-%%  \label{tab:SC processing parameters}
-%%\end{deluxetable}
-
 Once the preparation for the job is complete, the input and output
 file lists, the task list, and the job control file are transferred
@@ -2868,4 +2691,6 @@
 994,890 runs processed there.
 
+%% add a discussion of lessons-learned?
+
 \section{Conclusion}
 
@@ -2905,16 +2730,7 @@
 \input{datasystem.bbl}
 
-% \appendix
-
-% Table \ref{tab: database schema} provides a list of a majority of the
-% tables in the GPC1 database schema.  Tables that have been excluded
-% are either no longer used in IPP processing, or are used for rare
-% reductions that were not used for the PV3 data release.  The tables
-% are grouped into stages, with the primary table and any secondary
-% tables for that stage listed together, along with the primary key
-% column that link the tables together.
-
 \end{document}
 
+% this is a 'deluxetable' version of table 1
 \begin{center}
 \begin{deluxetable}{lllll}