Auto-Phase Assigner by Z
Strictly sequences the podium first, then cascades that count to independent towers.
Overview
Strictly sequences the podium first, then cascades that count to independent towers.
Inputs (2)
- Guids (Generic): Referenced Rhino geometry IDs.
- Run (Boolean): Wire a Button here to execute.
Outputs (2)
- Log (Text): Execution log
- Info (Text): Method, assumptions, simplifications and references.
Method, assumptions and simplifications
The same notes appear in the component's Info output.
Method
- When Run is True, each referenced Rhino object is read with its User Text keys BuildingID (default Building_01), TowerID (default Main) and Type; objects with Type = core are skipped.
- Blocks are grouped by BuildingID. A block whose TowerID contains podium (any case) is a podium block; the others are grouped by TowerID.
- Podium blocks of a building are sorted by the lowest Z of their bounding box and numbered 0, 1, 2...
- Each tower's blocks are sorted by lowest Z and numbered from the last podium phase + 1 upwards. All towers of a building start from the same number, so towers rise in parallel.
- The number is written to the object's Phase User Text; the run is recorded as one Rhino undo step (Auto-Phase Assigner), so Undo restores the previous Phase values. The Log lists every assignment.
Assumptions
- Each object is one block (one stacking step) and its bounding-box bottom is its level.
- Podium blocks are recognised only by the word podium in TowerID.
Simplifications and limits
- Blocks at the same Z in one group get consecutive phases in input order, not the same phase.
- All podium blocks of a building form one sequence, whatever their TowerID, so separate podiums are not phased independently.
- Phase is a simple vertical sequence; no construction logic, areas or dates.
Workflow
- Referenced massing blocks with User Text -> Guids; Button -> Run.
- Then BIM Attribute Serializer reads the Phase key to stack blocks.