Skip to content

Conversation

dolfim-ibm
Copy link
Contributor

This is a discussion thread on the idea of redesigning the model runtimes and stages.

@dolfim-ibm dolfim-ibm added the documentation Improvements or additions to documentation label Aug 21, 2025
Copy link
Contributor

DCO Check Passed

Thanks @dolfim-ibm, all your commits are properly signed off. 🎉

Copy link

mergify bot commented Aug 21, 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)(?:\(.+\))?(!)?:

Copy link

codecov bot commented Aug 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!


Model runtimes are as generic as possible (but very likely some duplicates might still be there).

1. they operate only on basic objects like PIL images and only expose API for batch predictions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe also PIL + chat-template (!= prompt)

4. model runtime could still have some intenal pre-/post-processing, but it should be limited to model internals, e.g. normalization of images to RGB.

Open questions:
a. should __init__ load the models or we prefer lazy loading?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer a lazy option with a force download option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants