-
Notifications
You must be signed in to change notification settings - Fork 979
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
添加模型的时候能够选择是视觉模型还是文本模型 #312
Comments
Title: When adding a model, you can choose whether it is a visual model or a text model
Function description There are many visual models now, such as Qwen/Qwen2-VL-72B-Instruct and grok-vision-beta. After I added the model and used it, the message sent was still a string and was not recognized as a visual model. It was me. Is the usage wrong? Or is it that the type of a certain model is text or visual, and the boss needs to adapt it one by one? Feature requirement: Can I choose whether the current model is a visual model or text when adding a model? |
我病急乱投医把映射了一下也还是不行。。模型映射是这样写的:!gpt-4-vision-preview>grok-vision-beta 是模型不支持 url 图片读取还是怎么回事呢 |
I was so sick that I went to the doctor and tried mapping, but it still didn't work. . The model mapping is written like this:!gpt-4-vision-preview>grok-vision-beta Is it because the model does not support url image reading or something else is going on? |
这样映射作为解决方案是可以的,如果工作不正常请开启后台调试模式,并提供请求体。 在长期解决来看,企业版提供内置模型表并且可自定义模型类型,后续会同步此架构设计。 |
This mapping can be used as a solution. If it does not work properly, please enable background debugging mode and provide the request body. |
之前因为 watchtower 的的原因(我提过的另一个 issue),所以使用了稳定版 stable 的 docker,它似乎没有 调试模式。。。 |
Previously, because of watchtower (another issue I mentioned), I used the stable version of docker, which seems to have no debug mode. . . |
功能描述
现在有挺多视觉模型,比如 Qwen/Qwen2-VL-72B-Instruct 和 grok-vision-beta,我添加模型并使用后,发送的消息依然是 message 为字符串,并未识别为视觉模型,是我用法不对还是说某个模型的类型是文本还是视觉,需要大佬挨个适配?
feature 需求:可否在添加模型的时候选择当前模型是否为视觉模型还是文本?
相关截图 (如果有)
The text was updated successfully, but these errors were encountered: