-
Notifications
You must be signed in to change notification settings - Fork 179
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
[Good First Issue]: Verify baichuan2-7b-chat with GenAI text_generation #273
Comments
Hi OpenVino developers, Thanks |
Hello @mengbingrock! Thanks for taking a look, I assigned you. Please let us know if you have any questions. :) |
Hello Developers,
The position_ids indeed in not shown in openvino_model.xml. Thanks |
hi @mengbingrock, thanks for you analysis! Yes, looking to intel.optimum might help to find why position_ids are not displayed in IR. You can but the breakpoing or a pring right before I will also take a look what input are fed to |
Thank you for your reply, @pavel-esir I thought the ir is responsible for this error, and it is generated from convert.py, ref: |
Hi @pavel-esir,
No position_ids is present, missing this parameter in IR. Where should I look at next? Thank your for your guidance. |
@mengbingrock thx for the update. I'm right debugging conversion in optimum to see why position_ids disappeared |
@mengbingrock i finally managed to get IR with In order to do so, here https://github.com/huggingface/optimum-intel/blob/main/optimum/exporters/openvino/model_configs.py#L77 Soon we will open PR for that, but meantime as a workaround you can modify your file locally |
Really appreciate your work on this @pavel-esir ! Next time I'll try to find the root cause myself to save your valuable time. |
Context
This task regards enabling tests for baichuan2-7b-chat. You can find more details under openvino_notebooks LLM chatbot README.md.
Please ask general questions in the main issue at #259
What needs to be done?
Described in the main Discussion issue at: #259
Example Pull Requests
Described in the main Discussion issue at: #259
Resources
Contact points
Described in the main Discussion issue at: #259
Ticket
No response
The text was updated successfully, but these errors were encountered: