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
The current QnA generation process relies on different documents than the Azure Indexes. QnAs are generated from the 'crawl' table, but Finesse use finesse-public-guidance index is generated from the 'public-guidance' blob storage. This causes issues with generating scores of 0 in the Finesse Benchmark tool located in the repository finesse-backend. The script needs modification to generate documents from the blob storage instead of the 'louis_crawl' postgreSQL databse.
Tasks:
Modify the script to generate QnAs from the Index blob storage
AFAIK @k-allagbe imported guidance documents from the same crawl table into the blob storage?
@rngadam After the testing I noticed that the 2 null scores (0%) are supposed to be in the bad_questions repository. This means that all the questions returned a score. Moreover, the imported guidance documents are indeed from the same crawl table than the blob storage. This lead me to think that the questions are perfectly generated and we only need more of them and to better classify them (into the good or bad questions repository). So before trying to fix this issue, I propose to generate more questions and test them on Finesse to verify that all documents return a score.
Summary:
The current QnA generation process relies on different documents than the Azure Indexes. QnAs are generated from the 'crawl' table, but Finesse use finesse-public-guidance index is generated from the 'public-guidance' blob storage. This causes issues with generating scores of 0 in the Finesse Benchmark tool located in the repository finesse-backend. The script needs modification to generate documents from the blob storage instead of the 'louis_crawl' postgreSQL databse.
Tasks:
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: