Mlx-community/OLMo-2-0325-32B-Instruct-4bit
simonwillison.net
simonwillison.net
[1] https://www.loeb.com/en/insights/publications/2023/12/richar...
https://www.reuters.com/legal/litigation/ai-companies-lose-b... reports on the ongoing case on the image generation side of the fence.
There are plenty of good counterarguments to this as well, when you consider the effects of automation and scale. I’m definitely interested in seeing how the jurisprudence develops as these cases go through the courts.
But I remain skeptical that without "critical thinking as a condition to write into "conscious" memory" the barrier of "conformism" will ever be broken.
Am I doing something wrong? Everyone seems to say how well models work in producing SVGs but I get shapes in all sorts of the wrong places. SVG documents are quite low level (verses editing them in Inkscape or Illustrator) so its tricky to modify, beyond very simple shapes.
Some of them can do good SVGs for things that make sense, like simple diagrams.
In simon's example whole purpose is to make it draw something that it has not seen before but can easily infer from geometry, spatial arrangement. I think it makes a fun problem.
https://allenai.org/blog/olmo2-32B
The closed and partly-closed models rely on a lot of secret sauce, so it’s also just really impressive to see their results being replicated in the open.
In the paramount tasks is to understand the internals of the "black box", get knowledge, engineer better. Of course having "fully open" projects should help that.
Kudos to Allen AI for their great work on a fully-open LLM!
I was here wondering if there was a specific reason for MLX behind this model, but (thankfully thinking of openness) nothing to do with the original model.
How do mlx quants compare to gguf?
Edit: the thread below says that mlx is faster, but gguf quantisations tend to maintain better text quality.
https://www.reddit.com/r/LocalLLaMA/comments/1gc0t0c/how_doe...
max_rec_size = mx.metal.device_info()["max_recommended_working_set_size"]
RuntimeError: [metal::device_info] Cannot get device info without metal backend
Because it is accompanied with a huge stacktrace, it makes me think this is a genuine bug and I hope Simon will fix it.
My plugin only works on Apple Silicon.