SCL-Geruest: Stationen (SYSn) als Materialeingang; kurze TRO-Verbindungen nicht mehr verwerfen
scl_skeleton.py brach mit KeyError ab, sobald der TRO-Fluss Stationen (SYSn) enthielt. Stationen bekommen jetzt keine REGION/Instanz, der von einer Station gespeiste TRO ist der Anfang der Reihenfolge, in den Staubereich-Kommentaren sind sie als Station markiert. tro_annotate.py liess Verbindungen unter 2,2 Markergroessen still weg (HundM05 TRO03->TRO04, 500 mm) - sie fehlten dann in tro_extract.py und in der SCL. Kurze Verbindungen werden jetzt Mitte-zu-Mitte gezeichnet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
7b98c8b8d4
commit
e2f1a558a2
@@ -432,6 +432,13 @@ no loading/unloading station: the flow is then a closed loop with no entry, so
|
||||
the order has to be broken somewhere arbitrary. The chosen start and the reason
|
||||
are recorded in the file header.
|
||||
|
||||
**Stations (`SYSn`).** Loading/unloading stations from `tro_flow.py` appear in
|
||||
the JSON as `SYSn` neighbours, not as TROs. They get no REGION and no instance.
|
||||
A TRO fed by a `SYSn` is the start of the order ("Materialeingang ueber SYSn"),
|
||||
so `--start` is no longer needed once the export contains a station. In the
|
||||
jam-area comments they are marked "(Station, kein TRO)", and an exit station
|
||||
shows up as a destination in the per-switch lists.
|
||||
|
||||
## 6. `tro_catalog.py` — TRO type catalog (library, no CLI)
|
||||
|
||||
The single source of truth for everything needed to generate or draw a TRO
|
||||
|
||||
Reference in New Issue
Block a user