Merged Apollo "hoax" discussion / Lick observatory laser saga

Status
Not open for further replies.
I wrote the following over at ApolloHoax while I was waiting for the administrators here to approve my account. I'll post it here too, since that's where I had intended it to be read.

<really interesting stuff>

Did you see this, Patrick? This is how you do it.

See how much solid information it contains? This post is one tenth the size of your wall of garbage, yet somehow yours has not one tenth as much worthwhile content.
 
I watched Transformers: Dark of the Moon earlier in the week. The historical inaccuracies around the Apollo missions were so numerous I couldn't stand it and had to stop. A scene at NASA in 1961 with models of the rockets from the Redstone to Saturn V behind a character at a desk. The CSM was heading to the Moon without the LM. When the Autobots travel to the site of Apollo 11 the ascent stage is still attached to the descent stage. To name a few of the anachronisms.

I also lost a little respect for Dr. Aldrin for appearing in it.
 
I love that essay/post. I think it is downright fantastic! beautiful! Read it again mate, you'll catch on.
Do you honestly think that that wall o'text is a good piece of English writing? It's not. It's littered with unnecessary repetition, comma splices and run-on sentences. It's also poorly set out for reading on a screen due to the lack of spacing. Instead of making pertinent points, it obfuscates in order to hide a lack of actual content. My advice is to rewrite it using bullet points and clear, unemotional language.
 
Patrick - before I bother struggling through it, is there anything new in the wall above, or it it just a rehash of the same old stuff?

Mostly not, but there is one risible nugget.

MAKING SENSE OF MICHAEL COLLINS' MAP




My general approach here focuses on a detailed study of the now infamous "J Map". The map Michael Collins carried with him in lunar orbit. Of course it is the very same map to which his handlers refer in their advising Collins as to where he should look on the surface of the moon in order to find his colleagues. Actually, the map carries the notation LAM 2, June 1969 in its upper left hand corner. But I like to refer to it as the "J Map" and so I shall, this emphasizing the "Juliet" reference.

Yes, believe it or not, P1K is attempting to pretend that he was au fait all along with Juliet and cartesian coordinates, even though he believed that these coordinates were part of the "Julian system" and represented RA/Dec numbers. Probably hoping we would all forget his comic faux pas.

But at least he was embarrased enough to try to hide it in a mammoth wall of text.
 
Also, if they had been in space, they'd have gotten a heck of a lot cozier with the bowel flora of their spaceship mates than the cislunar sanitation people would allow, let alone a qualified doctor. All the Apollo Missions are proven bogus right there, the sanitation angle.
Have you ever been on a camping trip, or changed a baby's nappy (diaper to you 'merkin types), or been in an enclosed environment such as a submarine? Your scatological fixation is becoming ridiculous.
 
(waves) Welcome to the JREF forum, Jay.

As you are no doubt aware, "Patrick1000" is yet another sock-puppet of fattydash, mvinson, piersquared, DoctorTea, BFischer, BSpassky, sicilian, etc. He is still pretending to be a doctor, writer, grown-up, mathematician, etc., and still recycling the same "if I ran the zoo" arguments. He's added some new mistakes and self-contradictions while keeping the old ones. One thing he has not added is any actual evidence for any of his claims - such as I'd asked him for numerous times over the past few months before writing him off as a troll. He persists here because JREF doesn't require posters to back up their claims.

Anyway, welcome over. You've prompted me to remember I want to write a simulation that interfaces to Virtual AGC... sometime... when I get around to it. Probably after retirement, or the heat-death of the universe, whichever comes first.
 
Last edited:
...believe it or not, P1K is attempting to pretend that he was au fait all along with Juliet and cartesian coordinates, even though he believed that these coordinates were part of the "Julian system" and represented RA/Dec numbers. Probably hoping we would all forget his comic faux pas.

But at least he was embarrased enough to try to hide it in a mammoth wall of text.

I liked the way he called it "the now infamous J map". As if it were to blame for his making an ass of himself.
 
Have you ever been on a camping trip, or changed a baby's nappy (diaper to you 'merkin types), or been in an enclosed environment such as a submarine? Your scatological fixation is becoming ridiculous.

I just finished reading Bill Bryson's "At Home", which contains some colourful descriptions of sanitary conditions in 18th and 19th century London.

If P1K had it his way, then London would be a ghost town, and all English people dead.

Having kids is the best way to become intimately acquainted with all manner of icky human secretions. Thankfully, I am past the worst of that now my kids are older.
 

Two, one guy courageous enough to simply become more or less open minded...

Are you referring to yourself? Sorry, but I don't see you as either courageous or open-minded.

Specifically, you aren't open-minded enough to consider that you may be wrong. Your argument below is based on the same premise you've used for months now. That premise has been refuted many times by trained and experienced experts, but you simply turn a deaf ear to it.

Open-mindedness means exactly to consider an idea on its merits rather than on one's preconceptions, and here you quite definitely ignore problems with the merit of your premise and concentrate solely on your preconceived belief in its correctness, buttressed by your misconception of the underlying technical points. Open-mindedness does not mean simply opposing the mainstream.

What exactly about your approach is courageous? You post in internet forums under assumed names and identities, hiding behind web proxies. You haven't submitted any of your findings to the historical and technical community for publication, and you can't abide even the casual objections of the people you encounter.

In contrast it takes courage to admit that one's previously cherished beliefs do not stand up to a factual analysis. It takes courage to walk away from a bad idea that you once advocated. But instead of standing up to your faults, you hide and dodge. That's the essence of intellectual cowardice.

A second guy to encourage the first not to lose his nerve.

But as can be attested by the administrators of the various forums in which you've posted, and from which you've been repeatedly banned, you bring your own cheering section. I struggle to see how that brand of dishonesty qualifies you as a serious researcher.

As for the remainder of this wall of text, it hardly bears detailed comment. It's the same slurry you've been shopping around the internet for the past two months, with little variation. You have nothing new, that hasn't already been soundly debunked. You simply don't understand how it all worked, so you ignorantly cry foul. Now it appears you're just looking for a receptive audience so you can bask in your courageous, open-minded glow.

You say there's no other answer except for fraud, but in fact there is an answer that's been staring you in the face (or rather, beaten over your head repeatedly) for months: you aren't capable of understanding how it all works. You have constructed an intricate web of misconceptions and personal expectations for how you think space missions ought to be conducted, and you propose to elaborately make the facts fail to fit that concocted standard so that you can triumphantly cry fraud.

Sorry, but there's a reason all the suitably educated people believe that Apollo was real.

A story, a piece of history, a real life factual account, must by its very nature have consistency, internal coherence as a feature.

No. That is the huge mistake that amateur historians make. Historical accounts of true events are always inconsistent, often on critical points. In fact, an abnormally high degree of consistency among different accounts of the same event is generally taken to mean that the "separate" witnesses have colluded on a story, also mistakenly believing that they won't testify credibly unless their stories match faithfully.

My analysis of the Apollo 11 Mission Report document below will be difficult for some.

You wrongly assume that people believe in Apollo because of some romantic devotion. People believe in Apollo because that's where the multitude of facts point. Look at this thread. You don't see people wringing their hands and lamenting the attack upon a cherished belief. Instead you see people pointing out how the facts support their belief, not yours. You don't get to pretend that your opponents are arguing emotionally when they patently are not.

It is harsh and devastating...

No, it's just wrong. And it's wrong now in exactly the same way it was wrong before when people refuted it.

So as tedious as the coordinate study and number crunching was/is, it all paid off.

Hogwash. You've simply established what was already known and accepted by Apollo practitioners and mainstream historians: that there is variance in the assessments of the landed LM's location.

Originally you tried to argue that this would have prevented them from rendezvousing with the CSM. But after I and other professional engineers laid bare your utter ignorance of how guidance systems worked, you've now shifted over into this new "historical inconsistency" line of attack.

Finally, I should like to remind the reader to keep in mind the intentional game of misdirection being played here, coordinates appearing in radian form, conventional decimal form, map lettering/numbering, with and without the trajectory to map conversion/correction factors.

No, you don't get to accuse others of misdirection just because you don't know how to read a map.

...one nevertheless anticipates reasonably good agreement with respect to the major features of a major story's telling.

No, that is the layman's misunderstanding of the study of history -- a wrong and oft-repeated mantra that has undone more than one lying witness.

Think carefully about the presentation above, utter coordinate chaos.

No, utter handwaving. Just because you cover your hand in a sequined glove before waving doesn't mean you have a case. You're desperately trying to manufacture a discrepancy so you can pat yourself on the back for your cleverness.

This stuff never happened. It quite simply doesn't add up.

No, you aren't the first to conjure up a standard of proof out of whole cloth solely for the purpose of showing how the facts don't measure up to it, and for no other purpose. The other times you tried to do this, you made the mistake of inventing a standard of proof that had objective flaws -- the medical condition of Apollo 8, the rendezvous problem on Apollo 11. And people more knowledgeable than you showed you at length why your standard of proof was ill-informed and unreasonable.

Now you've tried a "softer" approach, arguing that the study of history demands a certain consistency in its sources, and that the only explanation for inconsistency must be the assertive claim of fraud. You infer that your proposed standard of authenticity arises naturally from the study of history and as such needs no explicit defense.

If you are simply following the natural conventions of historical scholarship, can you explain why professional space historians such as William Burroughs, Jeffrey Kluger, Andy Chaikin, and the Coxes -- ostensibly following your same natural standard -- reach such vastly different conclusions than you do? Isn't it more likely that your opinion differs not because you're the first scholar in four decades to see the light, but because you're the last to see it?
 
Have you ever been on a camping trip, or changed a baby's nappy (diaper to you 'merkin types), or been in an enclosed environment such as a submarine? Your scatological fixation is becoming ridiculous.


I was on a sub when the Aux of the Watch neglected to shut a certain valve and blew 500 gallons of Sanitary Tank contents (urine and feces) out of the Officer's head. It spread throughout the Forward Compartment middle level, lower level, and Torpedo Room.
 

(waves) Welcome to the JREF forum, Jay.

Thanks, I've been reading here for years actually.

As you are no doubt aware, "Patrick1000" is yet another sock-puppet of fattydash, mvinson, piersquared, DoctorTea, BFischer, BSpassky, sicilian, etc.

Of course; that much was obvious.

He persists here because JREF doesn't require posters to back up their claims.

Indeed. As I pointed out, he seems to be looking for an audience rather than a discussion.
 
I was on a sub when the Aux of the Watch neglected to shut a certain valve and blew 500 gallons of Sanitary Tank contents (urine and feces) out of the Officer's head. It spread throughout the Forward Compartment middle level, lower level, and Torpedo Room.

Yuck! I'll bet that guy was in some pretty deep sh-- ... oh, never mind. :)
 
I wrote the following over at ApolloHoax while I was waiting for the administrators here to approve my account. I'll post it here too, since that's where I had intended it to be read.

Program alarms are little more than error messages, although the response to them may automatically take any of several forms: business as usual, a soft restart, or a hard restart.

The soft restart is a software routine that resets a few key data structures, stops nonessential tasks, and reloads the real-time tasks from a predetermined, prioritized table. But it leaves alone things like the state vector and the REFSMMAT. A hard reset is equivalent to powering on the computer anew. 120x alarms prescribe a soft reset.

As you recall, there are only 2,000 words of erasable storage in the computer architecture. The operating system breaks that up into small segments, each of which can be allocated to a running program. Some are reserved for the interpreter and allocated separately by it. The 120x errors indicate that no segments of erasable storage are available for some program that asks for one, and the last digit of the 120x indicates whether it is a regular segment or an interpreter-allocated segment that was asked for.

What exhausted them? The real-time tasks. Normally the small real-time tasks started up, scheduled their next invocation, asked for erasable storage, did their deed, released the storage, and exited -- all in very short time. Some like Servicer ran every 2 seconds and completed their work in just a hundredth of a second or so.

But in the case of Apollo 11 the computer was unexpectedly overloaded. So the real-time tasks took more wallclock time to complete than normal. As a result they never got to the part of their program that released the core sets (the little segments of erasable memory) before new real-time tasks started up according to their wallclock schedule and demanded memory.

So new tasks being scheduled by the relentless wallclock tick of the timer interrupts found the erasable memory glutted by tasks delayed in the relative world of multitasking computing. Under a normal workload there was plenty of computing capacity for all the tasks the designers had assigned.

And what was taking up all the computing power? As stated, the rendezvous radar. In certain modes the radar interrupts the computer periodically to tell it new information. The computer stores it in memory were programs that need radar information can get to it. The radar generates information at a fixed rate, governed by a timing signal from the computer that is interpreted by the radar's power supply. The power supply tells the radar's digital interface when to interrupt the computer.

