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

Unable to predict table #16

Open
vamsivarada opened this issue Feb 19, 2020 · 1 comment
Open

Unable to predict table #16

vamsivarada opened this issue Feb 19, 2020 · 1 comment

Comments

@vamsivarada
Copy link

I have tried tabulo predict on one of the pdf images from your sample's but it didn't generate anything, Below is the full message of the output.

Found 1 files to predict.
Neither checkpoint not config specified, assuming accurate.
Checkpoint not present locally. Want to download it? [y/N]: y
Downloading checkpoint...
Importing checkpoint... done.
Checkpoint imported successfully.
2020-02-19 17:16:24.245652: I tensorflow/core/platform/cpu_feature_guard.cc:145] This TensorFlow binary is optimized with Intel(R) MKL-DNN to use the following CPU instructions in performance critical operations: AVX AVX2
To enable them in non-MKL-DNN operations, rebuild TensorFlow with the appropriate compiler flags.
2020-02-19 17:16:24.248831: I tensorflow/core/common_runtime/process_util.cc:115] Creating new thread pool with default inter op setting: 8. Tune using inter_op_parallelism_threads for best performance.
Predicting page_8-min.jpg...OMP: Info #212: KMP_AFFINITY: decoding x2APIC ids.
OMP: Info #210: KMP_AFFINITY: Affinity capable, using global cpuid leaf 11 info
OMP: Info #154: KMP_AFFINITY: Initial OS proc set respected: 0-7
OMP: Info #156: KMP_AFFINITY: 8 available OS procs
OMP: Info #157: KMP_AFFINITY: Uniform topology
OMP: Info #179: KMP_AFFINITY: 1 packages x 4 cores/pkg x 2 threads/core (4 total cores)
OMP: Info #214: KMP_AFFINITY: OS proc to physical thread map:
OMP: Info #171: KMP_AFFINITY: OS proc 0 maps to package 0 core 0 thread 0
OMP: Info #171: KMP_AFFINITY: OS proc 1 maps to package 0 core 0 thread 1
OMP: Info #171: KMP_AFFINITY: OS proc 2 maps to package 0 core 1 thread 0
OMP: Info #171: KMP_AFFINITY: OS proc 3 maps to package 0 core 1 thread 1
OMP: Info #171: KMP_AFFINITY: OS proc 4 maps to package 0 core 2 thread 0
OMP: Info #171: KMP_AFFINITY: OS proc 5 maps to package 0 core 2 thread 1
OMP: Info #171: KMP_AFFINITY: OS proc 6 maps to package 0 core 3 thread 0
OMP: Info #171: KMP_AFFINITY: OS proc 7 maps to package 0 core 3 thread 1
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 13264 thread 0 bound to OS proc set 0
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 12156 thread 1 bound to OS proc set 2
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 16980 thread 2 bound to OS proc set 4
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 17288 thread 3 bound to OS proc set 6
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 22584 thread 4 bound to OS proc set 1
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 18916 thread 5 bound to OS proc set 3
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 22892 thread 6 bound to OS proc set 5
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 896 thread 8 bound to OS proc set 0
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 10468 thread 7 bound to OS proc set 7
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 11156 thread 9 bound to OS proc set 2
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 20656 thread 10 bound to OS proc set 4
OMP: Info #250: KMP_AFFINITY: pid 11852 tid 14932 thread 11 bound to OS proc set 6
done.
{"file": "page_8-min.jpg", "objects": []}

@rahulgupta3009
Copy link

Hey, thanks for the library, came across with a similar error. I could detect similar tables from the example image (page_8-min) with 0.70 probability threshold, but when I uploaded some of my samples, it seemed to recognize table only around the low threshold of 0.22, and that too with considerable inaccuracy (obviously).

Just wanted to check in if there are some pre-processing steps that are distinctly required to make sure Tabulo detects tables correctly, or if there are any image related specifications (resolution/dpi, etc)

Also, is there any way to expand the region detected with some margin? or it can be added manually?

TIA!

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