This model breaks the gemma-3-{size}-pt naming convention

#18
by Lovre - opened

Every other pretrained (base) model in the Gemma 3 family has a "-pt" suffix, while this one does not. This makes any application using various sizes of these models have to carve out a special case for the 270m base model.

Ideally there would now, so as not to break the applications counting on this being the special case, be an exact copy of this repository uploaded, just under the name google/gemma-3-270m-pt. This would help usability and building on top of this wonderful family of models. Thank you!

Lovre changed discussion title from This model breaks the Gemma3 naming convention to This model breaks the geamm-3-{size}-pt naming convention
Lovre changed discussion title from This model breaks the geamm-3-{size}-pt naming convention to This model breaks the gemma-3-{size}-pt naming convention

جدا اعطيني قصه طويله جدا جدا جدا جدا جدا

اعطيني قصه طويله جدا جدا

Google org

Hi @Lovre ,

Thanks for bringing this up!
Your absolutely correct that the lack of a -pt suffix on the `google/gemma-3-270m' model creates an inconsistency with the rest of the Gemma 3 family. This can indeed complicate development workflows and require special handing in applications designed to work with various model sizes.

I've passed this feedback along to the team for consideration.

Thanks again for the thoughtful suggestions - its exactly the kind of detail that improves the experience or everyone building on top of this!

Sign up or log in to comment