What the Data for This Category Looks Like
Data sources include material grade archives, customer technical specification documents, temperature control instrument collection data, furnace temperature uniformity test reports, test results from hardness testers and metallographic equipment, and workshop MES systems. Update frequency is per furnace load and per batch. Daily documents include heat treatment process cards, furnace loading diagrams, furnace temperature curves, hardness and metallographic reports, equipment inspection forms, and exception handling forms. Document fields include heating temperature (unit: ℃), holding duration (unit: hours), furnace temperature fluctuation range, number of parts loaded into the furnace, hardness test values (unit: HV), and other related items. Most documents use formats such as paper scans, Excel spreadsheets, or CSV files exported from industrial control systems.
What Constraints These Characteristics Impose on Multi-Turn Dialogue and Prompt Words
Data sources cover multiple formats including industrial control collection, paper documents, and system-exported files. Multi-turn dialogue must support targeted calls to different types of documents. The high-frequency update per furnace load requires limiting the valid historical range of the context window. This prevents redundant old data from interfering with current review. Document fields include numerical values with clear units such as temperature, duration, and hardness. Prompt words must enforce that parameters referenced in dialogue match the units and field names of the corresponding documents. Associated review of exception handling forms requires multi-turn retrospective access to historical furnace load data. The dialogue flow must support context association based on furnace batch numbers and part batches. Generalized historical record call methods must not be used.
Configuration Settings
This configuration applies to FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Maximum Context | 1200–1800 preceding characters | Matches the total length of core documents for a single furnace load, avoids redundant historical data interfering with current review |
variables | Bind furnace batch number and part grade parameters | Ensures each dialogue call only accesses exclusive document data for the corresponding batch |
chatId | Generate independent session ID per furnace load | Isolates review dialogues for different furnace loads, prevents cross-contamination of context |
messages | Retain the most recent 6 dialogue turns | Matches the standard number of dialogue turns for single furnace load review, avoids excessive historical data occupying context |
| Single Recall Limit | Top 3 entries | Limits the number of documents called each time, focuses on core files for the current furnace load |
| Question Optimization Rule | Enable unit verification mode | Enforces that parameters referenced in dialogue must match the units and format of document fields |
Three Common Misconfigurations
- Symptom: The system prompts "Failed to read document interpretation content placed in system prompt words, no uploaded files detected". Cause: Failed to bind heat treatment-specific documents to the
variablesparameter, or the bound document path does not match the actual storage path. - Symptom: Dialogue records disappear after page refresh, displaying as a new dialogue. Cause: Failed to generate an independent
chatIdper furnace load, or session storage configuration does not enable persistent storage. - Symptom: Temperature parameters referenced in dialogue do not match the actual documents. Cause: Failed to enable unit verification mode, and prompt words do not enforce matching units such as ℃ and hours from document fields.
How to Verify Correct Configuration
- Initiate a test dialogue, enter the furnace batch number for the current load, and check if the dialogue only recalls process cards and furnace temperature curves for the corresponding batch.
- View the
chatIdparameter, confirm that a new session ID is generated each time a new furnace load review is initiated. - Enter a parameter with incorrect units, and check if the dialogue triggers a unit verification prompt.
- Check the fields bound to the
variablesparameter, confirm that they include exclusive identifiers such as furnace batch number and part grade.
The values listed above are common starting points. They should be evaluated against the reader's own samples.