Fix docs indent

Change-Id: I4cc8bfb1883439cf91322e6383fb5107e31cc7d4
This commit is contained in:
Sergiu Deitsch
2024-12-17 15:46:21 +01:00
parent 32df9c52c3
commit d1c79cbd1c
+12 -15
View File
@@ -114,8 +114,7 @@ Solving
Termination: NO_CONVERGENCE (Maximum number of iterations reached.)
Let us focus on run-time performance. The relevant lines to look at
are
Let us focus on run-time performance. The relevant lines to look at are
.. code-block:: bash
@@ -132,23 +131,22 @@ Solving
Total 1.220
Which tell us that of the total 1.2 seconds, about .3 seconds was
spent in the linear solver and the rest was mostly spent in
preprocessing and jacobian evaluation.
Which tell us that of the total 1.2 seconds, about .3 seconds was spent in
the linear solver and the rest was mostly spent in preprocessing and jacobian
evaluation.
The preprocessing seems particularly expensive. Looking back at the
report, we observe
The preprocessing seems particularly expensive. Looking back at the report,
we observe
.. code-block:: bash
Linear solver ordering AUTOMATIC 22106, 16
Which indicates that we are using automatic ordering for the
``SPARSE_SCHUR`` solver. This can be expensive at times. A straight
forward way to deal with this is to give the ordering manually. For
``bundle_adjuster`` this can be done by passing the flag
``-ordering=user``. Doing so and looking at the timing block of the
full report gives us
Which indicates that we are using automatic ordering for the ``SPARSE_SCHUR``
solver. This can be expensive at times. A straight forward way to deal with
this is to give the ordering manually. For ``bundle_adjuster`` this can be
done by passing the flag ``-ordering=user``. Doing so and looking at the
timing block of the full report gives us
.. code-block:: bash
@@ -164,5 +162,4 @@ Solving
Total 0.935
The preprocessor time has gone down by more than 5.5x!.
The preprocessor time has gone down by more than 5.5x!