femr2 wrote:I'm cautious to offer 'agreement' to such a large movement of the initiation level, but the model is fully capable of change in the required parameters so I have no problem setting such a run up and rendering the result.
Remember this only applies to the southern end, it's application of the model to a more specific vertical slice in an attempt to match a later ejection in that horizontal region. It would represent the extreme lowest point, but that's precisely the case. IF the model can work under these circumstances (i.e., there really is flat-on-flat inelastic impact as opposed to wedging which conserves momentum but doesn't fully entrain material and isn't necessarily fully inelastic), it can only be expected to work in a 1D slice representative of the conditions at that location. We're only trying to fit the very fastest region. What if the problem were reversed?

It is my opinion that the northernmost, uppermost slice of the building is still above the top of the green region. Can you tell me what tweaks need to be applied to the spreadsheet model to match that? (in case the tweaks should result in arrest, you'll be obligated to provide a mechanism for continuation! haha)
I suggest some additional inspection of the relevant video footage, to which end I've uploaded a 1/3 speed best resolution video of the initial segment of the descent:
I can't dispute that, from this angle, a lot of the top is dropping along your default elevation. Moreover, I haven't examined this issue at the level of detail that others have, likely including yourself. If I had come to some conclusion based on careful research, the tone would be different. Naturally, there's a difference between asserting that the phenomena in question is justified based on an analysis and playing around with uncertainties. As example, if I say that this view most accurately represents the maximum split elevation, it's just an impression. If I'm wrong, oh well.
The mere presence of the ejecta at the level indicated by the lower line indicates this is a more accurate position for an extreme front, especially towards the south. As you note, the video also depicts the progression south to north. In discriminating conditions along the north-south axis, this is worth - on the outside - a second of head start or offset down one floor. It does not necessarily get added to the above but, failing a detailed temporal examination proving otherwise, it would be a prudent assumption. This takes it
nominally down to the 94th floor.
Visible evidence from that video must be reconciled with other knowns. One of which is the bowing extent I mentioned earlier. This is strong, independent corroboration for choosing a value no higher than 94. All was I was asking for was two stories beyond that!
The other known is the crop of one of your frames I posted above. Going back to those calculations, and judging crush front location by exactly the same standard as the five second mark, it's already 5 stories ahead. So, either this gets applied to the initial conditions for the model or the model tries to fit this early, huge discrepancy, and I don't think it would succeed. It would surely be more interesting than trying to fit the discrepancy at over 4 seconds later in the descent. That's why I opted to consider this early 5 floor discrepancy better incorporated as an initial offset. I tried to grab one more story with caternary action, but OK, that's cheating. I'll take it on the basis of uncertainty as a reasonable limit, though.
At least I've made a decent case that floors 93-94 are actually a better choice for a southern slice than 98, in absence of more compelling evidence otherwise. Can we agree on 93-94 as nominal, and 95 to 92 as extremes, for the purposes of this context? If so, then it's 92 we must consider, and so you have.
Shall do.
...
Reduces the 11 storey deficit to ~3.5 storeys.
Not sure why we have a three and half floor difference, but it doesn't seem that important to hash out at this moment. The mass distribution may be quite different and I'm always willing to toss in an off-by-one error times two on my part for anything I hack out in 20 minutes - like the previous code. It more than accounts for the difference.
My preference will be to estimate the actual mass of the hat truss and include it within the model. (It already includes addition for the aircraft (fully loaded) and the antenna)
Has anyone produced an estimation of the hat truss mass ?
I don't know of any, but I'll bet it's out there. Best figures are always best(!) but there has to be caution in applying precision inappropriately. Once again, the issue is matching the conditions of a limited region, so using the best figures for even the slender region - in a static layout - is not necessarily the most accurate picture of what mass distributions may have developed dynamically. One does not have to believe that there was necessarily an ongoing 'piling on' to this specific location to admit that there is uncertainty of distribution. Therefore, in order to account for the most extreme visible occurrence of ejecta, it is necessary to adjust to extrema of reasonable potential distribution, and understand that is the real centerline, and there are tighter plus/minus bands around that. Other, prior observations are employed to set constraints, as done above. And, again, the only reason it has to be done is the objective of matching later knowns also involving specific rather than aggregate location. If the purpose is to match the average behavior, then the opposite extreme would be the NW corner between your red lines, still near that elevation a couple of seconds into it.
In this matter, the known tilt must be considered. Even if one allows for total cap destruction within a few seconds (which I
would argue against), the last verified position and orientation of the upper block puts the diagonal of the rectangle over the south half. It is a different cross section, too, and not necessarily as dense because of core inclusion. This leads to further speculation. If a larger amount of the block remains intact through the five seconds, then shearing and/or wedging could occur as with the WTC2 east side and the model cannot be expected to be applicable as is.
The other choice is that the upper block partially or largely disintegrates over this period and some amount of rubble is contained. The known existence of the spire not only ensures there was some containment on the other side of the floor span, but also strongly suggests that some of the mass, which would stay in the core region in an unadjusted model, has to make its way downward through the floor region. Containment is guesswork, but skewing of the total impinging mass upward from the static distribution is not to be ignored and, if it fits it almost has to be worn.
In light of that, and knowing the hat truss had to add some mass, additional floors have to be added to my simple uniform mass calculation just to expect proper behavior. I did, six may have been too high, but probably not by much, and may have actually been too little. However, this says nothing about your mass distribution, the two are not comparable. Do you have a handy graph of the upper floor masses contained in your sheet?
Regardless of the progress going forward, I can say this has already proven to be a rewarding discussion as far as I'm concerned. I'll cut to the chase now, since I'm not going to defend to death a 1D simple model in an attempt to match reality. If it comes up short, I will fail the model, simple as that. The next step would be the wedge and, while it's not too hard to support existence, it's a devil to refute because WTC2 did it like nobody's business. Arguing with certainty to the contrary, just on the surface of having WTC2 as an example, and without video of the WTC1 S face, is not a tenable position. We are currently examining a much more restrictive model which can only be shown to succeed or not, it wouldn't be fair to refuse the other side of the coin when it comes up.