In attempting to educate Vixen on how gravity creates velocity, she resurrected a topic she apparently now wants to forget. She said,
This is evidently her prospective reason to reject the new findings, which will likely conclude that the hole in the side of
MS Estonia was caused by contact with the seabed. She says,
And of course she's the "true" skeptic in this scenario, so her understanding of how it's supposed to work factors into how credible her objection will be.
So what does the True Skeptic have to say about the water resistance of a sinking ship?
Well, what actually happened was he found the crack, and saw the rock outcrop that caused it, and left that part out. Even after he'd noted the wreck had shifted since it first sank.
Because in 1994/1995, the ship was laying at an angle that didn't allow divers or ROVs to get under the hull.
The wall fell in 1989. The Soviet Union followed in 1991. The Estonia sank in 1994.
The Russians were being kicked out of Estonia.
And? (spoiler alert, most Soviet gear is borderline line junk. See Ukraine)
And?
Mostly for comic relief.
And?
Which sounds cool unless you...
Now of course she didn't just pull that number out of thin air. She attempted to calculate it with the help of an AI. It was like pulling teeth to get her to admit it was an AI-generated answer. And it was obviously wrong, but we'll get to that.
Now Vixen wants to say:
The disavowal is an obvious lie. The link above is an unqualified attempt to solve the problem. The second part is yet another equivocation. She now admits she doesn't know how to calculate hydrodynamic resistance or impact force, but she can still—somehow—demonstrate how to do it, so she's begging you please not to laugh at the Triple-Niner.
Here's her "demonstration."
https://internationalskeptics.com/f...nia-case-reopened-part-v.356236/post-14082207 It's an AI-generated post, but she only lately accepted that we found that out. And now it's back in the news because she's referencing it again in hopes you'll still believe she knows something that all the relevant experts are allegedly ignoring. She has the relevant "dimensions" and might be persuaded to explain where the "gravity bit" fits in.
Having done this successfully for decades as a way to make a living, I'd say the first thing too consider is kinetic energy. Everything you want to know about a collision STEMs from that (pun intended). To think about it in terms of force, you want to know the stopping distance. What force does it take to stop an object of mass
m moving at velocity
v in distance
d? Then you can start talking about elastic or plastic responses in the materials, which feeds back into your stopping distance until you converge on an answer. You know you're off to a good start when your AI gets it wrong by the first sentence.
Well, yes, pressure is expressed as force per unit area. That's straight out of the first-year textbook. But then the AI gets the problem backwards. It takes a certain total force to stop a descending ship. That total force isn't
multiplied across the contact area; it's
divided by it. Two sentences = two errors. The AI is flunking basic physics so far.
As I've pointed out numerous times that's the definition of
hydrostatic pressure. It has nothing at all whatsoever to do with the water resistance (i.e., hydrodynamic drag) encountered by a sinking object. Hydrostatic pressure is exerted on everything, even on purely stationary objects under water such as the
MS Estonia wreck right now as it sits motionless on the seabed. And hydrostatic pressure is isotropic. "Isotropic" is Cockney rhyming slang for "acts in all directions." Hydrodynamic drag affects only moving objects and acts exactly opposite to the object's direction of motion.
Or in conventional notation:
I think that's a little low for the density of seawater, but we know the Baltic isn't as saline as deep ocean so we'll let that ride. We usually want
g to at least two decimal places. We'll never know why the AI—brain the size of a planet—is skimping on precision.
Two boo-boos. First the nitpick, which isn't as much of a nitpick as you might imagine.
g—"the gravity bit"—is given here in units of m/s². That's correct when your problem is asking about the acceleration resulting from Earth's gravitation. It's less obviously correct when your problem is asking about force, here the weight of a given mass as it proposes to exert a force. The proper units are N/kg as the strength of Earth's gravitational field at the surface in terms of force per unit mass. This becomes important as we combine the units algebraically to confirm that we got an answer in the units we expected. The numerical value is the same and the congruence of the concepts of gravitational acceleration and gravitational field strength is a proof that first-year students solve as homework.
The gravity bit is correct here, since it's the weight of seawater that we want. But we're talking about a ship sinking. Why does the weight and/or mass of the ship seem to have nothing to with the impact force, which is what the AI thinks it's computing?
The other boo-boo is the omission of the
other fluid involved: the atmosphere. The formulation and its solution are more properly :—
where
P0 is mean atmospheric pressure at sea level. That's
all the pressure of seawater over a square meter of whatever it is that's down there, without that thing having to be moving. If you need a pressure difference (so-called gauge pressure), then you need to make that rationale part of the problem. And as we've belabored, this number has absolutely nothing to do with either hydrodynamic drag or the velocity with which a sinking ship will hit the bottom. While pressure increases with depth of water, density does not. And it's density, not pressure, that determines hydrodynamic drag.
As I explained above, the AI has the problem backwards. It's trying to sew together two physics concepts that are individually correct (albeit both irrelevant), but which don't combine to solve the problem at hand. A competent physics student would notice this and reject the AI's answer.
When you're given pressure per unit area, it's appropriate to multiply that across the affected area to get the total load. That's how you would solve a problem such as a 44 m/s wind blowing against a window of known area. The "standard formula" for fluid dynamic drag I posted some pages back works for wind loading. It can compute the unit pressure of wind of a given density blowing at a given velocity. Then you can multiply by area (ignoring
CD for now) to give the total load.
But as I pointed out, here we deal with a total force that must be
divided by the contact area. That total force wasn't computed anywhere in the demonstration because the AI was confused about what was being asked for. We know it's a colossal force because it's the force required to stop a ship moving at a certain velocity in a very short distance. But at this point we don't know what it is.
Here the AI has just pulled a number out of its digital backside without any attempt to match it to the "dimensions" of
MS Estonia. It's warning Vixen that it has done this, but Vixen either doesn't know what to do with that or doesn't care. Rocks poke holes in ships because even smooth rocks don't have contact areas in the thousands of square meters. The force is concentrated in a small area of the ship's hull.
This correctly computes hydrostatic pressure at a depth of 80 meters over an area of 1000 m², but as far as the problem Vixen is claiming to have demonstrated goes, it might just as well be a recipe for salad cream. It could be a thousand square meters of seabed itself, without a shipwreck in sight. And it's irrelevant in a flooded ship, where water pressure increases uniformly on everything and not in a specific direction only.
Yet this is the figure Vixen reports as the answer for how hard the
MS Estonia struck the seabed. And this travesty of physics is how she imagines one would "demonstrate" that answer.
The competent physics student should have realized at this point that at no time did the solution incorporate the purported mass of the ship. It doesn't take a triple-niner intelligence to understand that a heavier ship lands with greater force than a lighter ship at the same velocity, and that therefore the mass of the ship should have affected the computation somewhere at some time. The 15,000 figure was never "plugged in" anywhere. The AI just mentions it in passing because it was input data.
And I'm pretty sure we already discussed that the 15,000 figure is the gross tonnage of the
Estonia, which is a commercially-defined metric that is nonlinearly proportional to the ship's commercially useful volume. It has practically nothing to do with the mass of the ship for physics purposes. It's not proper to refer to it as a "15,000 tonne" ship because gross tonnage doesn't actually have a dimension—certainly not metric tons.
Maybe Vixen will one day understand just what kind of heavy lifting this last bit has done. Our fee to a customer for figuring out everything after the comma in that sentence starts at three figures to the left of the comma.
But how about it,
@Vixen? Your "demonstration" is fractally wrong, to an extent that would get you a failing grade were you to have submitted this as homework or an exam answer. So what is it that you think you have "demonstrated" with this?