[Training 3.0] Add interlock file to data directories
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 203
- Forks
- 67
- Avg merge
- 20m
- Merged PRs (30d)
- 8
Description
In order to avoid situations where the wrong data directory is used, or when an old data directory is used, we should write an "interlock" file into the data directory that indicates the following information:
- The version of the MLPerf tools used to create the data
- The type of data stored in the data directory
When a data directory is used, the MLPerf tool should check the interlock file to make sure that the versions match up, and that the right type of data is present. If not, an error message should be displayed indicating the problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MLPerf tools that create and consume data directories, then trace where the directory version and data type are known. Define the interlock file contents and validation points; done means mismatched versions or data types produce clear errors instead of using the directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100