Skip to content

feat: upgrade MiniMax default model to M3 - #43

Open
octo-patch wants to merge 2 commits into
Karine-Huang:mainfrom
octo-patch:feature/upgrade-minimax-m3
Open

feat: upgrade MiniMax default model to M3#43
octo-patch wants to merge 2 commits into
Karine-Huang:mainfrom
octo-patch:feature/upgrade-minimax-m3

Conversation

@octo-patch

@octo-patch octo-patch commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

Summary

Upgrade the MiniMax vision evaluator (--provider minimax) to use the latest MiniMax-M3 model by default, while keeping MiniMax-M2.7 and MiniMax-M2.7-highspeed available as alternatives.

Changes

  • Set MiniMax-M3 as the default model for the minimax provider in PROVIDER_CONFIGS
  • Add a models list (MiniMax-M3, MiniMax-M2.7, MiniMax-M2.7-highspeed) with M3 listed first
  • Add a --model flag so users can still select MiniMax-M2.7 or MiniMax-M2.7-highspeed when needed
  • Update unit tests and the README accordingly

Why

MiniMax-M3 is the new flagship multimodal model (512K context window, up to 128K output, image input support), making it a better default than M2.7 for vision-based evaluation. M2.7 and M2.7-highspeed remain available via --model MiniMax-M2.7 / --model MiniMax-M2.7-highspeed for reproducibility and lower-latency use cases.

Testing

  • python -m unittest MLLM_eval.test_gpt4v_eval -> 30 passed

octo-patch and others added 2 commits June 2, 2026 14:20
Set MiniMax-M3 as the default model for the --provider minimax vision
evaluator and add a --model flag so MiniMax-M2.7 remains selectable.
Update unit tests and README accordingly.

Co-Authored-By: Octopus <liyuan851277048@icloud.com>
- Include MiniMax-M2.7-highspeed in the minimax provider's models list,
  alongside the M3 default and MiniMax-M2.7
- Update --model help text and README to mention M2.7-highspeed
- Add unit test covering the M2.7-highspeed entry
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.

1 participant