Changeset 5706 for trunk/doc/pslib/psLibSDRS.tex

Timestamp:

Dec 6, 2005, 8:54:01 AM (21 years ago)

Author:

eugene

Message:

prepare for release

File:

• trunk/doc/pslib/psLibSDRS.tex (modified) (5 diffs)

trunk/doc/pslib/psLibSDRS.tex

@@ -1 @@
-%%% $Id: psLibSDRS.tex,v 1.360 2005-11-30 01:21:39 price Exp $
+%%% $Id: psLibSDRS.tex,v 1.361 2005-12-06 18:54:01 eugene Exp $
 \documentclass[panstarrs,spec]{panstarrs}
 
@@ -49 +49 @@
 16 & 2005 Sep 13 & final for cycle 8 \\ \hline
 17 & 2005 Oct 18 & draft for cycle 9 \\ \hline
+18 & 2005 Dec 06 & draft for cycle 10 \\ \hline
 \RevisionsEnd
 
@@ -3642 +3643 @@
 lower bounds of the image, the coordinates should saturate on those
 limits.  The output of this function is always a valid region, though
-it may define an area of 0 pixels. \tbd{if Image is a subimage, do
-region coordinates refer to image or subimage?}
-
+it may define an area of 0 pixels.  If \code{image} is a subimage, the
+region coordinates refer to the subimage pixel coordinates.
 
 \begin{prototype}
@@ -5368 +5368 @@
 This function returns the number of pixels in the image region which
 satisfy any of the mask bits.  An error (eg, invalid image, invalid
-region) results in a return value of -1. \tbd{how should region be
-interpreted if mask is a subimage?}
+region) results in a return value of -1.  The \code{region} refers to
+the pixels of the \code{mask}; if \code{mask} is a subimage, the
+region must be defined relative to those subimage pixels.
 
 \begin{prototype}
@@ -7047 +7048 @@
 psProjection *psProjectionAlloc(double R, double D, double Xs, double Ys, psProjectionType type);
 \end{prototype}
+where the units of \code{R} and \code{D} are radians, while \code{Xs} and \code{Ys} are in radians per pixel.
 
 The following functions will project and deproject (respectively)