Skip to content

Conversation

@SteffiVanHees
Copy link

Add batch prediction for layout predictor.

Checklist:

  • Documentation has been updated, if necessary.
  • Examples have been added, if necessary.
  • Tests have been added, if necessary.

@mergify
Copy link

mergify bot commented May 26, 2025

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?(!)?:

@SteffiVanHees SteffiVanHees force-pushed the layoutpredict_batch branch from 2157f13 to aa2e39b Compare May 26, 2025 13:52
Signed-off-by: SteffiVanHees <steffi.vanhees@rebatch.be>
Signed-off-by: SteffiVanHees <steffi.vanhees@rebatch.be>
Signed-off-by: SteffiVanHees <steffi.vanhees@rebatch.be>
@nikos-livathinos
Copy link
Collaborator

@SteffiVanHees thank you for your interest to support batch layout predictions.

How do you plan to use the LayoutPredictor:predict_batch() method? Do you plan to make changes in Docling that can take advantage of the batch processing?

Also, it would be nice to extend the unit tests for the LayoutPredictor and the demo_layout_predictor CLI app.

@mergify
Copy link

mergify bot commented Sep 3, 2025

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?(!)?:

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

Successfully merging this pull request may close these issues.

2 participants