[Q&A] URML App Support for local "under 2GB memory" LLM #497
Unanswered
slowrunner
asked this question in
Q&A
Replies: 1 comment
-
URML app already supports other LLMs and it appears to work:The processing took just under 4 minutes on my Raspberry Pi 5
The error is consistent with the issue #508 but there is a known issue with qwen2.5:0.5b of "forgetting and halucinating" which was evident the next time I ran the same prompt: I have run larger models on my Mac and remotely accessed them from my robot, which is probably the better approach. The process and configuration on the URML robot would be the same, just changing the OPENAI_BASE_URL environment variable. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What are you trying to do?
I have successfully run qwen2.5:0.5b on my Raspberry Pi 4 GoPiGo3 robot with both type-to and a python API prompt interface using the ollama server. Additionally, I managed to use the Ollama MCP with the qwen2.5:0.5b LLM to add two basic "tools" (get_datetime_server and get_vbatt_server).
The Ollama context limit defaults to 4096, but is configurable. I don't know what a "urml tool" would look like and what the size of the urml validated prompts are to know if the qwen2.5:0.5b will handle the initial query prompt (with NLU->URML info), or if it will handle the urml tool output prompt.txt that will need to be fed back to qwen2.5:0.5b to actuate the robot tools.
Any chance the URML stack will support some "under 2GB memory usage" edge LLM?
"tiny LLM" -> prompt.en.txt-> urml tool -> prompt.txt -> "tiny LLM" -> robot toolsProfile
home
Exact command and inputs
What happened
Validator / CLI version
0.2.0
Beta Was this translation helpful? Give feedback.
All reactions