Program 03 · Bus Load Data
Find the connection ID.
Preserve every original load record.
Two load records may connect at the same location. Look up the ID, fill each row, and verify that names, active load values, and row order stay unchanged.
Fully synthetic data · Illustrates the processing approach
Source: both rows must be preserved
| Load ID | Original name | Active load (MW) |
|---|---|---|
| L-017 | Yunling1 | 30 |
| L-018 | Yunling2 | 45 |
Lookup source: generated 03 Bus Data
03 Bus Data provides the connection IDs required by the output template. Try the full name first. Only when that name is absent may a controlled fallback be used.
Yunling1, Yunling2 → Yunling
Neither full name exists in this example's bus data. The lookup falls back to Yunling while the original names remain unchanged.
| Reference name | Bus ID | Eligibility check |
|---|---|---|
| Yunling | B-202 | Meets matching conditions |
Output: two rows share one connection ID
| Load ID | Original name | Active load (MW) | Connection ID |
|---|---|---|---|
| L-017 | Yunling1 | 30 | B-202Bus data: Yunling |
| L-018 | Yunling2 | 45 | B-202Bus data: Yunling |
Verified: 2 input rows → 2 output rows. Original load IDs, names, values, and order are preserved. No rows are merged and no load values are converted.
Exception: more than one eligible ID
In a separate synthetic scenario, Songyuan has two eligible candidates, B-801 and B-802. This candidate set is independent of the main example. The program leaves the connection ID empty and flags it for review. If a full-name match exists but is ambiguous, it does not bypass the ambiguity by trying a fallback.