You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
In the Pinecone vercel starter project that was the origin of this app, the workflow was:
Make a query to the base model because context is not available
Results were poorly because base model wasn't trained on the topic
Click embed and upsert to perform RAG in the background
Ask the same question
Now you get the correct answer due to context
However, now I'm wondering if it would make more sense to fire the same event that is wired to the Embed and Upsert button when the user changes the select toggle for the topic?
It's also super unclear to newcomers that they must click this button to get the desired behavior differences in chat output.
Expected Behavior
It should be reasonably straightforward for folks without deep experience in embeddings and RAG to use the demo and learn the difference between a RAG and Non-RAG pipeline.
Is this a new bug?
Current Behavior
In the Pinecone vercel starter project that was the origin of this app, the workflow was:
However, now I'm wondering if it would make more sense to fire the same event that is wired to the Embed and Upsert button when the user changes the select toggle for the topic?
It's also super unclear to newcomers that they must click this button to get the desired behavior differences in chat output.
Expected Behavior
It should be reasonably straightforward for folks without deep experience in embeddings and RAG to use the demo and learn the difference between a RAG and Non-RAG pipeline.
Steps To Reproduce
Run the current version or visit production
Relevant log output
No response
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: