Are 4 to 4.5 hour office fire simulations valid?

Fire, in conjunction with impact damage, is the most logical explanation and I can point to steel frame buildings that collapsed due to fire alone.





Since it is illogical to think that explosives were used, why waste time and money on another investigation?





Let's take a look at two examples, one where a building withstood multiple bomb strikes, yet remained standing.


Chinese Embassy Photo

http://www.paulmidler.com/wp-content/uploads/2009/05/a.jpg


Next, where fire destroyed steel frame buildings.


Kader Toy Factory Fire

At about 4pm on May 10th, 1993, a small fire was discovered on the first floor of part of the E-shaped building. Workers were instructed to keep working as the fire was thought to be minor. The fire alarm in this building did not sound.

The building was reinforced with un-insulated steel girders which quickly weakened and collapsed. This part of the building was dedicated to the storage of finished products and the fire spread quickly. Other parts of the factory were full of raw materials which also burnt very fast... Fire-fighters arrived at the factory at about 4:40pm, to find Building One about to collapse.

The Kader buildings,...collapsed relatively early in the fire because their structural steel supports lacked the fireproofing that would have allowed them to maintain their strength when exposed to high temperatures.

https://en.wikipedia.org/wiki/Kader_Toy_Factory_fire




You will have noticed after all of these years, not one shred of evidence of explosives was ever found, even in today's videos and photos and the recorded seismic data.





You seem to forget that you have to provide visual and audio evidence of explosives. I might add that none exist. Did you really think that explosives would have survived uncontrolled raging fires for several hours?

Secondly, there was no way to properly prepare the WTC buildings for explosive implosion in secret. To demolish a steel frame building with explosives takes many months of preparation and the process of structural pre-weakening is a very noisy and dirty operation that would not have been tolerated by those working within those buildings.

Secondly, I have said in the past that I could have planted 1000 pounds of explosives on each floor of the WTC buildings and detonate them all at once. Now, do you know why the buildings would have remained standing? I am very sure that you can find a video where a steel structure remained standing despite absorbing the blast waves from a nuclear detonation.

The New/Full investigation calls seem to come from the nut corner more than anything else.

It is as if there is a fatality in a residential fire, the fire marshal determines it was an electrical fire, the county ME determines it was smoke inhalation and from the peanut gallery someone asks if the ME and FM investigated the possibility of spontaneous human combustion and since no investigation was undertaken to prove or disprove the SHC theory the investigation wasn't competent or complete.
 
And you have an issue with FORTRAN because....?
Some of us learned FORTRAN as our first play with a computer....

....let's see.

...it was.....

** years ago (2016 - 1941 = ##)

must have been - oops giving my age away...must of been 50 years back....

OK - who around here used Fortran 11 and punched cards??

;)



Cobol, Math, Basic, (IBM) SPS, (IBM) Autocoder, PL1........(a very long break)..... can scratch a bit of Bash scripting if really needed but.....
 
Last edited:
And you have an issue with FORTRAN because....?

Because...
for dinosaur FORTRAN NIST agrees with me ... Its Alive! It's Alive!

I used it forty years ago when I did my architectural thesis on an IBM rubber banded card stack of instructions using the random number generator tied to the school's mainframe's clock to design the facades of my Arts + Science building.
It freaked out my jury professors and classmate audience .
"You're the architect. You're supposed to design the building, not the computer! "

"But I designed the idea and the computer program that designed my building!"
I got my Master.

BTW: Everyone including the jury teachers thought the building had a proportionately interesting, balanced syncopated look before I told them a computer had designed it.
This led to a spirited teleologcal debate.
 
Last edited:
Card handling logictics was a big issue for my firm.

around a million rated properties to be billed - originally annual billing but became quarterly.

And the rating info on two or more cards per property.

And the original card reader 600 cpm - later got an 1100 cpm machine still later put card images on tape.

But do the sums - its a lot of cards and a long run.

AND at one stage the need was to punch next years starter card. Card punch 250cpm. AND opposite end of card reader machine and cycle locked.

And back in those days the "CPU" was doing much of the control of reader./punch.

The engineering stuff relatively much smaller in logistics....

...but tears over dropped and out of sequence card decks was not unknown.
 
