9 comments

  • Patrick_Devine 2 hours ago

    This was a pretty heavy lift for us to get out which was why it took a while. In addition to writing new image processing routines, a vision encoder, and doing cross attention, we also ended up re-architecting the way the models get run by the scheduler. We'll have a technical blog post soon about all the stuff that ended up changing.

    • exe34 2 hours ago

      did you feed back into llama.cpp?

      also, can it do grounding like cogvlm?

      either way, great job!

      • Patrick_Devine an hour ago

        It's difficult because we actually ditched a lot of the c++ code with this change and rewrote it in golang. Specifically server.cpp has been excised (which was deprecated by llama.cpp anyway), and the image processing routines are all written in go as well. We also bypassed clip.cpp and wrote our own routines for the image encoder/cross attention (using GGML).

        The hope is to be able to get more multimodal models out soon. I'd like to see if we can get Pixtral and Qwen2.5-vl in relatively soon.

  • o11c 37 minutes ago

    Did they fix multiline editing yet? Any interactive input that wraps across 3+ lines seems to become off-by-one when editing (but fine if you only append?), and this will be only more common with long filenames being added. And triple-quote breaks editing entirely.

    How does this address the security concern of filenames being detected and read when not wanted?

  • JumpCrisscross 19 minutes ago

    What’s the best way to “load” a small dataset into an LLM, locally, an interrogate it?

  • inasring 2 hours ago

    Can it run the quantized models?

  • vasilipupkin an hour ago

    how likely is it to run on a reasonably new windows laptop?

    • ac29 an hour ago

      With 16GB of RAM these vision models will run. How quickly depends on a lot of factors.