Skip to content
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

Detail backend (api) for qa on text files #6

Closed
3 tasks done
mt7180 opened this issue Sep 20, 2023 · 3 comments · Fixed by #14
Closed
3 tasks done

Detail backend (api) for qa on text files #6

mt7180 opened this issue Sep 20, 2023 · 3 comments · Fixed by #14

Comments

@mt7180
Copy link
Owner

mt7180 commented Sep 20, 2023

  • write TextDocument class to load text files and convert them into Llama-nodes
  • write Custom ChatEngine class to use and customize VectorindexRetriever, load document nodes into it
  • test main functionality in script with if name == "main"
@Zaubeerer Zaubeerer linked a pull request Sep 27, 2023 that will close this issue
@mt7180
Copy link
Owner Author

mt7180 commented Sep 27, 2023

Implemented code for the Document and ChatEngine classes in script.py, functionality is tested in if _name_ == "_main_"

@mt7180
Copy link
Owner Author

mt7180 commented Sep 28, 2023

I implemented LlamaIndex and created a CondensedQuestionChatEngine in combination with a RetrieverQueryEngine, which efficiently retrieve relevant context from a knowledge base when given a query. The RetrieverQueryEngine is based on a VectorIndecRetriever to retrieve the relevant nodes of a VectorIndex. The nodes are parsed with marvin ai_model as metadataExtractor, the metadata is used by the retriever to find the relevant nodes.

In general the Concepts "Decoupling Chunks Used for Retrieval" and "Chunks Used for Synthesis" are both used here:

  • The CondenseQuestionChatEngine is responsible for synthesis
  • while the RetrieverQueryEngine handles retrieval.
    This allows for more efficient and accurate retrieval of relevant documents before retrieving the specific chunks needed for synthesis.

@Zaubeerer
Copy link
Collaborator

Great! @mt7180, you nailed the issue commenting game :)

Such comments can be made either in the PR or the issue, depending on the company's preferences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants