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

Error in training Slanet for table recognition #11002

Closed
vani-mcm opened this issue Sep 26, 2023 · 4 comments
Closed

Error in training Slanet for table recognition #11002

vani-mcm opened this issue Sep 26, 2023 · 4 comments
Assignees
Labels
bug Something isn't working stale status/close

Comments

@vani-mcm
Copy link

I am new to paddlepaddle. Pls help me to solve this error.
System environment : ubuntu 20.04
python version : 3.8.18
Installed libraries using requirements.txt file in paddle repo
The error message:

  1. ValueError: could not broadcast input array from shape (8,) into shape (4,)

  2. return self._fmt.find(self.asctime_search) >= 0
    RecursionError: maximum recursion depth exceeded while calling a Python object

  3. SystemError: (Fatal) Blocking queue is killed because the data reader raises an exception.
    [Hint: Expected killed_ != true, but received killed_:1 == true:1.] (at /paddle/paddle/fluid/operators/reader/blocking_queue.h:175)
    If any information is needed, I will provide the necessary information.

@sandy-git-only
Copy link

I got the same problem:
ValueError: could not broadcast input array from shape (8,) into shape (4,)

I have changed the values below:
ver : release/2.6
I used the pretrained model : ch_ppstructure_mobile_v2.0_SLANet

  • box_format: &box_format xyxyxyxy
  • loc_reg_num: &loc_reg_num 8
    However it didnt work.

@weiwuxian1998
Copy link

i find the original box labeling format is [][][][], and the first and the third box is the top left and bottom right cords, so you can set box[0::2] in label_ops.py line 731, and can solve it

@GreatV GreatV added the bug Something isn't working label Jun 19, 2024
Copy link
Contributor

This issue is stale because it has been open for 90 days with no activity.

@github-actions github-actions bot added the stale label Jan 20, 2025
Copy link
Contributor

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 15, 2025
@paddle-bot paddle-bot bot closed this as completed Feb 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale status/close
Projects
None yet
Development

No branches or pull requests

6 participants