-
Notifications
You must be signed in to change notification settings - Fork 29
Rethink the "splits / mode" behaviour #41
Copy link
Copy link
Open
Description
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels