Index: trunk/doc/release.2015/ps1.analysis/analysis.tex
===================================================================
--- trunk/doc/release.2015/ps1.analysis/analysis.tex	(revision 40077)
+++ trunk/doc/release.2015/ps1.analysis/analysis.tex	(revision 40559)
@@ -1,4 +1,4 @@
-\documentclass[iop,floatfix]{emulateapj}
-% \documentclass[10pt,preprint]{aastex}
+% \documentclass[iop,floatfix]{emulateapj}
+\documentclass[10pt,preprint]{aastex}
 % \pdfoutput=1
 
@@ -173,11 +173,11 @@
 described in detail in \cite{2012ApJ...750...99T}.
 
-{\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.}}
+%%{\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{Background}
@@ -1878,5 +1878,5 @@
 \section{Forced Photometry Modes}
 
-\note{too much detail in this section; balance relative to psphot}
+\note{edit this section to remove references to the IPP stages; just refer to the psphot concepts}
 
 Traditionally, projects which use multiple exposures to increase the
@@ -1933,10 +1933,10 @@
 processing is queued for this stage, an entry is added to the
 \ippdbtable{fullForceRun} primary database table linking to the
-specific \ippdbcolumn{skycal\_id} entry that will be used as the
-catalog for the photometry.  The \ippdbcolumn{warp\_id} values for the
+specific \ippdbcolumn{skycal_id} entry that will be used as the
+catalog for the photometry.  The \ippdbcolumn{warp_id} values for the
 input \ippstage{warp} stage images that contributed to the
-\ippstage{stack} associated with that \ippdbcolumn{skycal\_id} are
+\ippstage{stack} associated with that \ippdbcolumn{skycal_id} are
 then added to the \ippdbtable{fullForceInput} table, linked to the
-primary table by the \ippdbcolumn{ff\_id} identifier.  The individual
+primary table by the \ippdbcolumn{ff_id} identifier.  The individual
 jobs for each warp are then run, which passes the \ippstage{warp}
 stage image products along with the \ippstage{skycal} catalog to the
@@ -1948,20 +1948,19 @@
 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).  \note{this doesn't seem correct, as each warp is run
-  independently. EAM: not true!}  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.
+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.
 
 Upon completion of the forced photometry (for point sources as well as
 galaxies, discussed below), an entry is added to the
 \ippdbtable{fullForceResult} table with the processing statistics for
-that combination of \ippdbcolumn{ff\_id} and \ippdbcolumn{warp\_id}.
+that combination of \ippdbcolumn{ff_id} and \ippdbcolumn{warp_id}.
 Once all of the entries in the \ippdbtable{fullForceInput} table have
 finished, a summary operation is run to generate an appropriate
@@ -2032,4 +2031,6 @@
 \section{Difference Image Photometry}
 
+\note{need an intro paragraph or so}
+
 The variance map for a difference image must be generated from the two
 images used to construct the difference.  Otherwise, the low sky level
@@ -2038,8 +2039,6 @@
 For a difference image, both positive and negative sources will be
 present.  The basic peak detection algorithm will only trigger for the
-positive sources.  One solution is to simply apply \code{psphot} to both the
-difference image and its negative value.  \note{do we want to code in
-an automatic switch to get both positive and negative excursions in
-the single pass?}.
+positive sources.  One solution is to simply apply \code{psphot} to
+both the difference image and its negative value.
 
 In the case of a difference image, the PSF model construction stage
@@ -2049,5 +2048,6 @@
 represent the PSF.  Presumably, one or both have been convolved with a
 PSF-matching kernel.  The images which result from the convolution
-should be used to measure the PSF model.  
+should be used to measure the PSF model.  \note{this is what we
+  actually do, so remove hypothetical wording.}
 
 The source classification scheme defaults to the galaxy models for
@@ -2146,18 +2146,5 @@
 Work still needed:
 
-* Tables
-* refereces for other programs
-
-* authors
-* PSF residual map
 * section 3.5.3 Model applied to detected sources needs to be reviewed
 
-* read for english & phrasing
-* convert XXX
 * background model description (see waters)
-* reduce / remove design goal wording?
-* too many bullets?
-* reduce coding description?
-* put engineering docs (psLib, psModules) on public website 
-
-
