1. benthamitemetric

    benthamitemetric Active Member

    Kostak Studios has now also put a video out that demonstrates very clearly that there is no dynamic analyses being performed in the "simulations" underlying Hulsey's released animations. Specifically, this video shows (via an analysis of pixel movement) that there is no movement within Hulsey's model other than the seemingly scripted movements of the penthouse drop and the subsequent uniform movement of the top 30 floors or so:



    As suspected, there is no actual deformation or failure analysis being performed on the individual elements of the building during the scripted collapse sequences.
     
    Last edited: Sep 9, 2019
  2. Oystein

    Oystein Active Member

    From Hulsey's Sep 03 presentation, I am only quickly dumping two bit of transcript that I have prepared - just so the work doesn't go to complete waste. Both are from the Q&A at the end.
    The first - I initially thought Hulsey had the definition of "live load" entirely wrong, but then I looked it up, and it isn't so bad. Still slightly weird that he thinks that the evacuation of people caused a significant decrease of loads. WTC7 weighed on the order of 100,000 tons[*]. A significant percentage would be at least 5% of that - 5,000 tons, the weight of 67,000 people (at 75 kg a piece) - NIST estimated 4,000 occupants on 9/11 (NCSTAR 1A, page 56). Does he think the movement of people at work in an office building is relevant?
    The second snippet is about the formation or non-formation of the kink in the east part of the north wall at the beginning of global collapse:


    [*] 9 years ago today, coincidentally, I did an estimate of total weight, and of Potential Energy released by WTC7, in my other blog:
    https://oystein-issues.blogspot.com/2010/09/gpe-of-building-wtc7.html
    Short version: I had found earlier that the specific gravity of the twin towers was about 1/6 that of water, and applied the same to WTC; the volume of WTC7 was height x depth x average of north face width and south face width = 186 m x 42.7 m x ((75+100)/2) m = 694,942.5 m^3, and mass then 1/6 tons / m^3 x 694,942.5 m^3 = 116,000 tons.
    PE released works out, conservatively, to 80 GJ.


    Source: https://www.youtube.com/watch?v=TAEHhDCTaBw
     
    Last edited by a moderator: Sep 9, 2019
  3. igoddard

    igoddard Active Member

    To understand what we could expect from Hulsey, here are two examples of what appear to be dynamic models from one of the modeling programs he used, Abaqus FEA:



    This is from Abaqus Explicit, which is in the Abaqus FEA suite.



    So graphics with this level of realistic detail are possible with the software Hulsey used.
     
  4. Steen and Claus

    Steen and Claus New Member


    I've looked at the two simulation views of the penthouse: Something doesn't add up.

    The front view shows the penthouse breaking in the middle, but the side view shows (accurately) the penthouse breaking ca. two thirds in, from the camera.

    We're not talking about perspective here: I've counted the grid lines, and there's an even number of grid lines on each side of the penthouse (front view), but a smaller number of grid lines to the far and a larger number of lines to the near (side view).

    When we look at the front view footage of WTC 7, the penthouse clearly breaks in a third og two-thirds of the length.

    Am I right or do I need more coffee? If I am right, then Hulsey is using different simulations for each view.

    /Claus
     
    • Disagree Disagree x 1
  5. Mick West

    Mick West Administrator Staff Member

    I think we are. The grid spacing is irregular on the right side, and there's a truncated corner on the left. Here I've blanked out all the front panels. Metabunk 2019-09-12 07-09-57.

    And here's a view of the top of the building (from a photo I took in 1998), showing the irregular shape of the penthouse (viewed from the other side)
    Metabunk 2019-09-12 07-13-20.
     
    Last edited: Sep 12, 2019
    • Informative Informative x 1
  6. Oystein

    Oystein Active Member

    Also from Hulsey's Sep 03 presentation, the moment where Hulsey categorically refuses to offer an explanation for the magical disappearance of all columns over 8 stories:


    Source: https://www.youtube.com/watch?v=TAEHhDCTaBw&t=1h8m35s
     
  7. Oystein

    Oystein Active Member

    In the old, closed thread on the Hulsey study, I had written this in post #3 on Jan 14, 2015 - more than 2 months before Hulsey officially started:
    This was a mock suggestion for a very lazy, trivial and non-explanatory simulation approach. It turns out, Hulsey's approach was even simpler, even less realistic: He did not bother to to anything with floor connections. He did not even "cut" columns. No, he made them disappear magically. Sections 4.4 to 4.6 (the three scenarious to trigger global collapse: East core only, East core then west core; East core then west core then entire perimeter) most of the time uses the phrase "simultaneous failure of ... columns over 8 stories" (and variants), but what failure mode does that imply? I think the solution is found in Section 4.4 on page 98 (my bolding):
    Sounds as if he does not break, buckle, cut columns - he simply removes them over 8 stories.

    Compared to my simplistic suggestion in January 2015, Hulsey dumbed his down in the following ways:
    • Ignored floor system failures
    • Did not "cut" columns, he just made them disappear without explanation
    • Did not attempt to replicate the actual sequence of failures (e.g. west core east-to-west progression)
    • Did not attempt to analyse the effects of cutting charges, as he refused to hypothesize any demolition scenario
     
    • Agree Agree x 1
  8. Jeffrey Orling

    Jeffrey Orling Active Member

    Could it be sloppy language? He mean they were rendered structurally invisible... non performing columns???
     
    • Disagree Disagree x 1
  9. Miss VocalCord

    Miss VocalCord Active Member

    No also in the report they talk about 'removed' literally; page 94
     
    • Agree Agree x 2
  10. Oystein

    Oystein Active Member

    How is that functionally different from making them disappear magically?
     
    • Agree Agree x 1
    • Funny Funny x 1
  11. econ41

    econ41 Active Member

    Whilst yours Oysten was a mock suggestion and not a serious predictin - Hulsey has also gone down other paths that were predicted.

    In the same closed thread I referred to the influence of T Szamboti.
    This comment at post #6:
    Then at Post #10:
    ...and since those early remarks I have been more pointed in predicting T Szamboti being the puppet master pulling the strings on Hulsey.

    So the study has a few major areas of failure before we even go to the engineering details. The first three I can think of being:
    1) The impossible "false global negative" claim that he proves "fire could not (or "did not") cause the collapse";
    2) The "fudging" of the "simulations" to force them to look visually similar to the real event;
    3) The wholesale importation of the Szamboti EPH descent mechanism;
     
    • Agree Agree x 1
  12. Steen and Claus

    Steen and Claus New Member

    Why would the grid spacing be irregular on one side?

    If that is true, that totally screws up any visual clues.

    /Claus
     
  13. Jeffrey Orling

    Jeffrey Orling Active Member

    I don't know that Tony is a puppet master as you suggest.... but it seems that the truthers have a huge lack of structural engineers who have done anything in depth whether right or wrong... and kept at it. Gorden Ross I believe dropped out after his claims that the corners were destroyed and the towers then could not stand. Gerry has no technical explanation for the collapse. He likes to nit pick details.... right or wrong. In marches Hulsey with a university engineering department and shows nothing new.... not even showing NIST's blunders and fraud.

    Why hasn't the truth movement put out what they suggest happened to the structure of these buildings with some level of specificity?
     
  14. Mick West

    Mick West Administrator Staff Member

    In a SAP2000 model, the lines should represent structural members. So for accuracy in modeling the collapse they should mirror the actual penthouse. So to verify this it might be visible in photos and should be there in the blueprints.
     
  15. Oystein

    Oystein Active Member

    This shows the "posts" (colunns) of the penthouses:

    NCSTAR 1-9 Fig 2-12 Roof Layout.

    Posts are closer to each other in the western part of its north wall.

    (I count 8 posts in this figure, but more in the SAP2000 animation)
     
  16. Mick West

    Mick West Administrator Staff Member

    I was looking at the drawings for the penthouse, and got sidetracked to floor 13. The framing (girders between columns, and beams between girders and girders or columns).

    I noticed when I overlaid sheet S-8 (attached) with Hulsey's figure 2.63 there was a discrepancy around the stairwells.
    Metabunk 2019-09-13 10-06-38.
    Notice the vertical white line in the middle of each indicated area. That's a beam that goes the full length of the section in Hulsey's model, but is not there in the actual drawings, as there's a stairwell there, which is framed around.

    Look at the area between columns 58,61,59, and 62.
    Metabunk 2019-09-13 10-09-25.

    White lines are Husley, red lines are S-8.

    It then started noticing this elsewhere. Hulsey's figure 2.63, supposed of floor 13, has quite different framing in the core to drawing S-8 (described as "Typical Floor Framing Plan, 8th to 20th & 24th to 45th")z

    Here I've marked missing members in green, and added members in blue.
    Metabunk 2019-09-13 10-30-10.

    Some detail:
    Metabunk 2019-09-13 10-31-02.

    Besides all the changes, notice one in particular that's a bit different. On the right side, there's a beam that has moved
    Metabunk 2019-09-13 10-32-39.
    The Blue one is Hulsey's lone beam, the green one is the S-8 drawing, it's 11 inches over to the left (the West).

    The next beam over is also wrong. It should be inline with the beam south of it, and both beams should be in line with column 24. Instead they are out of line.
    Metabunk 2019-09-13 10-55-01.



    Related, Hulsey's figure 2.59 similar seems to miss most of the framing in that region.
    Metabunk 2019-09-13 10-42-02.


    Hulsey appears to be working of E12-13, which shows the same detail as S-8. He includes E12-13 on page 15, saying:
    "Figure 1.10 shows the framing plan view for Floors 12 and 13. The drawings are difficult to read because of the number of framing members shown on the drawing."
    Metabunk 2019-09-13 10-48-13.


    Here's a HD image of E12-13 https://www.metabunk.org/f/E12-13.jpg

    That's his old ABAQUS model, what about the SAP2000 model? It's a bit hard to tell, as he displays it here with two floors overlaid. However, it does look like it might have proper framing?
    Metabunk 2019-09-13 11-03-34.

    The next two figures clearly show the simplified framing, it's not specified where they are from, but probably ABAQUS.
    Metabunk 2019-09-13 11-06-37.

    (This appears to be a perspective overhead view of two floors, which is a bit odd, that's why things don't line up)
     

    Attached Files:

    • Informative Informative x 2
    • Useful Useful x 2
    • Like Like x 1
  17. Paradigm_shift

    Paradigm_shift New Member

    'Feelings' indicate bias and perhaps is not a relevant observation to state.
    As for the video, I think something interesting is that these broken windows happen at the exact moment the penthouse begins to collapse, suggesting the entire structure underneath the penthouse has already failed - the broken windows indicate some collision on those floors. The penthouse is still completely visible and has only just begun to move as the first windows break. How is this possible?

    I was under the impression that the penthouse collapsing is what caused the progressive collapse of the interior, leading to the exterior collapsing inwards? Even in the video, it seems like the interior columns are all just simultaneously collapsing; you say what we see is a 'progressive' collapse, but what is making these collapses automatically happen where fire was only on 6-8 floors? How is healthy structure supposedly all giving way at the same time in a fire that wasn't a raging inferno and burnt uncontrollably with unevenly distributed fuel (office materials as there was no plane on WTC7)?

    I'm skeptical that fire can cause global damage to 3 buildings in 1 day when there are possibly only 1 or 2 recorded cases ever of a building ever experiencing global structural failure due to random burning of entropic fires with unevenly distributed fuel in a building, and even those burned for far longer, encapsulated more of the building and didn't reach near free fall for any duration of their collapses.
     
    • Disagree Disagree x 2
  18. Paradigm_shift

    Paradigm_shift New Member

    There is no observed jolt in real-life either.. I think you're missing the point. Dr. Hulsey recreated the observed collapse (even if his findings would support NIST it would be exactly the same) so why should there be a jolt? The fact is that the 'lack of jolt' is indicative that Hulsey's model is more accurate, T.Sz would not disapprove. The 'lack of jolt' indicates these columns were already taken out, the floors would all by falling simultaneously, not really touching, therefore, no jolt as they move hegemonically - which is why we see an entire block of building move as one in reality, at nearly free-fall.
     
    • Disagree Disagree x 1
  19. Mick West

    Mick West Administrator Staff Member

    I suspect we actually see that because it's not a real dynamic analysis. Of course, if it was, then removing all the columns magically instantly would have the same initial result. But there's the issue of what happens when the falling part of the building meets the bottom part. This is very different to the chaotic leaning gradual disintegration collapse of the Towers. Under Hulsey's hypothesis for WTC7 the columns would meet at full force because they are all still there. Of course, he can't actually demonstrate what happens, because his analysis is not real.
     
  20. Jeffrey Orling

    Jeffrey Orling Active Member

    It's virtually impossible to remove an entire 2 story length column let alone all of them in the plan. What happens theoretically is of no consequence to any real world scenario.
     
  21. Oystein

    Oystein Active Member

    How do you know this? Can you present evidence for that claim?

    But what we see in real life is irrelevant anyway - we are discussing the behavior of Hulsey's animations, not the real life events.
    As structure collides with structure in those animations, there should be SOME kind of response, but none is apparent.

    No, this is FALSE, he didn't. See my post #67 where I showed that Hulsey mentions only six of many more features of the observed collapse, but then only recreates 3 of the 6 he himself found noteworthy - and each one of the 3 is really forced onto the simulation artificially: All 3 features are input to the model, not result of any hypothesis.,

    Because after about 1 floor height of actual free fall (falling structure runs into no other structure), the falling stucture runs into standing structure - there is no more free fall. This should result in deceleration / a decrease of acceleration - which is called a "jolt" (jolt = sudden change of acceleration)

    Urrrr... accurate as measured against what? Are you sure you aren't conflating T.Sz.'s "No Jolt" findings for WTC1/2 with Hulsey's WTC7 model? Different buildings!

    But in Hulsey's various models they, nor the floors, are not. We are discussing Hulsey's models, and how they fail do model the behaviour of real floors and columns. This is before any consideration whether this also fits the reality of WTC7's collapse.

    But in Hulsey's models, there are floors connected to columns - and these floors crash into other floors. There shouuld be SOME structural/dynamic response - in Hulsey's model. Remember, we are discussion Hulsey's model.
     
    • Like Like x 1
    • Agree Agree x 1
  22. benthamitemetric

    benthamitemetric Active Member

    Given that it now seems clear that Hulsey did not perform the dynamic modeling necessary to support his conclusion re the global collapse, I think it is worth taking a few steps back and looking at the consequences of that failure in context.

    That failure certainly confounds Hulsey's immediate aim (i.e., demonstrating that his conjectured column deletion scenario would result in a collapse similar to what was actually observed), but that ultimately doesn't even really matter in the grand scheme of things. If Hulsey and his graduate students had competently created a true nonlinear dynamic model of the building, then it seems to me that there should be no technical barrier to them creating a demolition-via-structural-element-deletion scenario that closely resembles the collapse that was actually witnessed. If they were very clever, they likely could even come up with fanciful scenarios that don't involve obvious errors (such as requiring the magical unspoken deletion method do work on floors that were involved in fire, as conjectured in the released report). It would just be a matter of trial and error to come up with such "just so" scenarios whereby a collapse with certain visual characteristics could be induced by magically deleting structural elements in a certain sequence; in fact, it should logically be the case that there are infinite such "just-so" scenarios out there in the ether, waiting for Hulsey and co. to stumble upon them.

    Such "just-so" modeling this is what I actually predicted Hulsey would do in the other Metabunk thread here:

    And then here:

    My only real mistake was assuming they would actually be able to competently build the necessary dynamic model to back up their "just-so" scenarios. It seems they could not, but the underlying issue with their methodology remains the same: it proves nothing to recreate the collapse via magical just-so element deletion scenarios. The whole second half of Hulsey's report, flawed as it may be on a technical level, is just a colossal waste of time on a logical level. What Hulsey needed to do was test an evidence-based hypothesis and then see if that hypothesis had better explanatory power than's NIST's. (And even that wouldn't rule out NIST's scenario or other fire-induced collapse scenarios, but it would at least present a plausible alternative to NIST's chosen scenario.) But Hulsey instead failed to correct the many errors we previously identified here on Metabunk with respect to his local model and apparently just barged forward (as I predicted) with a mode of global model analysis that, even if it were properly executed, is devoid of any logical significance.
     
    Last edited: Sep 15, 2019
    • Like Like x 1
  23. Oystein

    Oystein Active Member

    Reminder from the UAF project page:
    Within the next 2 weeks, we should have their data available, which should remove any doubt as to what their models did and didn't do...

    ...IF we have the software and sufficient hardware, and the software skills to use that data! Does anyone here have such capabilities?
     
  24. Mick West

    Mick West Administrator Staff Member

    Although based on previous time estimates, likely towards the end of, or after, that time period. A significant issue is that the public comment period is up to November 1. So the later they release, the less time people will have to check their data. They should make the public comment period be at least six weeks after that data release.

    But yes, that will be interesting. Hopefull it will be structured in a way that it can be easily accessed. They do say:
    Several hundred gigabyes will take a long time to download though. Several days for many people - which really should also be factored into the public comment period. The large size will dissuade some people with bandwidth caps.

    I have the hardware capabilities (a reasonably powerful computer with 64GB of memory and terabytes of space). I don't have ABAQUS or SAP2000. I do have some coding skills, so should be able to munge their data into a variety of visualizations.
     
    • Like Like x 1
  25. Oystein

    Oystein Active Member

    It's tempting to interpret this all as deliberate obstruction.

    I think it could well be important to check and understand how the original software - the versions of ABAQUS and SAP2000 Hulsey used - interprets the data. There may be switches, toggles, parameters embedded in the construction data, or additional to it, that control what the software does or doesn't do.
     
    • Like Like x 1
  26. econ41

    econ41 Active Member

    Not me. But my usual word of caution. We run the risk of being baffled by BS if we go sifting the data before we validate how it is being used. (Or more likely INvalidate. ;) )

    The errors are almost certainly in the assumptions, context framing and the structure of arguments. Such has been consistent experience through out the history of WTC 9/11 debate. And it has been a trick that T Szamboti has relied on whether by deliberate intent or otherwise. I identified the error with a 2007 Szamboti paper in my very first internet post when I said:
    Other examples over the years include the two fatal false premises of Szamboti's "Missing Jolt" and the similar problem with some of Bazant's papers. (Specifically "crush down/crush up). And IIRC every step of the evolution of Szamboti's changing claims about WTC7.

    I'm not saying that there will not be errors which can be revealed by application of data. BUT the significant and fatal flaws of argument will almost certainly be in how the data is used.. not in the numeric details.
     
    • Agree Agree x 2
  27. econ41

    econ41 Active Member

    Yes. That is sort of "mid level". But the need is first to determine if what he is trying to do is valid THEN - IF it is valid - go down one layer and check the switches and other broad parameters. The actual numbers are yet another layer down into detail and probably of little importance because he will have errors at those two higher levels.
     
  28. Oystein

    Oystein Active Member

    Yes, exactly. Certainly the goal ought not be to compare every hook and ornament against shop drawings - we are not Truthers! :p

    The kind of thing I would be looking for is confirmation that the models are SET to behave in ways that have no correspondence to the physics of real steel frame structures. Such as not checking whether beams collide and thus allow them to pass through each other. Or having connections that never break and rather can be stretched dozens of meters, because they are not modeled with a condition or threshold above which they break.
     
    • Agree Agree x 4
  29. Miss VocalCord

    Miss VocalCord Active Member

    While waiting for any data to be released by Hulsey I was looking at his talk where he showed his theory of collapse; at just before 58 minutes in the video on the http://ine.uaf.edu/projects/wtc7/ site which is called:
    Somehow I can't link it here; however the same part can be found on youtube :


    (He claims it is the global collapse of floor 13, where as he later has to admit the east penthouse wasn't collapsed because of this, but that has been pointed out many times before.)

    What I did see in this simulation/view is something different as what can be seen in the same collapse of the separate videos like this one:


    If you look at the same collapse during the presentation of Hulsey you see the penthouse is falling much further down as in the other videos, almost as far as half way down the building around floor 24:
    WTC_EP.
     
    • Informative Informative x 1
  30. Jeffrey Orling

    Jeffrey Orling Active Member

    Unlikely that any BEAM would become completely free to collapse and drop straight down... Columns would likewise need to be translated laterally. The load would cause the columns to cripple/buckle because the cross sectional area required to support the load was so reduced. It appears that most of the more or less intact steel (columns) broke apart AFTER bracing was stripped off with floor collapse.

    Failure columns means the loads they carried--- to be transmitted axially to the column below had to be redistributed... and this can over load the structures that carried the new increased load... causing them to sag, buckle and fail and that is how the structural failure rapidly propagates through the structure. It's complex and likely very hard to model accurately.
     
  31. Oystein

    Oystein Active Member

    This does not address the post you quoted at all.

    I was talking about how the simulation software used by Hulsey and team represents the various types of structural elements as they intersect. Not what happens in reality. Specifically, does the software at all consider that materials will tear or break when overloaded? Does it only determine material response at the connections and perhaps treat the length of beam between connections merely as mathematical lines in space - such that beams would pass through beams as, for example, two floor assemblies run into one another?
     
    • Agree Agree x 1
  32. Steen and Claus

    Steen and Claus New Member

    Mick,

    Excellent analysis on the blueprints.

    Without the data(!) and a mirror setup of his model, we can't test if Hulsey has deliberately left out/added/misplaced the structural elements in question in order to get a desired result.

    What we can do, is conclude that there is a discrepancy between the blueprints and the model Hulsey used:

    - Some elements are missing.
    - Some elements are added.
    - Some elements are misplaced.

    The last is interesting: Hulsey makes a big point out of Column 79 on page 80:

    "According to NIST, the initiating failure occurred at the connection between Column 79 and girder A2001 at Floor 13 due to a relative displacement of girder A2001 of 6.25 inches. Our ABAQUS analysis corroborated the findings of our SAP2000 analysis, showing that girder A2001 would undergo less than one inch of westward displacement relative to Column 79 under the worst-case fire condition. Examining all possible conditions, our analysis found that the westward movement of girder A2001 relative to the base plate on Column 79 was 3.68” for noncomposite, 2.18” for partially composite and less than 1” for composite behavior (the condition at time of the fire)."

    But if the green in the S-8 drawing (your analysis) is misplaced by 11", what effect would that have?

    These questions should definitely be put to Hulsey:

    Why is there a discrepancy between the model and the blueprints?

    What effects do the missing/added elements have on the simulated scenarios?

    Mick, could you check Colum 79 and see if that is placed correctly?

    /Claus
     
    • Like Like x 1
  33. Steen and Claus

    Steen and Claus New Member


    IT consultant with +30 years of experience here.

    There will be a whole system behind the simulations, and that will be the litmus test for whether Hulsey is honest or not.

    The input data alone is worthless. Hulsey needs to publish everything, ready for installing on SAP2000 and ABAQUS.

    An analogy:

    1) I write a VBA program that analyses Excel data. The program relies on a database of constants and variables as well. The analysis proves Earth is flat.
    2) I publish the Excel data only.

    What are you going to do with the Excel data alone? It tells you nothing of how I got to my conclusion.

    /Claus
     
    • Like Like x 1
  34. Mick West

    Mick West Administrator Staff Member

    I was chatting with @gerrycan on Twitter, and a few things came up, specifically for looking at the UAF presentation given by Hulsey, and most about the global collapse simulations.

    Firstly, Hulsey never seems to mention "dynamic analysis" when showing the collapses. In one slide at 01:01:23 he says:
    Metabunk 2019-09-23 15-14-10.
    He then shows the odd fake-looking rotation which is in the report as figure 4.16 (except it's Penthouse44 in the presentation, Penthouse46 in the report)
    [​IMG]

    via GIPHY


    Source: https://giphy.com/gifs/VCn5AOzBAr2kgkkTcY/html5


    Not this is backwards to the order things are presented in the report, where he discusses static analysis first, and then the above animation, which is described as "dynamic analysis results"

    Hulsey then goes on to discuss the static analysis. He says there's two colors, red and green. Red indicates failed, green indicates not failed. But of course initially none of the columns exceeded their load capacity, should all be green. In fact, Hulsely seems to have misunderstood what is the green means. Green is used to indicate columns that have not failed, but were manually removed to initiate or progress the collapse. The grammar and spelling of this slide indicate it was written by one of his students (both were Chinese, not native English speakers).
    Metabunk 2019-09-23 15-28-47.

    The three slides later this is made very clear:
    Metabunk 2019-09-23 15-30-25.


    "would fail just to keep the progressive collapse proceeding" - So this seems to indicate that they did a linear static analysis step, and the building settled into a steady state, so they selectively removed more columns to make the collapse proceed. They continue doing this several times. The last such slide they show is at 1:04:05
    Metabunk 2019-09-23 15-34-47.

    This matches 4.12 in the report. But in the report there's a final image 4.13
    Metabunk 2019-09-23 15-36-35.

    This shows everything failing except for two columns which are in tension (obviously they would immediately fail after this step)

    He then shows a different version of the static analysis visualization, on two slides.
    Metabunk 2019-09-23 15-38-11.

    Metabunk 2019-09-23 15-38-48.

    Why is this purple, and not multi-colored, you ask? It's because of those weird appendages at the bottom. Those are significant errors in the analysis. Members that have been displaced so far away that the color code used for displacement has everything close to 0 displacement, even though the roof has moved over 100 feet. The color scale automatically adjusts to the range of things in the model.
    Metabunk 2019-09-23 15-41-08.

    Here the top is about 25E+12, i.e. 25,000,000,000,000 inches. So something has gone wrong with model, causing bits of it to be displaced thousands of miles below ground, and stretched out across that distance. Who knows if that has any effect on the physics. But it indicates a very glitchy model - and that's on top of it being hand tweaked with columns selectively removed.
     

    Attached Files:

    • Informative Informative x 2
  35. Mick West

    Mick West Administrator Staff Member

    There's also this image he shows for a flash. (not in the report)
    Metabunk 2019-09-23 15-50-42.

    Metabunk 2019-09-23 15-51-27.

    Presumably, floor 13 at some point in the static analysis. Notice the fractured floor around C79 and C80
    Metabunk 2019-09-23 15-53-28.

    This appears to sort-of match an earlier slide, also not in the report.
    Metabunk 2019-09-23 15-54-02.
    Notice nothing breaks though.
     
    • Informative Informative x 2
  36. Mick West

    Mick West Administrator Staff Member

    Revisiting the static model visualization in the report, they are quite high resolution.
    Metabunk 2019-09-23 16-02-53.
    That's a portion of 4.15, showing which columns on the left side are connected (green). I had mistakenly though these were at the back, but it seems they are at the side.

    This does not match anything analysis result. The closest is figure 4.12:
    Metabunk 2019-09-23 16-06-23.

    However the corner column is still there, and only the next two columns down are in tension, whereas five columns are in tension in the 4.15 visualization. So this seems to be a visualization of something else.

    I suspect the figures 4.8 to 4.13 came from the simulation that produced the "purple" visualization. Metabunk 2019-09-23 16-10-19.
    Since this is obviously glitchy and inaccurate, another version was done, patching the glitches, and that is what was used in the report.

    It is quite different. With three less floors (the bottom three) and a different set of smaller glitches.
    Metabunk 2019-09-23 16-17-58.
     
    • Informative Informative x 1
  37. Mick West

    Mick West Administrator Staff Member

    Here's a close-up of the newer glitches.
    Metabunk 2019-09-23 16-20-20.
    Of additional interest there's a local origin (the cyan with X,Y,Z arrows) - a point about which things can be rotated or scaled. Rather an odd place for one. However, it might simply indicate they had accidentally selected an element before taking the screenshot.
     
    • Informative Informative x 1
  38. Miss VocalCord

    Miss VocalCord Active Member

    I think the glitches are a result of how they have modelled the connections; They simply can't break or snap so every column they don't remove will simply be stretched into eternity.
     
  39. Mick West

    Mick West Administrator Staff Member

    There would be a lot more if that was the case. We see similar things in game development.

    Metabunk 2019-09-24 05-36-36.

    There's a variety of quite different reasons why this would happen: code bugs, data bugs, engine bugs. It's a bug though.

    At that point in the simulation, neither the purple or the (slightly neater) rainbow model are accurate representations of the actual physics of the building. Not that they ever really were, and it's not just the large distortions - things like the side columns stretching has no correlation with reality.
     
  40. Oystein

    Oystein Active Member

    Did he contribute any insight?

    I assume this means they never considered that, during load redistribution, any additionally load on any member will at first present a dynamic load that's (at least) double the static load, right?

    Frankly, I had all along understood the colors of the circles this way: Red means "fails structurally - a result of analysis", green means "did not fail, we select this for manual take-out in the next iteration"

    Holey shmoley! :D
    It's been obvious immediately that these simulations are glitchy, but that that they are THAT glitchy...
    And to think that these obvious glitches are never discussed!
    I understand it is not unusual for FEA to produce wildly divergent results when pushed beyond numerical limits that are difficult to estimate ahead of time. Such that any FEA result should receive a thorough reality-check. Obviously, Hulsey did not do this at all.