marek/MtoRagSystem
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Follow-up-Precision-Fix

Browse Source
This commit is contained in:
team 1
2026-04-26 12:44:44 +02:00
parent cd70460918
commit 76cb2189d5
9 changed files with 1008 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
RETRIEX_FOLLOWUP_PRECISION_FIX_README.md Normal file
View File

@@ -0,0 +1,24 @@
# RetrieX Follow-up Precision Fix
This patch tightens direct numeric follow-up handling without changing retrieval, scoring, shop, vector or database logic.
## Why
The follow-up query `mit welchem indikator wird der wert gemessen` could be treated too weakly as a technical product/value question because only `indikator` was a strong keyword. As a result, the stricter technical follow-up prompt rules were not always applied.
## Changes
- Adds `gemessen` / `measured` as technical prompt keywords.
- Adds explicit prompt rules to answer direct indicator/value follow-ups with the exact mapping first.
- Tells the model not to expand into the full indicator table, measurement principle, applications or advisory notes unless explicitly requested.
- Adds `gemessen` to the regression/effective-config keyword check.
## Expected behavior
Question: `mit welchem indikator wird der wert gemessen` after the 0,02 °dH / Testomat 808 answer.
Expected answer starts like:
`Der Wert 0,02 °dH wird beim Testomat 808 mit Indikatortyp 300 gemessen.`
The full indicator table should only be shown when the user asks for all indicators or detailed device information.