Skip to content
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.

Refine models directory #54

Closed
hedaoyuan opened this issue Dec 12, 2017 · 4 comments
Closed

Refine models directory #54

hedaoyuan opened this issue Dec 12, 2017 · 4 comments

Comments

@hedaoyuan
Copy link
Collaborator

The models directory needs to contain two parts. The first part is some standard model configuration files, such as MobileNet, ResNet, etc., that can be used as benchmark test data. The second part contains some well-trained model parameter files, such as the mobilenet ssd pascal model, which can be directly converted to inference model files for deployment to mobile.

@Xreki
Copy link
Collaborator

Xreki commented Dec 12, 2017

I think the structure of the second would be same as https://github.com/PaddlePaddle/models . If we use different data set, there should be a sub-directory.

@hedaoyuan
Copy link
Collaborator Author

I moved mobilenet.py and resnet.py to a configuration directory, and delete the README.md file, which does not look useful at the moment. I think @NHZlX can refine the mobilenet_ssd_pascal directory.

@NHZlX
Copy link
Contributor

NHZlX commented Dec 12, 2017

@Xreki The sub-directory just offer the model config and parameters? or the instructions for training. If add training process, there must be redundant somehow.

@Xreki
Copy link
Collaborator

Xreki commented Dec 12, 2017

If the training process is the same as that in https://github.com/PaddlePaddle/models , we just provide the config and pre-trained parameters, and write a README.md to tell users how to train. Also, we do not need to upload the parameters to github, but give a link to download. We can write a script file to download the parameters (like https://github.com/PaddlePaddle/Mobile/blob/develop/Demo/linux/ssd/models/model_download.sh) and write how to download the parameters in the README.md.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants