RunningAverage#
-
class
ignite.metrics.
RunningAverage
(src=None, alpha=0.98, output_transform=None, epoch_bound=True, device=None)[source]# Compute running average of a metric or the output of process function.
- Parameters
src (Optional[ignite.metrics.metric.Metric]) – input source: an instance of
Metric
or None. The latter corresponds to engine.state.output which holds the output of process function.alpha (float) – running average decay factor, default 0.98
output_transform (Optional[Callable]) – a function to use to transform the output if src is None and corresponds the output of process function. Otherwise it should be None.
epoch_bound (bool) – whether the running average should be reset after each epoch (defaults to True).
device (Optional[Union[str, torch.device]]) – specifies which device updates are accumulated on. Should be None when
src
is an instance ofMetric
, as the running average will use thesrc
’s device. Otherwise, defaults to CPU. Only applicable when the computed value from the metric is a tensor.
Examples:
alpha = 0.98 acc_metric = RunningAverage(Accuracy(output_transform=lambda x: [x[1], x[2]]), alpha=alpha) acc_metric.attach(trainer, 'running_avg_accuracy') avg_output = RunningAverage(output_transform=lambda x: x[0], alpha=alpha) avg_output.attach(trainer, 'running_avg_loss') @trainer.on(Events.ITERATION_COMPLETED) def log_running_avg_metrics(engine): print("running avg accuracy:", engine.state.metrics['running_avg_accuracy']) print("running avg loss:", engine.state.metrics['running_avg_loss'])
Methods
Attaches current metric to provided engine.
Helper method to compute metric’s value and put into the engine.
Computes the metric based on it’s accumulated state.
Detaches current metric from the engine and no metric’s computation is done during the run.
Checks if current metric is attached to provided engine.
Helper method to update metric’s computation.
Resets the metric to it’s initial state.
Helper method to start data gathering for metric’s computation.
Updates the metric’s state using the passed batch output.
-
attach
(engine, name, _usage=<ignite.metrics.metric.EpochWise object>)[source]# Attaches current metric to provided engine. On the end of engine’s run, engine.state.metrics dictionary will contain computed metric’s value under provided name.
- Parameters
engine (ignite.engine.engine.Engine) – the engine to which the metric must be attached
name (str) – the name of the metric to attach
usage – the usage of the metric. Valid string values should be
ignite.metrics.metric.EpochWise.usage_name
(default) orignite.metrics.metric.BatchWise.usage_name
._usage (Union[str, ignite.metrics.metric.MetricUsage]) –
- Return type
Example:
metric = ... metric.attach(engine, "mymetric") assert "mymetric" in engine.run(data).metrics assert metric.is_attached(engine)
Example with usage:
metric = ... metric.attach(engine, "mymetric", usage=BatchWise.usage_name) assert "mymetric" in engine.run(data).metrics assert metric.is_attached(engine, usage=BatchWise.usage_name)
-
completed
(engine, name)# Helper method to compute metric’s value and put into the engine. It is automatically attached to the engine with
attach()
. If metrics’ value is torch tensor, it is explicitly sent to CPU device.- Parameters
engine (ignite.engine.engine.Engine) – the engine to which the metric must be attached
name (str) – the name of the metric used as key in dict engine.state.metrics
- Return type
Changed in version 0.4.3: Added dict in metrics results.
Changed in version 0.4.5: metric’s value is put on CPU if torch tensor.
-
compute
()[source]# Computes the metric based on it’s accumulated state.
By default, this is called at the end of each epoch.
- Returns
- the actual quantity of interest. However, if a
Mapping
is returned, it will be (shallow) flattened into engine.state.metrics whencompleted()
is called. - Return type
Any
- Raises
NotComputableError – raised when the metric cannot be computed.
-
detach
(engine, usage=<ignite.metrics.metric.EpochWise object>)# Detaches current metric from the engine and no metric’s computation is done during the run. This method in conjunction with
attach()
can be useful if several metrics need to be computed with different periods. For example, one metric is computed every training epoch and another metric (e.g. more expensive one) is done every n-th training epoch.- Parameters
engine (ignite.engine.engine.Engine) – the engine from which the metric must be detached
usage (Union[str, ignite.metrics.metric.MetricUsage]) – the usage of the metric. Valid string values should be ‘epoch_wise’ (default) or ‘batch_wise’.
- Return type
Example:
metric = ... engine = ... metric.detach(engine) assert "mymetric" not in engine.run(data).metrics assert not metric.is_attached(engine)
Example with usage:
metric = ... engine = ... metric.detach(engine, usage="batch_wise") assert "mymetric" not in engine.run(data).metrics assert not metric.is_attached(engine, usage="batch_wise")
-
is_attached
(engine, usage=<ignite.metrics.metric.EpochWise object>)# Checks if current metric is attached to provided engine. If attached, metric’s computed value is written to engine.state.metrics dictionary.
- Parameters
engine (ignite.engine.engine.Engine) – the engine checked from which the metric should be attached
usage (Union[str, ignite.metrics.metric.MetricUsage]) – the usage of the metric. Valid string values should be ‘epoch_wise’ (default) or ‘batch_wise’.
- Return type
-
iteration_completed
(engine)# Helper method to update metric’s computation. It is automatically attached to the engine with
attach()
.Note
engine.state.output
is used to compute metric values. The majority of implemented metrics accepts the following formats forengine.state.output
:(y_pred, y)
or{'y_pred': y_pred, 'y': y}
.y_pred
andy
can be torch tensors or list of tensors/numbers if applicable.- Parameters
engine (ignite.engine.engine.Engine) – the engine to which the metric must be attached
- Return type
Changed in version 0.4.5:
y_pred
andy
can be torch tensors or list of tensors/numbers
-
reset
()[source]# Resets the metric to it’s initial state.
By default, this is called at the start of each epoch.
- Return type
-
started
(engine)# Helper method to start data gathering for metric’s computation. It is automatically attached to the engine with
attach()
.- Parameters
engine (ignite.engine.engine.Engine) – the engine to which the metric must be attached
- Return type