The UAP debates reminded me of a personal story about handling evidence and judging likelihood. I think this is interesting & amusing.
🧵:
On Shuttle mission STS-128 the rocket exhaust blew out 3,500 tiles from the side of the flame trench. /1
2/ The bricks were smashing into each other as they blew, fragmenting into millions of pieces of all sizes. The results were devastating to the perimeter of the pad. This is what the security fence looked like about a kilometer away. See the brick fragments? 🤯
3/ My research group collected an unbiased sample of fragments so NASA Marshall could use a realistic range of fragment sizes in their computer modeling of the event. This is @Ryan_N_Watkins and John Lane measuring and weighing fragments. (I’m holding the camera.)
4/ Ordinarily, nobody would have worried too much about the safety of the Shuttle itself since the brick release was beneath the mobile launch platform and the flame trench did its job ducting everything off to the side.
5/ However, we had an experimental infrared camera mounted on the top of the VAB watching the launch, and it detected a single piece of debris flying UPWARD near the Shuttle. This raised the question, could this or other fragments hit the Shuttle?
6/ This was a big deal because we lost Columbia when a piece of foam slammed into the leading edge of a wing and broke a hole in it, so during reentry hot plasma flowed through the hole and the metal structure failed. Loss of vehicle and crew.😢(image: ) https://t.co/2N8InQiJ0cspaceflightnow.com/shuttle/sts107…
7/ When we saw a piece of debris flying near the vehicle in liftoff of STS-124, we went into emergency mode. We were given 4 days to decide if it would be safe to land the vehicle, or should it stay in orbit until a rescue mission can be launched to save the crew? Four days!
8/ I had the idea that we could start by identifying the object by measuring its ballistics. My colleague John Lane had written software to interpolate between the frames of film cameras so we could combine multiple launch pad views to make the measurement.
9/ The problem was that the launch pad cameras were film cameras and the shutters were not synchronized between any two cameras, so each frame of the video was staggered relative to any other camera. John’s software interpolated the frames to synchronize them post facto.
10/ John got the blueprints of the launch pad and also went out to the pad to verify camera locations so he could do the math combining the two views.
11/ From this, John calculated the three-dimensional coordinates of the debris versus time as it flew upward next to the launching vehicle.
12/ John also measured the diameter, elliptical elongation, and rotation rate of the debris as it flew upward. (You could see it spinning.)
13/ My part of the effort was to write software that did the ballistics calculations and performed “simulated annealing” to determine the best fit parameters including origin, starting velocity, and material density of the object.
14/ The material density that was the best fit was exactly the density of a type of foam used to fill the throats of the solid rocket boosters before launch — to keep birds and insects out of the rocket so they don’t accidentally light the propellant by heating it somehow!
15/ So we showed conclusively that the high flying debris was just “throat plug foam”, not a flame trench brick fragment. And since the shuttle was still going slow at that time, a foam impact could not hurt the vehicle. Whew! 😮💨 Well, what happened next?… 😁
16/ We got that done in two days, so we we got scheduled to present our results the next day to the program managers to say it was safe to land. We went to the launch control center and gave our presentation with one day to spare.
But then,…
17/ …some folks from another NASA center had come to the meeting and they stood up and said that our analysis was WRONG. They had proof. They had checked our math, and they said we did the trigonometry wrong when we combined the two cameras. 🤔
18/ so they said the two cameras were not pointing exactly as we thought, and therefore the two videos showing debris flying up were actually showing TWO DIFFERENT PIECES OF DEBRIS.
That’s what they said.
19/ Well I didn’t say this in the meeting (because the managers took our recommendation anyways and proceeded toward landing), but I thought this to myself…
20/ Okayyy, so we know somebody made a math error. Either my guy Dr. John Lane who is one of the best applied mathematicians in the world with works-class experience in photogrammetry, or your guy. One of them made a math error.
If your guy is the one who is right, then…
21/…that means there were 2 pieces of debris instead of just one. And both pieces of debris had to have exactly the same size, same elongation, same rotation rate, same rotation phase, same starting velocity, same altitude in each timestep, same density & same deceleration, AND
22/…our math error had to be the *precise* error that made the 2 pieces exactly overlap in the horizontal dimensions so it made them look like the same piece. And on top of this, the infrared camera only saw one piece, so one was hot and one was stone cold despite the flames.😜
23/ On the other hand, if it was your guy who made the math error, then it was just a math error.
When you consider all that, you don’t even need to see the detailed math to know which one of them made the math error.🙃
24/ We published our results in Acta Astronautica. The preprint is available on the arXiv, here:
I was surprised one day shortly after these events when we had a staff meeting and an astronaut walking into the room...arxiv.org/pdf/0910.4357.…
25/ …and he presented the Silver Snoopy award for solving a problem that made human spaceflight safer. I felt deeply grateful for being noticed by the flight crew. Still one of the highlights of the NASA career. 🥲
But my point for now…
26/ …is that sometimes you can tell if math is wrong without even looking at the details of the math. I still laugh every time when I think about the extreme coincidences we were being asked to believe if our math had been wrong.😆 /end🧵
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The thing is, at such an early time in human (pre-)history, they did not have standardized number systems. This led to the very long ages of kings that we see in the Sumerian King List. A few details on how this happened… 🧵/1
2/Today, most cultures in the world use base-10, and we use it for every digit in a number. The first digit is ones. The second is 10s. The third is 10x10s. The fourth is 10x10x10s, and so on.
In early Mesopotamian number systems, they did not use the same base for each digit. This example uses ones, then sixes, then 10x6s, then 3x10x6s.
3/ Making it more confusing, they had a different number system for each type of thing they were counting. So they had one system for counting people, another for counting sheep, another for counting bushels of barley, another for counting years, etc. The concept of “numbers” had not been generalized as an abstract concept. Numbers existed only as “numbers of sheep” or “numbers of bushels”. It is analogous to the English system of liquid measures, where the number of teaspoons, tablespoons, cups, gallons, etc., is a different count in each higher measure.
2/ The first part of this story was likely embellished during the Qing dynasty but it is based in truth. When the Ming dynasty fell in the 1640s, a ruthless general of the peasant rebels, Liu Zongmin, took the concubine Chen Yuanyuan hostage and treated her abusively. Her lover (or husband), Ming general Wu Sangui, was of course humiliated and enraged!
Well, Wu Sangui was the general defending the Shanhai Pass at the eastern end of the Great Wall, responsible for keeping out the barbarian Manchu.
3/ Rather than stay loyal to the failing Ming or join with the ascendant Chinese peasant rebels, Wu Sangui was driven to seek swift retribution against those who abused his beloved concubine. He made a personal pact with the Manchus and let them through the wall. They swiftly conquered Beijing during its time of chaos and established the long-lasting Qing dynasty.
Sui Tang Yanyi (a later Qing-era novel) probably exaggerated Chen Yuanyuan’s role in this, saying that “the empire fell for her beauty.” Nevertheless, she became legendary for causing the downfall of the Ming and the establishment of the Qing. But how does this relate to Alaska?
1/ Let’s walk through a mining competition cycle. The students take their robots to the judge station for inspection and weigh-in. (More points awarded for lower-mass robots.)
2/ They set their robots on the forklift platform to lift into the arena.
3/ Robots are placed on the regolith in an orientation chosen randomly by the judges (so the robotic autonomy can’t be cheated).
@bobster190 @DJSnM @WilliamShatner The paper has all the citations to other work inside it. I linked the paper because it wouldn’t make sense to duplicate that in a tweet. The paper wasn’t about Pluto. It was only about asteroids. We wrote a second paper that discusses Pluto and I think answers your objections. /1
@bobster190 @DJSnM @WilliamShatner 2/ That 2nd paper is here (no paywall so it is accessible):
It does discuss the arguments surrounding the IAU’s vote in 2006. I think we did a much better and more complete review of the issues than any other publication on the topic. Most other papers…sciencedirect.com/science/articl…
@bobster190 @DJSnM @WilliamShatner 3/ …include patently false information about why Pluto was voted down by the IAU. For example, the claim that asteroids were demoted because they share orbits is utterly nonsensical. Even a cursory review of the publication history shows this. Also the claim that the Moon…
Here is something that hints strongly at how human scientists and engineers are already doomed by AI. 🧵
I noticed this tonight while using Grok for technical research. I asked it a complex question and Grok understood it completely and gave a sophisticated and highly believable answer, but when I asked for specific references so I can write it into a paper for a journal, none of the references Grok provided exactly support the answer it gave me. Instead, they hint at something deeper.
In this case, I am quantifying the loss of signal margin in a Moon-Earth communications link as a function of how many times you landed near the communication system so the rocket plume sandblasted the electronics' thermal coatings, causing them to operate hotter than designed. There is a real cost to sandblasting your hardware on the Moon, and I am trying to quantify it.
Grok gave me many quantified effects, including that the frequency oscillator will drift about 10 to 50 ppm per deg C of temperature rise outside its operating range and that the Signal to Noise Ratio of the overall communications link will drop about ~0.1–0.5 dB for small drifts (<10 kHz) in particular modulation schemes. This is a great result that I can use to quantify sandblasting damage on the Moon, and the result is totally plausible, but it doesn't appear in ANY reference that Grok provided. Nothing discusses this.
So I suspect Grok actually derived that relationship itself during the LLM training. I think the relationship is probably correct, because the many references hint around the edges of this relationship in the right magnitude. I think Grok noticed the patterns of many performance metrics including temperature, input power and frequency, outputs, etc., for many devices and how they are connected in typical systems, and it stored as a higher-level symbol the result that you get 10 to 50 ppm per deg C performance loss. I think it solved that during training as it sought the higher-order symbols to store everything it had learned. IOW, its learning process included a heckuva lot of valid inference on these technical issues, and it now knows more about the performance of communications equipment than even the published literature knows.
I asked Grok if this is true, and it says it is correct (screenshots).
/1
2/ I then asked Grok to derive this relationship the same way it probably did during the LLM training, and it did. So now, if I want to use this key result in my paper, I have to use the many references that Grok used when it derived the relationship, and I have to show the derivation explicitly in the paper, or I can't publish it per the rules of scientific publishing (which of course were created in the days before reliable AI, and we still don't have totally reliable AI, but we can see it is coming fast).
3/ So here is the derivation, which it says replicates the process it did during its LLM training, which led it to believe in the quantified relationship between frequency shift and signal to noise ratio. I'm including this just to show its character.
I think it’s likely the Outer Space Treaty will be voided within the next few decades as nations will claim (effectively) national territory on the Moon and Mars.
Here’s why I think this…
/1
2/ The OST is part of the International Rules-Based Order that emerged post-WW2. The IRBO was originally multipolar with the US-led NATO and Soviet-led Warsaw Pact. The collapse of the latter left the US as the main power wanting to keep the IRBO. China/the CCP hates this. theguardian.com/world/2023/oct…
3/ The CCP claims the rules-based order was set up when China was weak so it is unfair and needs to be replaced. They are aggressive at claiming territory in their national interest, disregarding the existing rules-based order by rejecting rulings of the international court. lowyinstitute.org/the-interprete…