zhanghang1989 / zhanghang1989/PyTorch-Encoding
Question about training Pascal VOC
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2k
- Forks
- 448
- PR merge metrics
- No merged PRs in 30d
Description
Very great repository. Here i have some questions about the training process of Pascal VOC. When i check the train_aug dataset prepared by the prepare_pascal.py script, i notice that the data split way is different to other widely used method, e.g. deeplab (If the split ways are same, the following content can be ignored). For example, the train split data includes some data from the official val set. And here is my question, have you ever compared the evaluation result of two train_aug split ways (the split ways used in this repository and deeplab: tensorflow/models/research/deeplab) on the Pascal VOC test set, since the latter one is convient for conducting ablation experiments on the val set, while the formal one can only evaluate models by submitting test results to the official website. In addition, if we use the latter split way to conduct our experiments, what's the training protocol: training epochs and learning rates for pascal_aug and pascal_voc data.
Contributor guide
No contributing guide indexed for this repository
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 prepare_pascal.py and compare its train_aug split with the split used by tensorflow/models/research/deeplab. Investigate the requested Pascal VOC evaluation comparison and training epochs and learning rates for pascal_aug and pascal_voc; done means documenting the split differences, results, and applicable training protocol.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch, tensorflow
- Domain
- machine-learning
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100