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

Table is not getting identified completely after training. #162

Open
Nikhilsonawane07 opened this issue Dec 22, 2023 · 1 comment
Open

Comments

@Nikhilsonawane07
Copy link

Nikhilsonawane07 commented Dec 22, 2023

I am trying to fine tune table structure recognition model on 10000 financial tables. I am resuming my training from TATR-v1.1-All weights. I have done annotations for all six classes : table, row, column, column headers, span cell, row headers. I have also performed postprocessing on annotated bboxes to align them properly with table. Using padding of 30 for training table images. When I am running inference pipeline with newly trained weights, tables are not fully getting detected. It is detecting table from line below Table column headers as shown in fig. Rows, columns and other things are getting identified correctly. What could be the issue? How can i improve my model?
@bsmock Can you please help
1_0_fig_tables

@Nikhilsonawane07 Nikhilsonawane07 changed the title Column headers are not getting identified after training. Table is not getting identified completely after training. Dec 26, 2023
@srivatsan-sridhar99
Copy link

Hey @Nikhilsonawane07 ,
I am also trying to fine tune the TSR model (microsoft/table-structure-recognition-v1.1-all) using a proprietary annotated dataset of financial tables with just table row and table column as the classes. The results are extremely bad.

I used the fine tuning notebook mentioned in https://github.com/NielsRogge/Transformers-Tutorials/tree/master/DETR. How exactly did you fine tune the model, using the script in this repo or the ones provided by hugging face?

Also, does the retrained model 'microsoft/table-structure-recognition-v1.1-all' also require table images and bounding boxes to have some sort of padding for fine tuning? is this just applicable for the entire table boundary or even for the cell boundaries? my cell boundaries are tightly cropped around the text.

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