Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FPS of the model #14

Open
abhigoku10 opened this issue Jun 27, 2019 · 7 comments
Open

FPS of the model #14

abhigoku10 opened this issue Jun 27, 2019 · 7 comments
Assignees

Comments

@abhigoku10
Copy link

@ArtyZe thanks for the source code and sharing the model . i have few queries

  1. what is the difference btw your instance segmeter.c and segmenter.c code , since the mode u share gives output for both the function
  2. the time take to predict the on an image is >27 secs which very less , assumption is since its built on c/c++ the fps should be good any ideas on this
  3. Any procedure for training on instance segmentation for custom data , please share

Thanks in advance

@ArtyZe
Copy link
Owner

ArtyZe commented Jun 27, 2019

@abhigoku10
Hello,

  1. In this project I realized the semantic segmentation of detect class(background and target), but instance segmentation is as far not works because I think the code of prjeddie is wrong, I have to fix it. Now I have hard work of face detection, so maybe later I can find a intern to finish it;
  2. Are you testing it in CPU only? If ture, the time is match what we are expecting for. First, I use the image size 1024×512,But actually you can resize and retrain the net with 214*214, but you have to resize the dataset of train; Second, I use the Network of Unet, but it is not necessary, you can change it reference yolo-tiny; Last, in my real project, I used many ways to reduce the computation, like prune, quantization, parallel compute, I have upload part of demo project to my repo:
    https://github.com/ArtyZe/yolo_embedded_acceleration
    After I finish the face detect project, I can update the accelerated segmentation code

@abhigoku10
Copy link
Author

@ArtyZe thanks for the response .

1.sure thanks for this update , i shall look into the instance segmentation .
2.yes i am running it on CPU, as suggest i shall re-train it with different resolution . Can i change the network from u-net, yolo-tiny to other network like yolact for which we have to change the cfg and other c files how feasible would it be .. Thanks for sharing the computation time features i shall look into it

@ArtyZe
Copy link
Owner

ArtyZe commented Jun 27, 2019

@abhigoku10
If you want to change the resolution, what you need to do is only resize train and label image, then change the cfg file.

@abhigoku10
Copy link
Author

@ArtyZe sure i shall do it , but any pointers/ references in changing the architecture that would be helpful

@ArtyZe
Copy link
Owner

ArtyZe commented Jun 27, 2019

@abhigoku10
Are you Chinese? I have written some docs in Chinese. If not, I will update it to readme file of this project this weekend :)

@abhigoku10
Copy link
Author

@ArtyZe i am not chinese ,it would be helpful if you could share the readme based on ur time thanku

@abhigoku10
Copy link
Author

@ArtyZe i want o use your https://github.com/ArtyZe/yolo_embedded_acceleration code , can you share the weights and cfg files to first test the working of the code

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

No branches or pull requests

2 participants