You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other than agentics and mathematics, usually FOSS is better. Ideally OpenEvolve for proof-of-concept work should heavily bias Qwen3-32B or Qwen3-30B-A3B, and only use larger Qwen coder for heavyweight development SomeOddCodeGuy/WilmerAI#26 (reply in thread)
This line of thought makes me think of a few things:
How do we transfer the skills of one extremely unhostable model into open weight industrial models and then to something more consumer-friendly? (yes I am essentially asking for a multi-tiered distillation solution)
Since RouteLLM only interpolates between 2 models, and WilmerAI only routes through task type, what are the possible ways of handling both at the same time, and using more than 2 models per task type? https://github.com/lm-sys/RouteLLM
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Other than agentics and mathematics, usually FOSS is better. Ideally OpenEvolve for proof-of-concept work should heavily bias Qwen3-32B or Qwen3-30B-A3B, and only use larger Qwen coder for heavyweight development SomeOddCodeGuy/WilmerAI#26 (reply in thread)
This line of thought makes me think of a few things:
Beta Was this translation helpful? Give feedback.
All reactions