From 8078ec3f5da740b0c1474a40282a9e9cbb049def Mon Sep 17 00:00:00 2001
From: Tiago Freitas Pereira <tiagofrepereira@gmail.com>
Date: Wed, 20 Jun 2018 13:39:42 +0200
Subject: [PATCH] Removed traces of evaluate.py in the documentation
---
doc/more.rst | 2 +-
doc/struct_bio_rec_sys.rst | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/more.rst b/doc/more.rst
index 089da351..952672d9 100644
--- a/doc/more.rst
+++ b/doc/more.rst
@@ -75,7 +75,7 @@ If ``--eval-files`` are specified, the same fusion that is trained on the develo
.. note::
When ``--eval-files`` are specified, they need to be in the same order as the ``--dev-files``, otherwise the result is undefined.
-The resulting ``--fused-dev-file`` and ``--fused-eval-file`` can then be evaluated normally, e.g., using the ``evaluate.py`` script.
+The resulting ``--fused-dev-file`` and ``--fused-eval-file`` can then be evaluated normally, e.g., using the ``bob bio evaluate`` script.
.. _grid-search:
diff --git a/doc/struct_bio_rec_sys.rst b/doc/struct_bio_rec_sys.rst
index 2c81a81a..0867f432 100644
--- a/doc/struct_bio_rec_sys.rst
+++ b/doc/struct_bio_rec_sys.rst
@@ -136,7 +136,7 @@ Once a decision has been made, we can quantify the overall performance of the pa
.. note::
- * The "Data Preprocessing" to "Matching" steps are carried out by ``bob.bio.base``'s ``verify.py`` script. The "Decision Making" step is carried out by ``bob.bio.base``'s ``evaluate.py`` script. These scripts will be discussed in the next sections.
+ * The "Data Preprocessing" to "Matching" steps are carried out by ``bob.bio.base``'s ``verify.py`` script. The "Decision Making" step is carried out by ``bob.bio.base``'s ``bob bio evaluate`` script. These scripts will be discussed in the next sections.
* The communication between any two steps in the recognition framework is file-based, usually using a binary HDF5_ interface, which is implemented, for example, in the :py:class:`bob.io.base.HDF5File` class. One exception is the "Decision Making" step, which uses score file in text format, i.e., to allow to incorporate other systems' results, which are computed outside of ``bob.bio``, but uses the same database and evaluation protocol.
* The output of one step usually serves as the input of the subsequent step(s), as portrayed in Fig. 3 -- Fig. 8.
* ``bob.bio`` ensures that the correct files are always forwarded to the subsequent steps. For example, if you choose to implement a feature projection after the feature extraction stage, as illustrated in Fig. 5, ``bob.bio`` will make sure that the files in the "projected" directory are passed on as the input to the Enrollment stage; otherwise, the "extracted" directory will become the input to the Enrollment stage.
--
GitLab