I've had to go 'code' on it of course, but I'm planning on using the spreadsheet model as the basis for all source data, which I'm hoping will much reduce data skepticism, and allow fairly rapid progression of it's features.
Initial visualisation is in simple 'smearogram' form, but once I have fairly useful mechanisms in place, I'll bolt it into the existing 3D rendering process that I use for the spreadsheet model (And in the process add smearogram output to the latter also)
It's very early days (couple of hours coding), but just 'playing' with partially inelastic collisions has already highlighted quite an interesting factor I'd already considered/assumed, but 'seeing' it is always insightful...
This first image is for fully inelastic collisions, conservation of momentum only, no structural supports. Floors 93 upwards allowed to free-fall. Constant floor thickness, storey height and mass:

http://femr2.ucoz.com/photo/1-0-82
Bolting in partially inelastic collisions, accurate floor heights, per-floor masses and some very beta (read dodgy) energy expenditure mechanics results in this 'thing' :

http://femr2.ucoz.com/photo/1-0-84
Now, whilst the mechanics used are definitely a bit dodgy at the moment, the first point of note is the effect that asynchronous impacts and partially elastic collisions has upon the amount of mass and associated KE involved in impacts at the 'crushing front'.
The amount of mass which could actually be considered part of the 'pile driving mass' is significantly less than that involved in any synchronous impact model.
I need to improve the mechanisms, but I think the effect on 'collapse time' should be considered to be 'profound'.
Suggestions for improvement, motion behaviours, factors and comments very welcome...


