Fix Runware model labels and categorization#203
Merged
Conversation
- Add architecture field to ApiInfo type for raw architecture data from bundle - Update convert script to normalize architecture to modelType (FLUX, SDXL, Imagen, etc.) - Update merge script to preserve architecture and modelType fields - Fix Google Imagen model labels (google:1@1 → 'Imagen 3', etc.) by deriving from descriptions - Update UI getModelType() to use modelType field first before pattern matching - Apply pruning to remove 18 non-working models with 0 calls - Result: 122 models (85 image, 36 video, 1 audio) with 92.6% modelType coverage - Reduces 'Other' category from many models to only 9 models - SDXL models now properly categorized instead of appearing in 'Other' Fixes issue where Google models showed as 'google:1@1' instead of proper names and many models were miscategorized as 'Other' despite having architecture data. Co-Authored-By: Ilya Timonin <timoncool@gmail.com>
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix Runware model labels and categorization
Summary
Fixes two major issues with the Runware model catalog:
google:1@1,google:1@2, etc. instead of proper names like "Imagen 3", "Imagen 3 Fast"Solution:
architecturefield to ApiInfo type to preserve raw architecture data from the Runware bundlemodelTypevalues (e.g., "sdxl" → "SDXL", "flux1d" → "FLUX")getModelType()function to use the populatedmodelTypefield first before falling back to pattern matchingResults:
modelTypepopulatedReview & Testing Checklist for Human
Risk Level: Yellow - Data changes affecting user-facing model names and categorization
Verify Google Imagen labels are correct - Check that the derived names make sense:
Test model categorization in UI - Open the model picker and verify:
google:X@Y)Spot-check model generation - Try generating with a few different model types to ensure nothing broke
Notes
modelTypewill fall back to pattern matching ingetModelType()and may appear in "Other" - this is expectedSession: https://app.devin.ai/sessions/5388bb693ed44ffb8aa537d7f4e7c79d
Requested by: Ilya Timonin (@timoncool)