Documentation in markdown for user custom dataset usage
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 10
- Forks
- 2
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 15
Description
if anyone wants to train on his data :
- he puts the excel file into his project
- he goes to dataset_description.py
- he fills the datasetDescription with useful infos, for exemple
class Dataset:
PUBLICATION_DATASET = ExcelDatasetDescriptor(
"IRRADIATION",
"DC_POWER",
"pub/publishable_data.xlsx",
"Sheet1"
)
- If he want to use the dataset he just described, he can now specify it in the config.py file (in the latest commit)
This guide needs to be reviewed, formatted and put in the README.md, maybe add some instructions for other file types
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 with the dataset_description.py example and the config.py usage described in the issue, then review the existing README.md. Document the custom Excel dataset workflow clearly, format the example, and determine whether guidance for other file types can be added. Done means the README contains an accurate, understandable guide for using a custom dataset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100