Skip to content

Rethink the "splits / mode" behaviour #41

@cdancette

Description

@cdancette

Ideas:

  • have a train and an eval mode, like now
  • Ability to specify multiple splits for each mode. Run the splits sequentially (makes sense for eval, maybe less for train. Option to merge them in common batches, or run batches in alternance ?)
  • Metrics should use the {split} and not the {mode} to save their data ?

Use cases can be train/val/test, or multi source datasets (example for data augmentation with another dataset in train).
Or having multiple eval dataset, with different metrics

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions