Skip to content
This repository was archived by the owner on Nov 17, 2023. It is now read-only.
This repository was archived by the owner on Nov 17, 2023. It is now read-only.

[vote] terminology for training process #407

@pluskid

Description

@pluskid

In the current Python binding, the terminology for some training related terms is a bit inconsistent. Specifically, here we should determine the usage of the term for one mini-batch and one full pass through the data.

Current status is: round and iteration mean the same thing -- full path through the data. epoch means a single mini-batch. This will affect parameter and callback names, like start_round, epoch_callback, etc. We should choose a unified (and standard) terminology here before it's getting too late to change names.

My personal opinion is that epoch, if we ever want to use this name, should mean one full pass through the data. I do not find any "standard" reference for this. But looking around, almost all materials I found epoch means this. Some examples:

Possible vote options (please add more if needed)

  1. epoch for full data pass, iteration for a single minibatch
  2. data_pass for full data pass, iteration for a single minibatch
  3. round for full data pass, iteration for a single minibatch
  4. epoch for full data pass, batch for a single minibatch

Metadata

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