huggingface / huggingface/optimum-intel
MiniCPMO MAX_TRANSFORMERS_VERSION
- Dominant language
- Jupyter Notebook
- Stars
- 620
- Forks
- 270
- Avg merge
- 4d 47m
- Merged PRs (30d)
- 25
Description
It's a well-known issue that `openbmb/MiniCPM-o-2_6` only works with transformers versions up to `4.51.3`, hence the `MAX_TRANSFORMERS_VERSION` defined here: https://github.com/huggingface/optimum-intel/blob/a484bc6ee1175bbe8868bb53d2c42ab4c4802aa6/optimum/exporters/openvino/model_configs.py#L2711
In our case we have a patched variant of `openbmb/MiniCPM-o-2_6` which resolves the issues for transformers > `4.51.3`, but are unable to *attempt* the export due to this check.
Is there a way that we can override or disable the version checks? If not, it would be nice to have such a mechanism.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at optimum/exporters/openvino/model_configs.py around line 2711, where MiniCPM-o-2_6 is limited by MAX_TRANSFORMERS_VERSION. Trace how that check is applied during export and determine where an override or disabled check could be exposed. Done means a patched MiniCPM-o-2_6 variant can attempt export despite the default version limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100