My fiancee has a couple degrees while I just graduated high school. She's incredibly smart but I'm definitely more street savvy. She grew up a bit sheltered.
Genuinely asking, I'm just an engineer... with very very bad grades. Passed was enough for me.
Once a professor asked me if I wanted to take the exam again because it was clear that I knew more than what I showed on the exam (a lot of 2 + 2 = 5 mistakes, I was fairly good at that and owe most of my low grades to that). I asked him if I passed, he said yes. Fuck that shit, I'm taking that grade and parading it across town, wooohoo 🥳.
As they say, a PhD is about learning more and more about less and less. Some of the smartest people at conferences I've attended legitimately risk death crossing the street.
I actually went and checked the minimum air gap to avoid arcing at 10,000V at standard sea level air pressure and it's actually measured in millimeters.
Further, is the voltage differential there between parallel conducting lines or is it between the lines and the ground?
I'm really having trouble seing how a dry stick would cause arcing between two of those lines short of bringing them nearer than 4 mm in the first case, much less between one of the lines and the ground in the second case if its being held at chest level.
PS: Mind you, it does make sense with a stick which is not dry - since the water in it makes it conductive - but then the guy himself would be part of the conductive circuit, which kinda defeats the point of using a stick.
What you want to do is create an arc between the stick and the line, and not have it transfer to you. A dry stick would do this quite well, since it would be at ground voltage and as such would provoke a short arc without electrocuting yourself. The fence also probably doesn't have all that much power, likely can't deliver more than a few amps, so it would be quite safe even.
My professor (computer science - NP complete problems specific) had a theory.
Higher up your education, more and more you learn about less and less.
I am convinced he accidentally stumbled across Buddhism all on his own (he was a religious Christian, the generous, do not judge others kind). Because Buddha seems to have done his PhD in nothing. Even "wrote" the whole dissertation on nothingness.
My university basically gave up with a couple of professors. They hired a personal assistant, full time, just to try and keep them organised. They apparently settled on 3 phone calls, to make sure they made lectures on time. It even extended to things like reminding them to actually get their wives birthday presents, and personal book keeping.
It seems the human brain has a capacity limit. The more specialist knowledge shoved in, the less room for more normal knowledge. Eventually it displaces even the most basic common sense.
Meet the German word Fachidiot: (derogatory) A person who is only interested in their own trade or research area and has few or no other interests or skills.
I'd like to report that the more specialized a medical doctor is, the less common sense they have.
Had a doctor chew me out because he couldn't be bothered to simply turn the computer on.
That was the issue. Pushing a button was beneath him. Cool man, I'm the only one here at this hour and the phones have to be manned constantly. That ticket can go to another department and wait until they come in morning.
Also, low priority and I noted that the doctor refused to simply turn it on.
Well, I have an EE Degree specialized in Digital Systems - pretty much the opposite side of Electronic Engineering from the High Power side - and I would be almost as clueless as that guy when it comes to testing a 10,000V fence for power.
On the other hand I do know a lot of interesting things about CPU design ;)
First a fair warning: I learned this stuff 3 decades ago and I've actually been working as a programmer since then. I do believe the example I'll provide still applies up to a point, though CPUs often implement strategies to make this less of a problem.
=====
CPU's are internally like an assembly line or a processing pipeline, were the processing of an assembly instruction is broken down into a number of steps. A rough example (representative but not exactly for any specific CPU architecture) would be:
Step 1: fetch assembly instruction from memory
Step 2: fetch into the CPU data in memory that the instruction requires (if applicable).
Step 3: execute arithmetic or binary operation (if applicable).
Step 4: evaluate conditions (if applicable)
Step 5: write results to memory (if applicable)
Now, if the CPU was waiting for all the steps to be over for the processing of an assembly opcode before starting processing of the next, that would be quite a waste since for most of the time the functionality in there would be available for use but not being used (in my example, the Arithmetic Processing Unit, which is what's used in step #3, would not be used during the time when the other steps were being done).
So what they did was get CPUs to process multiple opcodes in parallel, so in my example pipeline you would have on opcode on stage #1, another that already did stage #1 and is on stage #2 and so on, hence why I also called it an assembly line: at each step a "worker" is doing some work on the "product" and then passing it to the next "worker" which does something else on it and they're all working at the same time doing their thing, only each doing their bit for a different assembly instruction.
The problem with that technique is: what happens if you have an opcode which is a conditional jump (i.e. start processing from another point in memory if a condition is valid: which is necessary to have to implement things like a "for" or "while" loop or jumping over of a block of code in an "if" condition fails)?
Remember, in the my example pipeline the point at which the CPU finally figures out if it should jump or not is almost at the end of the pipeline (step #4), so everything before that in the pipeline might be wrong assembly instructions being processed because, say, the CPU assumed "no-jump" and kept picking up assembly instructions from the memory positions after that conditional-jump instruction but it turns out it does have to jump so it was supposed to be processing instructions from somewhere else in memory.
The original naive way to handle this problem was to not process any assembly instructions after a conditional jump opcode had been loaded in step #1 and take the processing of the conditional jump through each step of the pipeline until the CPU figured out if the jump should occur or not, by which point the CPU would then start loading opcodes from the correct memory position. This of course meant every time a conditional jump appeared the CPU would get a lot slower whilst processing it.
Later, the solution was to do speculative processing: the CPU tried to guess if it would the condition would be true (i.e. jump) or false (not jump) and load and start processing the instructions from the memory position matching that assumption. If it turned out the guess was wrong, all the contents of the pipeline behind that conditional jump instruction would be thrown out. This is part of the reason why the pipeline is organised in such a way that the result of the work only ever gets written to memory at the last step - if it turns out it was working in the wrong instructions, it just doesn't do the last step for those wrong instructions. This is in average twice as fast as the naive solution (and better guessing makes it faster still) but it still slowed down the CPU every time a conditional jump appeared.
Even later the solution was to do the processing of both branches (i.e. "jump" and "no-jump") in parallel and then once the condition had been evaluated throw out the processing for the wrong branch and keep doing the other one. This solved the speed problem but at the cost of having double of everything, plus had some other implications on things such as memory caching (which I'm not going to go into here as that's a whole other Rabbit Hole)
Whilst I believe modern CPUs of the kind used in PCs don't have this problem (and probably also at least ARM7 and above), I've actually been doing some Shader programming of late (both Computing and Graphics Shaders) and if I interpreted what I read correctly a version of this kind of problem still affected GPUs not that long ago (probably because GPUs work by having massive numbers of processing units which work in parallel, so by necessity they are simple) though I believe nowadays it's not as inadvisable to use "if" when programming shaders as it used to be a few years ago.
Anyways, from a programming point of view, this is the reason why C compilers have an optimization option of doing something called "loop unrolling" - if you have a "for" loop with a fixed number of iterations known at compile time - for example for(int i = 0; i < 5; i++){ /* do stuff */ } - the compiler instead of generating in assembly a single block of code with the contents of the "for" loop and a conditional jump at the end, will instead "unroll the loop" by generating the assembly for the body of the loop as many times as the loop would loop - so in my example the contents of that "for" loop would end up as 5 blocks in assembly each containing the assembly for the contents, one after the other, the first for i=0, the next for i=1 and so on.
As I said, it's been a long time since I've learned this and I believe nowadays general CPUs implement strategies to make this a non-problem, but if you're programming microcontrollers or doing stuff like Compute Shaders to run on GPUs, I believe it's actually the kind of thing you still have to take in account if you want max performance.
Edit: Just remembered that even the solution of doing the parallel execution of both branches doesn't solve everything. For example, what if you have TWO conditional jump instructions one after the other? Theoretically would need almost 4 or everything to handle parallel execution for it. How about 3 conditional jumps? "Is you nested for-loop screwing your performance? More news at 11!".
As I said, this kind of stuff is a bit of a Rabbit Hole.
Humidity in the air makes that wayyy more dangerous because your skin will be highly conductive and the lower the resistance, the higher the current (which is what really hurts).
I’ve been a human grounding strap a couple times and don’t recommend it. I think the vibrating pain of AC (someone reenergized the outlet on me) is worse than the punch of high voltage (failing spark plug wire I grabbed with metal pliers while diagnosing a misfire).
My arm once got pulled into an electric fence when I was a kid and I couldn't stop getting shocked until someone physically pulled me away. It was more of a self-control issue than accidentally bridging the gap.
That was the day I learned that some pain can be pleasant. The owner of the property didn't seem as pleased with my discovery as I did. He had to shut off the fence and yanked my arm away and then told me to go explore my perversions somewhere else. I was too young to understand the word "perversion," and I'm now eternally grateful to that poor unprepared rancher.
You find it enjoyable? I regularly touch electric fences, but not because I want to but because I'm too stupid to think of another way to figure out if the thing is working. I find it to be the opposite of pleasant.
At approx 3kV/mm, you would have to be pretty close to a 10kV fence.
Humidity plays a big role as does the frequency that the fence is running on. But you would be pretty safe standing a meter away, on that dry sunny day in the picture.
Also above a point, the high voltage causes the conductors to buzz.
If I'm not mistaking the buzz is because it's AC hence the buzz frequency is the same as the AC's.
Certainly it makes sense that the high voltage would be generated from mains power using a big fat transformer since that's probably the simplest way to do it.
I have a 10KV electric fence. 5KV to 15KV is typical electric fence voltage in a farm or bear prevention fence. Can't feel a thing unless you actually touch it.
They are also not lethal. Very low current, just very high voltage. So it only hurts like fuck, but won't kill a human, cow, or any other mammal that touches it.
They can kill an animal (including a mammal) if they become entangled and give up out of suffering, though.
This is pretty rare, but can happen.
It's virtually zero risk to a human, though, who can cognize things like getting their hand disentangled from a string (even in a panic situation), or to most mammals, which tend to jerk backwards on contact.
This is why you should never try to remove a tree from a power line yourself.
Electricity always takes the path of least resistance back to the source. A tree, and possibly your body, may end up being the "path of least resistance".
You won't know if YOU are the path of least resistance or it the line is even energized until it's too late.
about 10kV per cm i believe. you're only at risk of it arcing to your body if you're within a centimeter of the wire. and that assumes your body to ground is a good conductor (it's not)
Just because you're very good at one thing doesn't mean you're good at another. Sometimes the further you go down one path, the less you know about everything else.
I always saw it as being part of messing with the kids, he looks at the warning lights on top of the fence first. And for my headcannon at least, Grant is savvy enough to know that's no way to test if the fence is live or not, lol.
He is already standing too close and that stick would arc with that many volts flowing through it. The most likely outcome in reality if it had been energized. The arc would have jumped from the stick to him and no more New Zealand guy.
You ever saw a electric fence at a high security installation? I just texted a guard at nearby prison and he said theirs are 5000 volts. He said when its humid they tingle when you get a few feet away. He also says they will kill you dead. He goes on to say its why they have another fence as a barrier to prevent people who don't respect them from killing themselves. I know the ones at a nuke were marked lethal and would kill birds from time to time. They were just marked high voltage but the plant guys told us they were very high voltage at a higher frequency.
Now if he'd just tossed the stick at it longwise so that it touched several wires at the same time, it might get a result. I'm personally not sure how much a reaction you'd get out of dry wood with 10,000 volts. Stripping the bark off of green stick with definitely be better, or a wet stick. Although if electricity arced through the stick at least it probably wouldn't kill him because of the amount of resistance that stick has.
I don't remember the scene, but personally I'd test an electric fence with a nonconductor. You'll probably get some sparks but won't die. You do you, ppl in this thread.
Characters in Jurassic Park are portrayed as flawed, imperfect people who make mistakes. None of the plot relies on them being idiots or anything, but people screw up, panic on occasion, and don't know things from time to time.
Dr. Grant using a stick to test the fence is a mistake, albeit a small one without real consequences. While it doesn't distract from his character arc of how he feels about kids, it is his character simply messing up.
I also disagree with the person you replied to. While their assessment is correct, Dr. Grant is a character with a lot of time working in the field and therefore has a lot of practical skills. He does way, way better than a doctorate in mathematics working in academia would. Writing off all people with a doctorate (or experts in general) as being hyper specialized is a mistake.
Even throwing a metal pipe against it won't do anything. Electric fences have one electrode in the ground, and that's how your body makes the circuit. If they had run and jumped onto the fence, then jumped off on the other side they would have been fine with the fences still active.
Source: I've set up an electric fence and been shocked multiple times, once through my head.
You're assuming the dinosaur fence operates on the same principal as a regular livestock electric fence. I put it to you that the Dino enclosures use alternating positive and negative stringer wires, where touching one won't do anything, but touching two will make a short circuit.
That would make a lot of sense, but as we can see the stringers are connected together, meaning they'd just short out if they were alternate polarities. To me this indicates that it's like a standard livestock fence, with an electrode in the ground somewhere and the circuit completing through the animal.
However, considering my 16'x48' pig enclosure required a three-foot rod to be grounded, a system large enough for a sauropod would need a lot of grounding. Considering this, the fact that they used a circuit-through-animal design indicates it probably wasn't the best way to do it.
Yet Tim gets shocked when hanging on the fence when it turns on while he’s climbing down. I trust movie science far more than your acquired knowledge. Your ignorance is probably what’s holding you back from full blown deity.
A PhD wouldn't know anything about science, so its pretty accurate really :/
Edit: It's the internet so naturally im being downvoted for learning but after looking it up, I was wrong. The PhD does stand for philosophy doctorate, but no longer refers specifically to the feild of philosophy as it once did. Apologies to anyone offended.