Now the rendezvous radar was considered important, so it has two redundant power supplies, each locked to the computer timing signal. The radar was in SLEW (i.e., manual) mode at this point. In SLEW mode no data was supposed to be sent to the computer, so the synchronization between the power supplies was allowed to "float" and the digital circuit was supposedly disabled. But it turns out that the out-of-phase power input confused the radar's digital circuit and caused it to emit computer interrupt signals. Not only that, the out-of-phase power-supply cycles generated twice as many interrupts as the digital circuit normally should have. As much as 15 percent of the computer's capacity was being eaten up in accepting the overzealous radar information.

Why was the radar on? Because in an abort, they'd have to turn on the radar, wait for it to warm up, and then give it time to lock onto the CSM and produce good range/rate data. Apollo 11 planners thought it would be a good idea to keep the radar on and warmed up in order to reduce the crew's workload in the case of an abort. Normally in the plan, the radar would be turned off. And in that case it wouldn't have been generating interrupts.

Even under this unexpectedly high load from the double rate of radar interrupts, when none at all were expected, the computer was holding its own. But then Aldrin innocently and expectedly punched Verb 16, Noun 68 into the computer. Verb 16 means "monitor on the DSKY" and Noun 68 is a set of descent parameters: range-to-go, time-to-go, and velocity.

Under the hood, V16 activates a real-time task to read the values from the proper noun location -- here a known place in Program 63's erasable memory -- and load them into the DSKY display registers at regular intervals (once per second, if I recall correctly). A very simple routine, but in this case the straw that broke the camel's back. The continuous-display request was just enough additional workload to keep other real-time tasks from exiting cleanly and releasing their memory before it was needed.

Program 63 is, in guidance terms, a workhorse. It has a lot to do. Programs 64 and 66 require less computing power, so after the computer switched descent modes to P64, the overall computing load lessened so that the computer could maintain its normal workload even with the radar interrupts blazing.

When 120x alarms hit and the soft reset occurs, one of the first things that gets eliminated is the real-time display routine from Verb 16. It's not on the "magic" list of required real-time tasks for this flight mode, so Aldrin's display blanks and the computer goes back to a lean-and-mean operation. Only when he re-enters the display routine does he get in the same situation -- "It seems to happen whenever we have a 16-68 up."

In addition, Armstrong several times switched the flight controller into ATT HOLD mode (i.e., manual flight) which considerably reduces the digital autopilot's workload. ATT HOLD (i.e., attitude-hold, which simply keeps the LM fixed in the attitude the pilot establishes with the joystick) isn't as demanding as the modes ordinarily employed in the programmed descent modes. So in P64 and P66, with Armstrong occasionally flying manually, the computer was able to keep up with the spurious radar interrupts, and even V16N68.

In later LMs the rendezvous radar was revised to properly cross-strap the power supplies even in SLEW and AUTO TRACK mode, and the CDUs (the digital interface circuits) were revised to more reliably inhibit interrupts altogether except in LGC radar mode.

Welcome to the JREF.

Nice post much like your ones at BAUT.
 
I was on a sub when the Aux of the Watch neglected to shut a certain valve and blew 500 gallons of Sanitary Tank contents (urine and feces) out of the Officer's head. It spread throughout the Forward Compartment middle level, lower level, and Torpedo Room.

Of course that could never have happened, because the entire crew would all instantaneously gastroenteritis or something.

Therefore submarines are a hoax. :jaw-dropp

BTW welcome Jay, good to see you back around.
 
Yuck! I'll bet that guy was in some pretty deep sh-- ... oh, never mind. :)



Yes, he went to Captain's Mast and got a suspended bust, a big fine, etc.

The boat stank for weeks afterward but that goes without saying. We didn't "abort" the mission. We stayed at sea and continued our mission.
 
You want to spend some time on a frigate in a North Atlantic storm, with the crews Head (sea toilet) up in the bows you get a lovely poop bidet when the ship is ploughing into the swell. Makes for a slippery deck to say the least.
 
You want to spend some time on a frigate in a North Atlantic storm, with the crews Head (sea toilet) up in the bows you get a lovely poop bidet when the ship is ploughing into the swell. Makes for a slippery deck to say the least.

Indeed. My brother-in-law is a communications officer on a Perry-class FFG, and he doesn't have much good to say about the plumbing. But then again he's in the South Pacific and therefore not in as much of a position to complain about the weather.
 
Status
Not open for further replies.

Back
Top Bottom