aboutsummaryrefslogtreecommitdiff
path: root/docs/reference-overview.tex
diff options
context:
space:
mode:
authorScott Ettinger <settinger@google.com>2013-09-09 12:54:43 -0700
committerScott Ettinger <settinger@google.com>2013-09-10 00:29:21 +0000
commit399f7d09e0c45af54b77b4ab9508d6f23759b927 (patch)
treeabf3b5ab8259679fb37a8e20308e8cd2a8cd439c /docs/reference-overview.tex
parent1d2624a10e2c559f8ba9ef89eaa30832c0a83a96 (diff)
downloadceres-solver-399f7d09e0c45af54b77b4ab9508d6f23759b927.tar.gz
Bug: 10673139 Bug: 10621282 Change-Id: Ib740a6e0e29049cc203da9f083b0d4f5734a2741
Diffstat (limited to 'docs/reference-overview.tex')
-rw-r--r--docs/reference-overview.tex18
1 files changed, 0 insertions, 18 deletions
diff --git a/docs/reference-overview.tex b/docs/reference-overview.tex
deleted file mode 100644
index 23ab82b..0000000
--- a/docs/reference-overview.tex
+++ /dev/null
@@ -1,18 +0,0 @@
-%!TEX root = ceres-solver.tex
-\chapter{Overview}
-\label{chapter:overview}
-
-Solving problems using Ceres consists of two steps.
-\begin{description}
-\item{\textbf{Modeling}} Constructing an optimization problem by
- specifying its parameters and the terms in the objective function.
-\item{\textbf{Solving}} Configuring and running the solver.
-\end{description}
-
-The two steps are mostly independent of each other. This is by
-design. Modeling the optimization problem should not depend on how the
-solver works. The user should be able model the problem once, and then
-switch between various solver settings and strategies without touching
-the problem.
-
-In the next two chapters we will consider each of these steps in detail.