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

Understanding the flow #3

Open
Lakshaysharma048 opened this issue Oct 1, 2018 · 5 comments
Open

Understanding the flow #3

Lakshaysharma048 opened this issue Oct 1, 2018 · 5 comments

Comments

@Lakshaysharma048
Copy link

Hi mvoelk,
I recently saw your code and unable to understand from where to start.

Unable to find main function.

Can you please help.

@mvoelk
Copy link
Owner

mvoelk commented Oct 1, 2018

If you are familliar with Jupyter Notebook, the SSD related notebooks SSD_predict.ipynb, SSD_train.ipynb and SSD_evaluation.ipynb should be a good starting point. I will also update the code in the next few days...

@Lakshaysharma048
Copy link
Author

Hi Mvoelk,

Thank you.
Is there anything that is missing in SSD text detection part?

@mvoelk
Copy link
Owner

mvoelk commented Oct 2, 2018

SSD is an generic object detector. For the text detection part, see TB_*.ipynb, SL_*.ipynb and TBPP_*.ipynb. For more details, please read the README.md, the related papers and the thesis. The current code should run as it is.

@Lakshaysharma048
Copy link
Author

Hi Mvoelk,

I was able to understand the TextBox code but at the prediction time, it is giving the class label as "text". (Text and Background) is what we have set as class labels.

I want to pass the output to CRNN function which in turn will check it's lexicon to give the exact word name back to the textbox code. is there a way to connect both of them.

@mvoelk
Copy link
Owner

mvoelk commented Oct 12, 2018

In SL_end2end_predict.ipynb, the text instances are cropped and passed to CRNN. The CRNN implementation is lexicon free.

@mvoelk mvoelk closed this as completed Nov 7, 2018
@mvoelk mvoelk reopened this May 16, 2019
@mvoelk mvoelk mentioned this issue May 16, 2019
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