table-transformer VS trippy

Saw this last time but never played with it https://github.com/microsoft/table-transformer

Have you tried the SOTA on Table Detection and Extraction with out of the box model weights?

https://huggingface.co/blog/document-ai https://github.com/microsoft/table-transformer https://github.com/google-research/pix2struct https://github.com/PaddlePaddle/PaddleOCR/blob/release/2.6/ppstructure/table/README.md

GPU is at 100% although a bit spiky (dropping occasionally to 50%), I expect that to be normal? I use the same configuration as the authors, num_workers is set to 1 https://github.com/microsoft/table-transformer/blob/main/src/structure_config.json . Data is on a separate SSD, C-drive is a NVMe SSD

[3] https://github.com/fujiapple852/trippy/issues/1104

You are right that showing packet loss for intermediate hops is a frequent source of confusion.

Rather than leave it out, I added a status column which shows different statuses for intermediate hops (blue if the hop responds to less than 100% of probes and brown if it responds to 0%) vs the target hop (amber and red).

Where this breaks down is when dealing with ECMP for UDP & TCP tracing, as a given hop (ttl) may represent the target for a given round of tracing but not for the next. The mistake, imho, is to associate _any_ data with a hop (ttl) rather than the hop in the context of a tracing flow.

That is why Trippy had a number of features aimed at helping with ECMP, such as Paris and Dublin tracing, and the ability to filter tracing by unique flow id. I've covered these quite a bit in the 0.8.0 [0] and 0.9.0 [1] release notes if you want to know more.

[0] https://github.com/fujiapple852/trippy/releases/tag/0.8.0

Tracing flows: breakdown complex UDP/TCP ECMP traces into individual flows (i.e. common network path); render a chart of flows in GraphViz DOT format (example)

u/queiss_ the 0.8.0 release note has a section covering this, but the TL;DR is: