Skip to content
This repository has been archived by the owner on Nov 25, 2020. It is now read-only.

decouple pre-processing prediction and post-processing? #12

Open
Merlin2013 opened this issue Sep 15, 2018 · 0 comments
Open

decouple pre-processing prediction and post-processing? #12

Merlin2013 opened this issue Sep 15, 2018 · 0 comments

Comments

@Merlin2013
Copy link

Just like the common object detection, three phases are included for a whole cycle.
pre-processing: read image, resize or crop (run on cpu)
prediction: load inputs, run on GPU, and get the last conv (run on gpu)
post-processing: do NMS, generate the coordinates, and callback (run on cpu)

how can i decouple the different tasks and imporve throughout ( i think it's more complex here),
is there any reference for this?

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

1 participant