What the data for this category looks like
Data for power sector yield and market reports comes from official public trading documents released by national and provincial power trading centers. Daily report updates are completed within 12 hours after the day’s trading concludes. Documents use structured Excel or CSV formats, grouped and summarized by region, generation type, and trading batch. Fields include: region code, generation category, trading period, transaction average price (unit: yuan/megawatt-hour), transaction volume (unit: megawatt-hour), unit revenue (unit: yuan/megawatt-hour), weighted average revenue (unit: yuan/megawatt-hour).
What constraints do these data characteristics impose on deployment and upgrade
Three constraints arise from the characteristics of power sector data:
- Data sources are official exclusive platforms. Dedicated access keys must be configured, and interfaces have rate limiting rules. Adjust the interval of scheduled pull tasks to avoid triggering rate limits.
- Data updates are completed after daily trading closes. Configure sync tasks that trigger at a fixed daily time to ensure full daily market report data is obtained.
- Field order and naming for structured documents vary by region. Support custom field mapping rules, and unify unit conversion logic to avoid calculation errors caused by unit mismatches.
How to set configurations
| Configuration Item | Suggested Value | Rationale |
|---|---|---|
UPLOAD_FILE_MAX_SIZE | 1000 MB | Accommodate bulk file sizes of provincial power market daily reports, prevent upload failures |
PARSE_FILE_TIMEOUT_SECONDS | 600 seconds | Power daily reports contain multi-region, multi-category data, extend timeout to avoid parsing interruptions |
FETCH_DATA_CRON | 0 18 * * * | Align with the daily update schedule of power daily reports (released before 17:00 daily), ensuring full daily data is pulled at 18:00 |
API_REQUEST_RATE_LIMIT | 10 requests per minute | Comply with official rate limiting rules of power trading platforms, avoid access blocking |
RECALL_TOP_K | Top 8 entries | Power data is grouped by region and category, recalling top 8 entries covers market information of major trading entities |
SIMILARITY_THRESHOLD | 0.75–0.85 | Filter low-match non-power category data, ensure accuracy of recall results |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material format, data volume and business rules. Specific issues require targeted analysis, and it is recommended to test on your own samples before finalizing.
Three Common Misconfigurations
- Phenomenon: Services deployed in Docker containers cannot pull power trading data, and logs show connection timeout. Cause: The container lacks correct outbound network rule configuration, so it cannot access external power data interfaces.
- Phenomenon: Local development environments can normally parse uploaded power daily report files, but after deploying via a container image, file fields cannot be recognized and no error prompt is displayed. Cause: The deployment image is missing dependent components for structured power document parsing, or the file encoding configuration does not match the local environment.
- Phenomenon: Calling the data pull interface returns the
AxiosError 404status code. Cause: The configured power trading platform API interface address is incorrect, or the configuration was not updated after the interface version was upgraded.
How to confirm successful configuration
- Run a manually triggered data pull task, and verify that the returned structured data fields match the configured mapping rules.
- View the execution logs of the scheduled sync task, and confirm that no rate limiting blocking or timeout errors have occurred.
- Upload a test file in standard power daily report format, and confirm that the parsed results can be used normally for subsequent yield calculation.
- Verify the outbound network permissions of the container, and confirm that it can access the configured power data interface address.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.