Removed outdated line in the documentation following commit
(Issue
@@ -159,7 +159,7 @@ captured output. To interpret control characters like a console this would do:
Metrics API
------------------
+-----------
You might want to measure various values during your experiments, such as
the progress of prediction accuracy over training steps.
@@ -169,8 +169,6 @@ or run must be available in the scope. The ``_run.log_scalar(metric_name, value,
a metric name (e.g. "training.loss"), the measured value and the iteration step in which the value was taken.
If no step is specified, a counter that increments by one automatically is set up for each metric.
-It is important that the value is a Python native type (int, float) and not e.g. a numpy.float64.
-
Step should be an integer describing the position of the value in the series. Steps can be numbered either sequentially
0, 1, 2, 3, ... or they may be given a different meaning, for instance the current iteration round.
The earlier behaviour can be achieved automatically when omitting the step parameter.
@@ -253,7 +251,7 @@ defaults to the filename.
Bookkeeping
-==========
+===========
Finally, Sacred stores some additional bookkeeping information, and some custom
meta information about the runs.
This information is reported to the observers as soon as it is available, and