The common engineering task was water supply network analysis and I remember (if memory hasn't failed me) some benchmark runs on a typical network job.

45 minutes on the firms own small machine. (mostly slow processing - card I/O a minute or two)

3 minutes on an early IBM 360 (Half of that could be card I/O limited - I've forgotten the hardware setup)

a few seconds on a CDC 6600 (excluding the card IO time - it was a multi tasking data centre and each client had their own input room with card reader and output printer. Card reader 250 cpm.)

That would be circa 1968-69 at a guess.

Haven't a clue how that would compare with a modern PC.
 
Last edited:
Felt tip marker last name across the sides of the cards stack helped "recompile" them.
+ use rubber bands (plural)
If you got serious - allocate some columns to index number the cards so you could mechanically resort-resequence - but us engineers were notoriously careless for such things and occasionally paid the penalty.
 
Last edited:
BTW: Everyone including the jury teachers thought the building had a proportionately interesting, balanced syncopated look before I told them a computer had designed it.
This led to a spirited teleologcal debate.

I don't have an easily told computer use example...

...BUT as 61 yo "Mature Age Student" of Law I got to present a seminar on "Legal Ethics" to the class of ~30 mostly in their twenties.

I risked an "Instant Fail" when I opened with the statement "Legal Ethics is an Oxymoron".

Sure got the attention of the group AND the two professors.

That also set the scene for an interesting discussion. :D
 
Never used punch cards as a physics major.

However I later had to maintain and service an RTTY tx/rx system that used punch tape. The tape reader went kaflooey one evening. I was still recovering from a particularily liquid previous evening. I took that sucker apart, lubed all 65 million tiny ########## parts and reassembled it while a wee bit shaky and headachy. Amazingly my malady must have allowed greater focus and attention to detail(by causing me to move slower to keep my horizon steady), because I reinstalled it and it worked better and quieter than ever.


The RTTY was used to transmit weather data coded as a series of four character alphanumeric 'words'. The tech would use the tape punch terminal to code a full observation and feed the tape to the rtty. Without the tape the techs had to manually type the message and retype if they made a mistake. A tape could be scotch taped together from ones with mistakes.
 
Saw an engineering student get teary when he tripped and spilled his stack of punch cards
I can't multi quote on this phone, but all of the above is the reason for NASTRAN'S input format.
You can scramble the cards any way you want, and it don't care. Reads them in and sorts them the way they are supposed to go.
Despite its age, FORTRAN is an extremely powerful tool, and you can do all kinds of error checking as you go.
 
Never used punch cards as a physics major.

However I later had to maintain and service an RTTY tx/rx system that used punch tape. The tape reader went kaflooey one evening. I was still recovering from a particularily liquid previous evening. I took that sucker apart, lubed all 65 million tiny ########## parts and reassembled it while a wee bit shaky and headachy. Amazingly my malady must have allowed greater focus and attention to detail(by causing me to move slower to keep my horizon steady), because I reinstalled it and it worked better and quieter than ever.


The RTTY was used to transmit weather data coded as a series of four character alphanumeric 'words'. The tech would use the tape punch terminal to code a full observation and feed the tape to the rtty. Without the tape the techs had to manually type the message and retype if they made a mistake. A tape could be scotch taped together from ones with mistakes.
My experience - as client operation's engineer NOT the IT specialist - was a real time SCADA setup also monitoring weather - rainfall and runoff actually.

The source hardware was crude by today's standards - uniselectors and relays era. And "We" bolted a computer over the top of several base systems as a real time logger and alarm annunciator.

PDP8 fed by a paper tape program loader. 35 minutes load time after which the code for "Checksum Error" would flash up..


Grrr......

It really was a Heath Robinson setup. The data transmitted from outstations came as a sequence of telephone dial pulses from that era of telephone technology. You could listen and count the pulses as the uniselectors clicked through to the position. The computer interface simply used timing loops to detect start and stop of each pulse transmitted as an audio tone.

Heath Robinson would have been proud of it.
 
Last edited:
It appears that Tony, having lost this debate, is no longer posting in it.

Dave

Agreed.

Tony has so far posted 21 times in this thread, and has failed to even just formulate a proposition, an interesting question or valid, fact-based argument.

That's a terrible loss. Tripped and fell while not even having left the starting block, and still squirming in the dirt.
 
My experience - as client operation's engineer NOT the IT specialist - was a real time SCADA setup also monitoring weather - rainfall and runoff actually.

The source hardware was crude by today's standards - uniselectors and relays era. And "We" bolted a computer over the top of several base systems as a real time logger and alarm annunciator.

PDP8 fed by a paper tape program loader. 35 minutes load time after which the code for "Checksum Error" would flash up..


Grrr......

It really was a Heath Robinson setup. The data transmitted from outstations came as a sequence of telephone dial pulses from that era of telephone technology. You could listen and count the pulses as the uniselectors clicked through to the position. The computer interface simply used timing loops to detect start and stop of each pulse transmitted as an audio tone.

Heath Robinson would have been proud of it.

Sounds errr, interesting. :D
Amother bit of equip on the wx stations was the Ground Meteorlogic Device ( how woefully ambiguous) WW2 era balloon tracker homed on a 1.68Ghz signal from the instrument package. Thus recorded temp., baropressure, humidity, and wind speeds. In the past a tube driven chart recorder had been used and height and wind speeds calculated by the tech. New computer filled a rack. Had a whopping 256K memory, did most calcs.
Next up was to replace the IFAmplifier with new fangled solid state. Freq downconverter was stil tubes and live with -180 Vdc which made tuning painful if you touched the metal chassis at the same time.
 

ISF - Join now!

Every member here is approved by hand. No bots, no spam, just people who care about evidence and honest debate.

Membership is free!

Create your free account

Back
Top Bottom