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
We have the base foundation to do querying across tables
Halucinates - Even though the sql query output is empty, it returns a hallucinated response
Issues with classification - a given user message, sometimes, get's classified as query
Sometimes the generated query is wrong - fails during the query execution
Chart generation
Only one table's sample data is hardcoded in the UI side, even we are passing the same table name to the chain, so it can get the schema, so the charts are getting generated fine, but it is only restricted to the same table
For plotting the chart, we need both the data and the chart spec ( generated by llm ) - How do we get the right data for every user query while generating the chart
We don't know if the generated chart is the right one
More like an implementation problem
Usability - not very intuitive
We need the right users for feedback
Hallucinating while having a normal conversation
Final response generation after generating the SQL query and results is slow
Sometimes when asked questions out of scope, in a repetitive manner, the responses look very hard coded , it gives the same response over and over again
Too complex a backend - need to simplify it, too many chains
9. The chatbot seems to be responding to the previous query rather than the current query
The text was updated successfully, but these errors were encountered:
Areas of Improvement
We have the base foundation to do querying across tables
Chart generation
Usability - not very intuitive
We need the right users for feedback
Hallucinating while having a normal conversation
Final response generation after generating the SQL query and results is slow
Sometimes when asked questions out of scope, in a repetitive manner, the responses look very hard coded , it gives the same response over and over again
Too complex a backend - need to simplify it, too many chains
9. The chatbot seems to be responding to the previous query rather than the current queryThe text was updated successfully, but these errors were encountered: