Structural Data interpretation
Predicted and measured movement side by side
ETABS construction-stage predictions matched to survey measurements and regenerated as reporting graphs.
- Client context
- Structural engineering team
- Built with
- ETABS, Excel, Python
What changed
The team can regenerate a predicted-versus-measured view for each reporting cycle and send the resulting graphs to builders and clients as a progress update. The source data no longer has to be matched and rebuilt by hand each time.
The problem
ETABS gives you a lot back. On a construction-stage analysis of a large tower, that was gigabytes of results across two models, holding the predicted deflection at every level, for every stage of the build. The team wanted to compare those predictions with the surveyor's measurements as the building went up. Reassembling and matching spreadsheets of that size by hand for every reporting cycle was not practical.
What I built
I aligned the ETABS results with the surveyor’s data so predicted and measured deflections matched by level and construction stage. Then I wrote a set of Python scripts to produce the comparison graphs and tables directly from those sources.
The pieces were simple, but the matching had to be dependable: read both sources, align the stages and levels, then produce a result the team could report from.