Skip to content

Place a reasonable limit on output blob logging #1297

Open
@longjon

Description

During training, Caffe periodically dumps the contents of output blobs, in a one-value-per-line format. This conveniently allows multiple losses or other metrics to be monitored.

A mistake in net specification may cause an internal data blob to be a disconnected top, i.e., an output blob. Caffe will happily dump billions of values to the log in this case, not stopping until disk is full.

(Yes, this happened to me today, so I am making a reminder here to fix it.)

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions