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

Questions About Experience Handling and Search in the Knowledge Base #136

Open
andyyosshi opened this issue Jun 10, 2024 · 2 comments
Open

Comments

@andyyosshi
Copy link

I have some questions regarding Experience.

Currently, for each expert's Experience located in /knowledge_base/, there seem to be some Experiences that include variables within them. For example, "cause_name": "insert_large_data" has a variable like "inserted_tuples_threshold" within its "desc".

  • Are these variables parsed somewhere so that the system is designed to let the expert determine real values?

Additionally, I understand that abnormal_metrics names are used to search for Experiences stored in the Chroma DB. Could you clarify which parts of the Experience are used in the search? Is it the cause_name, desc, steps, or metrics?

Thank you for your assistance.

@zhouxh19
Copy link
Collaborator

Sorry for the delayed reply!

  1. We match experiences using the "metrics" attribute, which is saved as the index ("pg_content") in Chromadb by default.

  2. The actual metric values is appended outside the experience, which are generally not exact caused by approximate matching.

image

@andyyosshi
Copy link
Author

Thank you for the clarification!

To ensure I understand correctly, the "metrics" attribute of an Experience is the primary component used for matching within Chroma DB. However, the actual metric values appended outside the Experience may not be exact due to approximate matching.

Could you also provide some insights on how the variables within the "desc" attribute of an Experience, such as "inserted_tuples_threshold", are handled? Are these variables dynamically evaluated by the system or the expert?

Thank you once again for your assistance.

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

No branches or pull requests

2 participants