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

Is the dataset publicly available? #9

Open
JasonKitty opened this issue Aug 23, 2024 · 8 comments
Open

Is the dataset publicly available? #9

JasonKitty opened this issue Aug 23, 2024 · 8 comments

Comments

@JasonKitty
Copy link

I can only find DocGenome dataset, is table recognition trained on this dataset?

Thank you!

@PrinceVictor
Copy link
Contributor

Yes. Our model is trained on the DocGenome dataset. Specifically, we extracted the table data from DocGenome to fine-tune our model.

Thank you for your interest in our work!
Let me know if you have any further questions.

@JasonKitty
Copy link
Author

JasonKitty commented Aug 23, 2024

Yes. Our model is trained on the DocGenome dataset. Specifically, we extracted the table data from DocGenome to fine-tune our model.

Thank you for your interest in our work! Let me know if you have any further questions.

Thank you for your reply! I have two more questions.

  1. The article mentions that table recognition and formula recognition both use the same model as Pix2Struct. Are these models trained separately for each task?

  2. For formula recognition, Mineru uses unimernet, which adds length embedding to the decoder. Is there a similar improvement applied in table recognition?

@PrinceVictor
Copy link
Contributor

Thank you for your questions.

  1. Separate models trained for table and formula recognition.
  2. Unlike unimernet, the is no length embedding added to decoder.

@JasonKitty
Copy link
Author

Thank you for your questions.

  1. Separate models trained for table and formula recognition.
  2. Unlike unimernet, the is no length embedding added to decoder.

Thank u! One more question, the paper mentions tokenizer from nougat, is there an update here? Because I find that the two Tokenizers are not the same.

@PrinceVictor
Copy link
Contributor

We currently utilize the tokenizer from Pix2Struct, but we have expanded the vocabulary to support the Chinese language better.

@JasonKitty
Copy link
Author

We currently utilize the tokenizer from Pix2Struct, but we have expanded the vocabulary to support the Chinese language better.

Table recognition is a token-intensive task, and I think using a dedicated tokenizer can streamline expression, improve inference speed and training performance.

@PrinceVictor
Copy link
Contributor

Thank you for your valuable suggestion. We will continue to improve the model for better performance.

@JasonKitty
Copy link
Author

Thank you for your valuable suggestion. We will continue to improve the model for better performance.

Questions Regarding the Data Preparation.

  1. It is mentioned in the article that the training data consists of 500k articles. May I ask how many table image-Latex pairs were used for StructEqTable training?
  2. In table Latex, there are often many cross-references (e.g., \ref{}, \cite{}, \citep{}), and non-unique expressions (e.g., \textbf{} and \bf{}, different formatting controls that produce similar visual effects). Will such noise negatively affect the model's learning?
  3. Was any data cleaning performed on the table Latex?
  4. How were the table images annotated with the corresponding Latex text?
  5. What are the shortcomings of this model?

Looking forward to your reply.
Thank you!

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