Permalink
Browse files

Docs: Many clarifications and fixes for consistency

docs: Many clarifiations and fixes for consistency
  • Loading branch information...
1 parent b1620f6 commit 530c724a6655f9d385bccd61953ee2c27c3baab1 @oleg-alexandrov oleg-alexandrov committed Dec 24, 2013
@@ -34,7 +34,7 @@ \chapter*{Credits}
{\bf Contributing Developer \& Former IRG Terrain Reconstruction Lead}
\begin{itemize}
-\item Dr.\ Laurence Edwards (NASA)
+\item Dr.~Laurence Edwards (NASA)
\end{itemize}
A number of student interns have made significant contributions to
@@ -187,8 +187,8 @@ \subsection{Processing Mars Orbital Camera Imagery}
how to convert the \ac{MOC} images to \ac{ISIS} cubes.
\begin{verbatim}
- ISIS 3> mocproc from= e0201461.imq to= e0201461.cub mapping=no
- ISIS 3> mocproc from= m0100115.imq to= m0100115.cub mapping=no
+ ISIS 3> mocproc from=e0201461.imq to=e0201461.cub mapping=no
+ ISIS 3> mocproc from=m0100115.imq to=m0100115.cub mapping=no
\end{verbatim}
Note that the resulting images are not map-projected. Bundle
@@ -211,8 +211,8 @@ \subsection{Processing Mars Orbital Camera Imagery}
between files.
\begin{verbatim}
- ISIS 3> footprintinit from= e0201461.cub
- ISIS 3> footprintinit from= m0100115.cub
+ ISIS 3> footprintinit from=e0201461.cub
+ ISIS 3> footprintinit from=m0100115.cub
ISIS 3> echo *cub | xargs -n1 echo > cube.lis
ISIS 3> findimageoverlaps from=cube.lis overlaplist=overlap.lis
\end{verbatim}
View
@@ -65,7 +65,7 @@ \chapter{Control Network Toolkit}
location of all detected features.
\begin{verbatim}
- ASP > echo *.tif | xargs -n1 -P 10 ipfind --max 10000
+ > echo *.tif | xargs -n1 -P 10 ipfind --max 10000
\end{verbatim}
Notice the options \emph{\-\-max 10000} used for the \texttt{ipfind}
@@ -77,14 +77,14 @@ \chapter{Control Network Toolkit}
combinations. Here's how:
\begin{verbatim}
- ASP > pairlist_all.py *.tif | xargs -n2 -P 10 ipmatch -r homography
+ > pairlist_all.py *.tif | xargs -n2 -P 10 ipmatch -r homography
\end{verbatim}
Alternatively we could just match between images that happen to be
sequential by name.
\begin{verbatim}
- ASP > pairlist_seq.py *.tif | xargs -n2 -P 10 ipmatch -r homography
+ > pairlist_seq.py *.tif | xargs -n2 -P 10 ipmatch -r homography
\end{verbatim}
Though for large datasets it doesn't seem approriate to compare all
@@ -124,7 +124,7 @@ \chapter{Control Network Toolkit}
matches. We'll go ahead and delete anything 10 and under.
\begin{verbatim}
- ASP > echo *.match | xargs -n1 -P 10 reduce_match --min 10 --max 100
+ > echo *.match | xargs -n1 -P 10 reduce_match --min 10 --max 100
\end{verbatim}
Finally we are ready to collect all pairwise matches into a single
@@ -134,7 +134,7 @@ \chapter{Control Network Toolkit}
network, here's how to perform the last step.
\begin{verbatim}
- ASP > cnet_build *.cub -t isis -o asp_control
+ > cnet_build *.cub -t isis -o asp_control
\end{verbatim}
Let's go ahead and see how the results turned out in qnet!
@@ -163,7 +163,7 @@ \chapter{Control Network Toolkit}
\texttt{cnet\_merge}.
\begin{verbatim}
- ASP > cnet_merge large.cnet small.net -o larger.cnet
+ > cnet_merge large.cnet small.net -o larger.cnet
\end{verbatim}
The above command will create an even larger control network which
@@ -1,4 +1,4 @@
-\chapter{Stereo}
+\chapter{Stereo Correlation}
\label{ch:correlation}
In this chapter we will dive much deeper into understanding the core
View
@@ -721,8 +721,8 @@ \subsubsection*{Commands}
%exhibits the problem
ISIS 3> cubenorm from=N1511700120_1.lev1.cub to=N1511700120_1.norm.cub
ISIS 3> cubenorm from=W1567133629_1.fill.cub to=W1567133629_1.norm.cub
- ISIS 3> spiceinit fr= N1511700120_1.norm.cub
- ISIS 3> spiceinit fr= W1567133629_1.norm.cub
+ ISIS 3> spiceinit from=N1511700120_1.norm.cub
+ ISIS 3> spiceinit from=W1567133629_1.norm.cub
ISIS 3> cam2map from=N1511700120_1.norm.cub to=N1511700120_1.map.cub
ISIS 3> cam2map from=W1567133629_1.norm.cub map=N1511700120_1.map.cub \
ISIS 3> to=W1567133629_1.map.cub matchmap=true
@@ -797,13 +797,14 @@ \section{Digital Globe Imagery}
found with extra-terrestrial missions largely due to the availability
of GPS and high bandwidth comms with the satellite.
-In the next 2 sections we will show how to process unmodified and map-projected variants of World View 1 imagery. This steps will be the
-same for Digital Globe's other satellites. The imagery we are using
-are from the free stereo pair example of Lucknow, India available from
-Digital Globe's website \cite{digital-globe:samples}. These images represent
-a non-ideal problem for us since this is an urban location, but at
-least you should be able to download this imagery yourself and follow
-along.
+In the next 2 sections we will show how to process unmodified and
+map-projected variants of World View 1 imagery. This steps will be the
+same for Digital Globe's other satellites. The imagery we are using are
+from the free stereo pair example of Lucknow, India available from
+Digital Globe's website \cite{digital-globe:samples}. These images
+represent a non-ideal problem for us since this is an urban location,
+but at least you should be able to download this imagery yourself and
+follow along.
\subsection{Processing Raw}
\label{rawdg}
@@ -813,11 +814,7 @@ \subsection{Processing Raw}
\texttt{052783824050\_01\_P001\_PAN}. It has a
lot of files and many of them contain redundant information just
displayed in different formats. We are interested only in the TIF or NTF
-imagery and the similarly named XML file. In this example product from
-Digital Globe, we received our ideal format of a TIFF file. NTF files
-can sometimes use JPEG2000 for the underlining encoding. We supply a
-decoder from OpenJPEG in ASP, unfortunately it is quite slow and might
-mean extremely long preprocessing times.
+imagery and the similarly named XML file.
Further investigation of the files downloaded will show that there are
in fact 4 image files. This is because Digital Globe breaks down a
@@ -826,25 +823,19 @@ \subsection{Processing Raw}
increments for every subframe of the full observation. The tool named
\texttt{dg\_mosaic} can be used to mosaic (and optionally reduce the
resolution of) such a set of sub-observations into a single image file
-and create an appropriate camera file (section \ref{dgmosaic}).
+and create an appropriate camera file
-Since we are ingesting these images raw, it is strongly recommend that
-you use an affine epipolar alignment to reduce the search range. Processing
-with the \texttt{stereo} command is as simple as feeding the imagery
-as the second and third argument. The XML data is fed as the camera
-model argument and thus are used as the fourth and fifth argument. The
-completed command and a rendering in QGIS are shown below.
+\begin{verbatim}
+ > dg_mosaic 12FEB12053305*TIF --output-prefix 12FEB12053305 --reduce-percent 50
+\end{verbatim}
-\begin{figure}[h!]
-\centering
- \includegraphics[width=2.0in]{images/examples/dg/DigitalGlobeContext.png}
- \includegraphics[width=2.0in]{images/examples/dg/DigitalGlobeCloseUp.png}
- \includegraphics[width=2.0in]{images/examples/dg/DigitalGlobeCloseUpDRG.png}
-\caption{Example colorized height map and ortho image output.}
-\label{fig:dg-nomap-example}
-\end{figure}
+and anologously for the second set. See section \ref{dgmosaic} for more
+details. The \texttt{stereo} program can use either the original images
+or the mosacked pair.
-\subsubsection*{Commands}
+Since we are ingesting these images raw, it is strongly recommended that
+you use an affine epipolar alignment to reduce the search range. The
+\texttt{stereo} command and a rendering in QGIS are shown below.
\begin{verbatim}
> stereo -t dg \
@@ -854,6 +845,15 @@ \subsubsection*{Commands}
12FEB12053341-P1BS_R2C1-052783824050_01_P001.XML dg/dg
\end{verbatim}
+\begin{figure}[h!]
+\centering
+ \includegraphics[width=2.0in]{images/examples/dg/DigitalGlobeContext.png}
+ \includegraphics[width=2.0in]{images/examples/dg/DigitalGlobeCloseUp.png}
+ \includegraphics[width=2.0in]{images/examples/dg/DigitalGlobeCloseUpDRG.png}
+\caption{Example colorized height map and ortho image output.}
+\label{fig:dg-nomap-example}
+\end{figure}
+
\subsubsection*{stereo.default}
The stereo.default example file works generally well with all Digital
@@ -879,8 +879,9 @@ \subsection{Processing Map-Projected Imagery}
through the RPC model and then forward through the linear camera model
to calculate the final result.
-The hardest part of this whole process is getting your input low-resolution 3D model. In this example we will use a void filled variant
-of NASA SRTM data. Other choices might be GMTED2010 or USGS's NED
+The hardest part of this whole process is getting the input
+low-resolution 3D model. In this example we will use a variant of NASA
+SRTM data with no holes. Other choices might be GMTED2010 or USGS's NED
data.
It is important to note that ASP expects DEM images to be in
@@ -900,12 +901,11 @@ \subsection{Processing Map-Projected Imagery}
used. That can only be understood by careful reading of your
provider's documents.
-The NASA SRTM square for our example spot in India is N26E080. Below
-are the commands for map-projecting the input and then running
-through stereo. You can use any projection you like as long as it
-preserves detail in the imagery. Note also that we have added a
-seventh parameter to the stereo call where we provide the input low
-resolution DEM.
+The NASA SRTM square for our example spot in India is N26E080. Below are
+the commands for map-projecting the input and then running through
+stereo. You can use any projection you like as long as it preserves
+detail in the imagery. Note also that we have added a seventh parameter
+to the stereo call where we provide the input low-resolution DEM.
\begin{figure}[h!]
\centering
@@ -918,10 +918,10 @@ \subsection{Processing Map-Projected Imagery}
\subsubsection*{Commands}
-The first step is downloading a void-filled SRTM tile to map-project
-on to. In this example we use \texttt{srtm\_53\_07.tif}, a 90 meter
-resolution tile from the CGIAR-CSI modification of the original NASA
-product \cite{cgiar:srtm90m}.
+The first step is downloading a low-resolution DEM file without holes to
+map-project on to. In this example we use \texttt{srtm\_53\_07.tif}, a
+90 meter resolution tile from the CGIAR-CSI modification of the original
+NASA product \cite{cgiar:srtm90m}.
\begin{verbatim}
> mapproject -t rpc --t_srs "+proj=eqc +units=m +datum=WGS84" \
@@ -940,8 +940,11 @@ \subsubsection*{Commands}
dg/dg srtm_53_07.tif
\end{verbatim}
-The complete list of options for \texttt{mapproject} is in section
-\ref{mapproject}.
+If the \texttt{--t\_srs} option is not specified, it will be read from
+the low-resolution input DEM.
+
+The complete list of options for \texttt{mapproject} is described in
+section \ref{mapproject}.
\subsubsection*{stereo.default}
@@ -20,9 +20,9 @@ \section{Binary Installation}
newest version you have available.
\item [{USGS~ISIS}] \hspace*{\fill} \\
-If you are working with planetary missions, you will need to install
+If you are working with non-terrestrial imagery, you will need to install
\ac{ISIS} so that you can perform preprocessing such as radiometric
-calibration and ephemeris attachment. Their installation guide is at
+calibration and ephemeris attachment. The \ac{ISIS} installation guide is at
\url{http://isis.astrogeology.usgs.gov/documents/InstallGuide}. You
must use their binaries as-is; if you need to recompile, you can
follow the \emph{Source Installation} guide for the Stereo Pipeline in
@@ -119,13 +119,13 @@ \subsection{Common Errors}
location for \texttt{ISIS3DATA}.
\begin{verbatim}
-point2mesh E0201461-M0100115-PC.tif E0201461-M0100115-L.tif
+point2mesh stereo-output-PC.tif stereo-output-L.tif
[...]
99% Vertices: [************************************************************] Complete!
> size: 82212 vertices
Drawing Triangle Strips
Attaching Texture Data
-zsh: bus error point2mesh E0201461-M0100115-PC.tif E0201461-M0100115-L.tif
+zsh: bus error point2mesh stereo-output-PC.tif stereo-output-L.tif
\end{verbatim}
The source of this problem is an old version of OpenSceneGraph in
View
@@ -133,9 +133,12 @@ \subsection{NASA Vision Workbench}
\subsection{The USGS Integrated Software for Imagers and Spectrometers}
-This version of the Stereo Pipeline must be installed alongside a copy
-of \ac{USGS} \ac{ISIS} if you wish to process NASA satellite
-imagery. \ac{ISIS} is widely used in the planetary science community
+For processing non-terrestrial NASA satellite imagery, Stereo Pipeline
+must be installed alongside a copy of \ac{USGS} \ac{ISIS}. \ac{ISIS} is
+however not required for processing Digital Globe images of Earth, as
+described in section \ref{quickstartDG}.
+
+\ac{ISIS} is widely used in the planetary science community
for processing raw spacecraft imagery into high level data products of
scientific interest such as map-projected and mosaicked imagery
\cite{2004LPI....35.2039A, 1997LPI....28..387G, ISIS_website}. We
@@ -146,7 +149,7 @@ \subsection{The USGS Integrated Software for Imagers and Spectrometers}
By installing the Stereo Pipeline, you will be adding an advanced
stereo image processing capability that can be used in your existing
-\ac{ISIS} work flow. The Stereo Pipeline supports the \ac{ISIS}
+\ac{ISIS} workflow. The Stereo Pipeline supports the \ac{ISIS}
``cube'' (\texttt{.cub}) file format, and can make use of the \ac{ISIS}
camera models and ancillary information (i.e. SPICE kernels) for
imagers on many \ac{NASA} spacecraft. The use of this single standardized
@@ -155,9 +158,6 @@ \subsection{The USGS Integrated Software for Imagers and Spectrometers}
leveraging \ac{ISIS} camera models, the Stereo Pipeline can process
stereo pairs captured by just about any \ac{NASA} mission.
-As an additional note, the Stereo Pipeline can also process
-Digital Globe images, which does not require ISIS, as described in
-section \ref{quickstartDG}.
%% It might be good to add a section on terminology someday...
%\section{Terminology}
@@ -268,10 +268,9 @@ \section{Warnings to Users of the Ames Stereo Pipeline}
Ames Stereo Pipeline is a {\bf research} product. There may be bugs or
incomplete features. We reserve the ability to change the API and
-command line options of the tools we provide. Some of the documentation
-may be incomplete or out-of-date. Although we hope you will find this
-release helpful, you may use it at your own risk. Please check each
-release's {\bf NEWS} file to see a summary of our recent changes.
+command line options of the tools we provide. Although we hope you will
+find this release helpful, you may use it at your own risk. Please check
+each release's {\bf NEWS} file to see a summary of our recent changes.
While we are confident that the algorithms used by this software are
robust, they have not been systematically tested or rigorously
@@ -23,6 +23,7 @@ \chapter{The {\tt stereo.default} File}
% -------------------------------------------------------------------
\section{Preprocessing}
+\label{stereo-default-preprocessing}
\hrule
\bigskip
View
@@ -11,24 +11,24 @@ \chapter{Tools}
\section{stereo}
\label{stereo}
-The \texttt{stereo} program is the primary tool of the Ames
-Stereo Pipeline. It takes a stereo pair of images that overlap and
-creates an output point cloud image that can be processed into a 3D
-model or DEM using the \texttt{point2mesh} or \texttt{point2dem}
-programs, respectively.
+The \texttt{stereo} program is the primary tool of the Ames Stereo
+Pipeline. It takes a stereo pair of images that overlap and creates an
+output point cloud image that can be processed into a visualizable mesh
+or a DEM using \texttt{point2mesh} (section \ref{point2mesh}) and
+\texttt{point2dem} (section \ref{point2dem}), respectively.
\medskip
-Usage:\\
-\hspace*{2em}\texttt{ISIS 3> stereo [options] \textit{Left\_input\_image Right\_input\_image output\_file\_prefix}}
-
-\medskip
+Usage:
+\begin{verbatim}
+ ISIS 3> stereo [options] left_input_image right_input_image output_file_prefix
+\end{verbatim}
This tool is is primarily designed to process USGS ISIS \texttt{.cub}
files and Digital Globe data. However, Stereo Pipeline
does have the capability to process other types of stereo image pairs
(e.g., image files with a CAHVOR camera model from the NASA MER
-rovers). If you would like to experiment with these features, please
+rovers). If you would like to experiment with these features, please
contact us for more information.
The \texttt{\textit{output\_file\_prefix}} is prepended to all
Oops, something went wrong.

0 comments on commit 530c724

Please sign in to comment.