All configuration items here are compatible with the interface logic of FastGPT v4.17.0.
What the data for this category looks like
Data sources include design documents, reference standards and environmental monitoring data, calibration software outputs, laboratory information systems, and customer range requirements. Updates occur after each calibration for every individual device. Daily documents cover assembly and commissioning sheets, calibration procedures, original calibration records, error curves, metrology certificates, and software version logs. Fields include tested part number, calibration date, reference standard number, error value, range, and metrology certificate number. Most units use international standard units of measurement.
Constraints for Citation Sources and Traceability
High-volume one-off calibration document generation requires the traceability system to quickly locate the latest calibration record for a single device. Documents contain unique identifiers such as metrology certificate numbers and reference standard numbers, requiring precise matching of the traceability chain to ensure audit validity. Professional metrology fields and units require that associated information is retained during retrieval to prevent distortion of traceability data. Unstructured content such as original calibration records and error curves must be accurately retrieved to avoid missing critical error data that impacts audit results.
Configuration Settings
| Configuration Item | Recommended Range | Rationale |
|---|---|---|
| Similarity Threshold | 0.75–0.85 | Meets precision requirements for matching professional documents such as metrology certificates and calibration records |
quoteMaxToken | 8000–12000 token | Accommodates the total content length of complete calibration records and error curves for a single device |
| Single Retrieval Count | Top 6 results | Covers requirements for multiple associated documents including calibration procedures, metrology certificates, and commissioning sheets |
detail | Full | Retains critical traceability fields from original records such as reference standard numbers and calibration dates |
| Maximum Context Window | 16000–20000 characters | Supports associated data for batch audits of multiple devices |
Three Common Configuration Errors
- Setting
quoteMaxTokento too small a value results in truncated calibration records during retrieval, with incomplete cited content displayed in the interface, making full error curves and metrology certificate numbers unviewable. This occurs because total length requirements for a single device's calibration documents are not accounted for. - Hardcoding a knowledge base ID directly in the prompt returns fixed results during calls, unable to automatically match corresponding calibration data based on the audited tested part number. This occurs because variable binding logic is not used to enable dynamic knowledge base retrieval, triggering configuration errors.
- Not setting a reasonable similarity threshold leads to retrieval of large volumes of irrelevant general calibration procedures, failing to accurately locate dedicated records for the current tested part. This occurs because matching rules are not adjusted for the field characteristics of professional metrology documents.
How to Confirm Proper Configuration
- Input the dedicated part number of a single tested device, and verify if retrieved documents include the calibration record, metrology certificate, and error curve corresponding to that number.
- Review the completeness of cited content to confirm no field truncation or missing information.
- Adjust the similarity threshold to verify whether the precision of retrieval results meets matching requirements for professional documents.
- Test the variable binding logic to confirm that retrieved documents automatically switch to data for the corresponding device when different tested part numbers are input.
The values provided here are common starting points, and should be evaluated against internal samples.