*staggers out of a collapsed Jaeger*
It'll probably be a while before I can resume science posting, but I haven't forgotten about this blog.
Enjoy the K-Day anniversary, everyone! :)
*collapses - for now*
Monterey Bay Aquarium
will byers stan first human second
Alisa U Zemlji Chuda
NASA

Kiana Khansmith
Keni
YOU ARE THE REASON
cherry valley forever
Stranger Things

pixel skylines
Claire Keane

oozey mess

â
let's talk about Bridgerton tea, my ask is open
hello vonnie
Cosimo Galluzzi
Xuebing Du
occasionally subtle
Cosmic Funnies

Kaledo Art
seen from France

seen from United States

seen from United Kingdom
seen from Belgium

seen from Zimbabwe

seen from Netherlands

seen from TĂźrkiye

seen from France
seen from Germany

seen from United States

seen from Malaysia
seen from South Africa
seen from Argentina
seen from TĂźrkiye

seen from Saudi Arabia

seen from United States
seen from United States

seen from Moldova
seen from Saudi Arabia

seen from United States
@pacificrimscience
*staggers out of a collapsed Jaeger*
It'll probably be a while before I can resume science posting, but I haven't forgotten about this blog.
Enjoy the K-Day anniversary, everyone! :)
*collapses - for now*

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch ⢠No registration required ⢠HD streaming
pacificrimscience said:I donât drink either, but now Iâm tempted to propose a drinking game based on the track we just recordedâŚ
âââââââ-
Take a sip when Science! is discussed. (enough alone to get drunk at this step)
Another when the Science! in the movie is pretty good, albeit still flawed.
Take a sip when we talk about accents.
Another when theyâre actually good!
Take a sip when we talk about subverted tropes.
Another when we gush about Mako being a strong protagonist.
Down the glass when Jamie says âNewtâ instead of âNewtonâ.
(Bear in mind that this is a bit of a joke; I'm not trying to encourage excessive drinking.)
As an extension of that first rule I propose the Picky Scientist Rules for a drinking game, also known as the Picky Person in STEM Rules:
Before starting the game, choose what categories of Science! discussions will require drinking. (There are a lot of Science! discussions. The categorization lets players roughly control how drunk they'll get.)
Subject matter categories:
Jaegers
Kaiju
Physics
Chemistry
Biology
Neuroscience
Engineering and technology
Computers
Drifting
Type of discussion categories:
Inaccurate Science!
Accurate Science!
Mental replacements for inaccurate Science!
Engineering practice
Design decisions
Science! combined with literary devices
Other
Players are also allowed to create their own categories.
Any (combination of) logical operators on categories may be used, provided that the result doesn't impose conditions on the discussions themselves. Here's some examples:
"Inaccurate physics and engineering" (really "inaccurate Science! and (about physics or about engineering)") is a valid set of discussions to drink to.
"Chemistry xor kaiju" is also a valid set of discussions to drink to.
"Take two sips if the discussion is about mental replacements for inaccurate Science!" is also valid, but is an additional rule rather than just a set of discussions to drink to.
"If a discussion is about physics, it must be about inaccurate Science!" is invalid, because it imposes conditions on the discussions in order to be a true statement.
(Yes, this means players get functional completeness to work with. There are no restrictions on how complicated the criteria for drinking get, but of course the players will have to work through those criteria while playing...)
Once the criteria for discussions to drink to has been defined, start the movie and commentary track.
Take a sip for every discussion that meets the criteria set for that game.
If there's any disagreement or confusion about whether a particular discussion meets the criteria, count it as meeting the criteria and take two sips instead of one.
If a player notices a possible Science! discussion topic (directly related to something in the movie) that meets the criteria but isn't mentioned on the commentary track, that player must declare the topic to everyone else in that game. Everyone playing then downs their glass.
If a previously declared topic (within the same game) turns out to be mentioned later on the commentary track, take a sip.
Just finished laying down a commentary track with the-oxford-english-fangirl, pacificrimscience, and jkrockin!
I think we only got to cover a mere FRACTION of topics to discuss about Pacific Rim. Which is GOOD, because I know there are folks who wanted to record tonight, but couldnât for various reasons.
If youâre part of the commentary project, weâre shooting for another session, possibly Sat the 14th, 6-8pm EST. Iâll be shooting out some emails this weekend. If you are on the project and donât have my email yet (and I donât have yours) and youâre still game to record at some point, please shoot me an Ask.
Itâs been a bit like herding cats (no oneâs fault, this is a horribly busy time of year) and Iâm very excited weâre finally starting to lay down tracks. I was worried weâd be spending the entire movie just ::internally screaming::, but we all actually do have some very interesting commentary to bring to the table; Iâm excited to release the audio and companion website very soon. :)
Iâll post a followup when the raw audio is done encoding â weâll also be doing some cleanup and whatnot due to a few technical hiccups. Itâll be like a rifftrack â you can listen along while watching your own copy of the movie.
I know weâve only just scratched the surface - I kept all my points very short trying not to dominate the track, which means there are a lot of juicy details I didnât address. (The extended versions are either already on this blog or will be coming when I get to write them up.)
And now that I know what recording these is like, Iâm sorely tempted to try topic-specific tracks that do include all those details. One for physics, one for biology and chemistry, one for neuroscience and Jaeger programming (yes really) ⌠alas, much more research and time is required to make that work.
Did somebody say âphysicsâ and âPacific Rimâ in the same sentence? Iâm in!
If you want to record with us, get in touch with so-i-did-this-thing. I'm not sure if he's currently taking more people, but you can ask and find out!
If you just want to listen to people (mostly me right now) discuss the physics of Pacific Rim, check out the commentary track and website when they come out.
Just finished laying down a commentary track with the-oxford-english-fangirl, pacificrimscience, and jkrockin!
I think we only got to cover a mere FRACTION of topics to discuss about Pacific Rim. Which is GOOD, because I know there are folks who wanted to record tonight, but couldnât for various reasons.
If youâre part of the commentary project, weâre shooting for another session, possibly Sat the 14th, 6-8pm EST. Iâll be shooting out some emails this weekend. If you are on the project and donât have my email yet (and I donât have yours) and youâre still game to record at some point, please shoot me an Ask.
Itâs been a bit like herding cats (no oneâs fault, this is a horribly busy time of year) and Iâm very excited weâre finally starting to lay down tracks. I was worried weâd be spending the entire movie just ::internally screaming::, but we all actually do have some very interesting commentary to bring to the table; Iâm excited to release the audio and companion website very soon. :)
Iâll post a followup when the raw audio is done encoding â weâll also be doing some cleanup and whatnot due to a few technical hiccups. Itâll be like a rifftrack â you can listen along while watching your own copy of the movie.
I know we've only just scratched the surface - I kept all my points very short trying not to dominate the track, which means there are a lot of juicy details I didn't address. (The extended versions are either already on this blog or will be coming when I get to write them up.)
And now that I know what recording these is like, I'm sorely tempted to try topic-specific tracks that do include all those details. One for physics, one for biology and chemistry, one for neuroscience and Jaeger programming (yes really) ... alas, much more research and time is required to make that work.
Hello!
Hello everyone, and welcome to my blog!
(Iâm still in shock over this. O.O Itâs an incredible honour.)
A few things you should know about me and this blog:
As much as I love Pacific Rim and science, I cannot write science posts all day. Science posts also take time to write (and often research), even if the post is just reviewing an article. This means that this is generally not a high-post-volume blog. Please be aware of this, especially since
I take questions through ask / submit! There are a few caveats though:
It will probably take some time to answer your question, due to point 1 above.
I try to keep this blog active even when I havenât been able to finish an answer yet. Just because Iâm making other posts doesnât mean Iâve forgotten about a question.
Before sending in a question, please check whether itâs already been answered by me or Travis Beacham.
Depending on the volume of questions I get, I may not be able to answer all of them.
My answers are not official.
I am currently extra-busy due to real-life time demands. This means longer lead times for questions and somewhat less activity than Iâd like, but donât let that deter you from sending in questions!
I write for an audience with a very wide range of backgrounds, both in science and in general. I try to keep my writing accessible without being overly long-winded, but I am by no means perfect. Clarification questions are welcome, and constructive writing feedback is always appreciated.
On occasion I make not-strictly-science(-or-STEM) posts. Please donât be surprised.
I cannot read every reblog of my posts. If you want to show me a particular reblog for any reason, send me a message. I also track my URL tag, #pacificrimscience, in case you want to show me a post.
I hope you enjoy this blog!
Bringing this back for my new followers.

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch ⢠No registration required ⢠HD streaming
VERSION 0.1?!!
For godâs sake, I can only imagine what the bugs were like⌠or this is just a mockup done in After Effects (with the pilots pretending to be in sync while the jaeger goes through some pre-programmed stuff) to impress the top brass?
THIS IS WHAT I THINK ABOUT AS A PROGRAMMER.
Iâm so glad to see someone else noticing this, it gets me every time. How do you even get to that as v0.1? Not even v0.1.5 or something, itâs just their first go. I bet they donât even have source control, thereâs one hard drive with the entire Jaeger program on it. If someone just dropped it or overwrote some code the Kaiju would win. The pilots are being overwhelmed with debugging messages where the programmers just had it print out relevant variables and then forgot to remove the code, if they rotate their hand anticlockwise the hemispheres switch and theyâre not sure why yet. The pilots say the drift smells like raspberries and nobody has a clue why so they just assure them itâll be fixed in v0.2.Â
And then when they finish the demo the first thing the brass asks is if the green hemisphere could be a little greener.
#life of a programmer, #//fix the raspberies, #Jaeger.doTheThing();, #driftStrength = complicatedFunction() + 2 // Works better with +2
OH GOD, I AM CRYING. THIS IS ABSOLUTE TRUTH.
I'm also happy to see someone else noticing this. I have so many things to say about this picture, including some that will go in another post I've been drafting for months.
The thread above made me laugh very hard, mostly because I've seen many similar things in my own programming experience. (If you want to hear my programming stories, ask me on my personal blog.) Let me add some more:
Sometimes one of the external libraries crashes on perfectly valid input, to the programmers' consternation. They'd love to use a better library, but first they need to brass to approve the time and funds to find/make one and modify the code to use it. And the brass won't approve that unless they're pleased with the demo.
As a temporary measure they put all direct use of that library in its own process so at least it can't crash the whole program when it goes down. The code is littered with sections like this:
// always use the manager for this library; // it handles the inter-process communication // NEVER load the library in this process; // it crashes erratically nextValue = LibraryManager.getNextValue(); log(nextValue);
if (nextValue != -1) {    // works better with -3    complicatedFunction(nextValue - 3); } else { // library crashed    // put backup code here at some point }
During the demo they discover a whole new failure mode for that library -Â it suddenly starts producing nonsense values for no apparent reason. This leads to sending a lot of nonsense to the pilots, who aren't very happy about the sudden distraction but keep going with the demo.
The programmer watching the logs on another screen notices within a few seconds and has to kill the process dealing with that library to make the nonsense stop. The pilots aren't very happy with the imperfect communication (due to incomplete backup code) either, but it's better than constant distraction and they both have the planned demo sequence memorized anyway.
As the pilots are heading back to talk to the brass, one of the programmers snags a radio and explains the sudden stream of nonsense to the pilots. They promptly help the programmers get approval to use a better library, but due to the need to rewrite a lot of code the new library isn't fully integrated until version 0.2.5.
On the other hand, it might not be that bad.
Maybe this isn't a demo to show other people, it's just an internal test. (No one should see version 0.1, there are too many bugs in it for that.) The demo that got the first line of Jaegers ordered (in Tales From Year Zero) probably didn't have much Drift software at all, since Caitlin Lightcap bridged in in the middle of it without even knowing if Drifting was possible.
And they might have used mock data at that point rather than actually hooking pilots up to it. I know I'd be wary of hooking someone up to version 0.1 of a brain-computer interface where the computer can send data, especially since in this case bugs could really hurt.
But sometimes good software development practices don't get followed...
And can we talk about the medical equipment of some sort beside that screen?
I Finally Made a Personal Blog
It's here. I haven't posted very much on it yet, but at least it's set up now.
DO YOU LOVE PACIFIC RIM? DO YOU LOVE PACIFIC RIM *AND* ARE INTO FILM CRITICISM?
OH BOY, THEN DO WE HAVE A PROJECT FOR YOU!
The Pacific Rim fandom has shown it has a talent for deconstructing storytelling and pop culture. Thereâs a significant amount of âmetaâ authors who write film commentary on everything from the influence of past kaiju movies to costume design to the roles of gender and culture in Makoâs character arc.
By the time the BluRay hits shelves, we should have enough material for a fan-made commentary track.
I think this could be a really cool collaborative project and am looking to recruit fellow fans who would be interested in contributing meta commentary on the film. Our end product would be an mp3 that people can download and play in sync with the movie.
Topics could include, but are not limited to:
An examination of character tropes and how they are fulfilled/subverted
Visual storytelling through color, symbols, camera angles, etc.
Characterization through costuming
Portrayals of gender, culture, disabilities
Comparisons to other genre films
Homages to kaiju movie source material
Musical motifs
"Did you notice" (background fun stuff, easter eggs, etc.)
Right now, Iâm am throwing out a CALL TO ARMS for those who would be interested in contributing. Hereâs a link to a signup form:
https://docs.google.com/forms/d/1RlZhX7dwmQhL3Wz81jZDswh4IMhaTLcCb7hyxbv2VkQ/viewform
General guidelines:
There will be a limited number of slots for actual commentary recording; people will be selected based on subject matter and where it falls within the movie - we want a variety of topics spread throughout the entire film so thereâs little dead air.
Recording will most likely happen in chunks to allow for the greatest amount of flexibility + number of participants.
If you donât want to / canât record, you can still submit written meta for consideration for inclusion and someone else will read it for you.
Differing criticisms/interpretations are cool as long as they are persuasive enough and well-argued.
Fanons/head-canons will probably be unavoidable, please exercise good judgment. Same thing with relying on supplemental materials. Using the artbook as a spring-board to discuss Guy Davisâ contributions to the movie as a creature designer as his previous experience as an artist on the BPRD comics? Yes! Using the artbook as your primary source for discussing certain character traits/backstory that never appear in the movie? Probably not ok.
A day or so after signups close, an announcement will be made to cover deadlines and how weâll be collecting meta commentary. Donât worry, youâll have time to watch the BluRay and Guillermoâs own commentary a few times. :)
UPDATE
Weâre winding down on the signup window, so please submit an app if youâd like to participate!
We have an AMAZING collection of contributors so far (everything from theater and music people to engineers and scientists), and Iâll be contacting yâall Saturday, so keep your eyes peeled on your Ask / Fanmail boxes if youâve already submitted an app.
I will make one special appeal â while we have a few kaiju movie experts now, weâre still lacking a little on the giant mecha front. So, if your expertise is in GIANT ROBUTS weâd love to have you!
Signal boosting this.
I have signed up myself, but that doesn't mean all the science spots are full.
Hi there! Love your blog, it's so much fun! :D I have a question about Kaiju Blue, if you or anyone else would like to hypothesize about it. We know it's kaiju blood, but other than being acidic and corrosive what would make it so toxic and stain-y? Does anyone have any opinions or hypotheses about the epidemiology of Kaiju Blue poisoning? What would it do to the body? According to MM&M "If Kaiju Blue is inhaled, the victim will begin to cough up a blue vapor." Thoughts anyone?
Hi, and thanks!
Thatâs actually quite a few questions! Iâll go through them individually.
We know [Kaiju Blue is] kaiju blood, but other than being acidic and corrosive what would make it so toxic and stain-y?
That could be due to any of a lot of chemicals; I canât say for sure which ones are even in kaiju blood, but you may enjoy the K-Science discussion.
Does anyone have any opinions or hypotheses about the epidemiology of Kaiju Blue poisoning?
Iâm not an epidemiologist (and I donât have sufficient background to give it a good shot); anyone want to share some thoughts?
What would it do to the body?
We donât know exactly whatâs in kaiju blood, so any guesses at its effects on humans may well be incomplete. Iâll give it a shot based on what we do know, but anyone is welcome to help out.
As you mentioned, we know that kaiju blood is acidic and corrosive. Some acids are corrosive, so this combination makes sense. Even without exact chemicals, we can look at the effects of corrosive substances in general. The relevant European Union hazard symbol (source) is pretty clear about it:
Exposure to corrosive substances results in chemical burns (warning: linked page includes pictures of severe tissue damage). Wikipediaâs section on the effects of corrosive substances on living tissue gives us more details:
In addition, some corrosive chemicals, mostly acids such as hydrochloric acid and nitric acid, are volatile and can emit corrosive mists upon contact with air. Inhalation can damage the respiratory tract.
Corrosive substances are most hazardous to eyesight. A drop of a corrosive may cause blindness within 2â10 seconds through opacification or direct destruction of the cornea.
Ingestion of corrosives can induce severe consequences, including serious damage of the gastrointestinal tract, which can lead to vomiting, severe stomach aches, and even death.
Read the whole description there if youâre curious; I only quoted part of it.
According to MM&M âIf Kaiju Blue is inhaled, the victim will begin to cough up a blue vapor.â Thoughts anyone?
Coughing is pretty useful for getting things out of oneâs airway. The catch is that it exposes other people to those things. The Precursors may well have designed the kaiju for that effect, especially since the vapor could easily be inhaled by others who might then start coughing themselves. (It depends on whatâs in the vapor, but I donât think it would be good for humans.) We know that kaiju are built to be as troublesome as possible, and I expect that to extend to after they fall.
In light of this, I'd like to discuss the scenario above. (Original comic here.) It's not as simple as it looks.
(Aside: video games as Drift-compatibility tests? Totally workable. I really should run through Portal 2's co-op (again) with some of the people on my copilot candidate list.)
Drifting while playing video games? Also workable, but tricky. There are the obvious advantages, the not-so-obvious advantages (like how Mako seems to be using Raleigh's view of the screen to continue playing in the last panel), and then there's separating who's doing what.
Let's face it, most 2-player cooperative video games require both players to be doing different things at the same time. Each player would have to keep track of their own stream of thoughts corresponding to actions (walk, turn, shoot portal, ...) without getting mixed up by the other player doing the same. I imagine that would be rather tricky.

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch ⢠No registration required ⢠HD streaming
[[several layers of indenting cut; click username link above to see previous posts with cut text]]
Yes, come join the K-Science party!
Oh, luminol. Iâd been considering it just for the color and intensity, but it really doesnât last long and would basically have to be constantly reacting with something else to produce that sustained bright glow the kaiju gave off, so that miiight not be the best option. That list of light-emitting compounds looks like itâll be awfully handy!
I had also thought about a red tide parallel, and I like that idea a lot! The bioluminescence is about right, and red tides are actually horribly toxic and can cause respiratory issues and severe neurological symptoms including memory loss and paralysis in humans, and kill other marine species outright. Iâve been basing my theories on Kaiju Blue around those effects, but the reason behind both the blue glow and the production of toxins by the phytoplankton in question is poorly understood in real life, so your guess is as good as mine on the interdimensional alien front.
[[Thatâs what happens when you start a K-Science division. :)
For those who donât know, the cut and partly cut posts can be accessed by clicking on the username links at the top.]]
While I was researching one of my previous answers I found some links that might be useful.
Thereâs a list of silicon compounds, although I donât think itâs complete. As was previously mentioned, some of them do not play well with water, but others look interesting. (That idea about ceramic bones? Check out silicon nitride. It would be tricky to grow inside a kaiju, but for a lot of the cases weâve seen the Precursors could have just printed it in.)
Thereâs also a Wikipedia article on hypothetical types of biochemistry which talks about a variety of different possibilities. Maybe this will spark some ideas? (Multiple element substitutions?)
Hm, the red tide thing is interesting, but when people say âred tidesâ theyâre not always talking about the same thing - for example, the nasty kind down in the Gulf of Mexico, Karenia brevis, produces fairly potent neurotoxins, but is not bioluminescent. On the other hand although the âred tideâ here in SoCal, Lingulodinium polyedrum, has been âassociatedâ with certain toxins, theyâre a thing that affects humans so little that people will intentionally go to the beaches at night during an intense bloom for the sake of the experience of swimming or surfing in the bioluminescent water.
But again the problem comes up that those things only bioluminesce upon âimpactâ, whether thatâs by waves crashing or someone running across wet sand or whatever. Like, you can put them in a water bottle, shake it up, and the glow doesnât even last as long as luminol would.
More bioluminescence speculations! (And also more here.) While we're at it, do we know how long kaiju parts continue to glow for after a kaiju dies (and the reactions producing the bioluminescent chemicals stop)? I don't think we have enough samples to match the decay pattern(s) to chemical rate equations yet, but even a rough idea of how long they take to stop glowing will let us eliminate chemicals whose reaction kinetics are very different from that.
In light of other recent posts, maybe we should also be speculating on kaiju neuroscience. Anyone up for trying to figure out their minimum nerve conduction velocity once the DVD comes out? (Although it might vary between kaiju, especially if the Precursors were experimenting with kaiju nervous systems. We can try anyway.)
Admin Announcement
Until now, I haven't had a personal blog. Which means I've been using this as sort of a personal blog for the purposes of following people. I will be remedying this situation shortly.
This will not change the focus of this blog, but I will be reorganizing who I follow and on which account. There may be some delays in science posting while I prepare my personal blog, so please bear with me.
About Kaiju Brains and Coordination
In the tags of this post I mentioned that there's another point to be made about kaiju brains. So here it is, even though it's not just about kaiju brains:
Both of a kaiju's brains must constantly coordinate, and therefore must be linked, to get useful movement rather than the front and back trying to do different things (or other varieties of coordination messes). But if both brains have to approve of every action before taking it, the reaction time problem that required two brains in the first place comes right back. (Signals sent between the two brains are also subject to conduction velocity limits.) This means they can't be using such an approval scheme for quick decisions like combat reactions. (Less time-sensitive decisions, like which runoff trail to follow, could be approved that way or even debated back and forth between the two brains.)
So they have to coordinate even though each one can initiate movements without waiting on approval from the other. Each brain finds out the other's movement decisions only after they've been made and sent out through the kaiju's nerves. To make this work, each one has to anticipate what movements the other might make and work with them.
Let me sum this up: there's a neurological requirement for two linked brains that must constantly coordinate while also being able to anticipate and flow with each other's movements just to move around. (One-brain fallback is possible (theoretically for kaiju, anyway) but both limited and very strenuous.) And the neurological requirement is a consequence of the size of the thing moving. Sound familiar? It doesn't just describe kaiju...
It is my current opinion that there exists no neurological basis for Newt to have concluded that Kaiju would have a second "hind" brain. What are your thoughts on the subject?
Pretty much an extended version of this post. Relevant quote:
For a creature the size of a kaiju (many many times larger than any dinosaur), the nerve conduction velocity from the tail to the head would be something of a problem.
To give a concrete example of this problem, let's say a kaiju's tail gets grabbed in combat. For the kaiju to properly react (as in more than just a damage-prevention reflex, although I won't speculate on the nature of kaiju reflexes here), three things have to happen in order: the sensory signals ("tail grabbed") have to travel through the kaiju's nerves from its tail to its brain, the brain has to process those signals and decide what to do, and the motor signals ("move this way") for that decision have to travel out through the kaiju's nerves once again to reach the rest of its body (including its tail).
Those signals can only travel through nerves so fast (thus the term nerve conduction velocity), so bigger distances between the brain and the relevant body parts translate into longer reaction times. As the Precursors scaled up the kaiju, eventually the latency would get bad enough to cause issues in combat. (Imagine a kaiju not reacting to its tail being grabbed until several seconds later, by which point its tail may have already been sliced off.) This latency issue is why kaiju need a second brain.
I don't know what a kaiju's nerve conduction velocity would be, but presumably Newt does (and it's slow enough that the second brain becomes necessary). Based on that and observing kaiju reaction times for different parts of their bodies, he could figure out the presence of the second brain even if he hadn't seen it in reports or samples. The reaction time pattern (increasing roughly based on distance to the closer of two points, rather than one point as expected from a single-brain setup) would give it away.
Ever wondered what we can find out from that kaiju footprint? Here's your answer.

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch ⢠No registration required ⢠HD streaming
Do you know anything about radiation/radiochemistry? I work in nuc.med and I would LOVE to discuss the radiation and its effects on jaeger pilots (from first generations like Pentecost all the way to Gipsy Danger)
I know probably just enough about radiation and radiochemistry to have a discussion if I looked up a lot of details. I donât mind looking up lots of details, so I would love to have this discussion too. I just might be slow about it because looking up details takes a while.
Most of my knowledge about radiation comes from high school science classes and xkcd. I took all the science classes my high school had (physics, chemistry, and biology), so the mentions of radiation were scattered across a bunch of courses. I did learn basic things like the different kinds of radiation (and a bit about each), simple radioactive decay calculations, and some (probably highly simplified) stuff about the effects of radiation on the human body. There were a couple of cases where we read about radiochemistry experiments, but the word âradiochemistryâ wasnât mentioned at all.
So if weâre discussing, say, Pentecostâs radiation exposure just from Coyote Tangoâs reactor, I know that weâd have to go through a lot of steps:
Find out what reactions occur in Coyote Tangoâs reactor, along with what types of radiation they produce and the emission rates
Figure out how much of that radiation is actually headed in his direction
Account for the stopping power of everything between him and the reactor (which probably means weâd be dealing with mostly gamma radiation, but I wouldnât count out secondary beta radiation right away)
Figure out his exposure pattern based on his combat record
Find out the effects of that exposure pattern on different parts of the body
But then Iâd have to look up the relevant details for all those steps. Thatâs why I say I know probably just enough about radiation and radiochemistry to have a discussion if I looked up a lot of details. Your expertise would be appreciated. :)
*waves* Hey, Callmehobo, letâs talk! One of my research interests is nuclear technology and I really wanna ramble with somebody about how it was handled in this movie!
Honestly, one of the things that bothered me most about the science in Pacific Rim is how the nuclear stuff worked. (Nuclear reactors do not behave at all like nuclear bombs, even when malfunctioning! Cherenkov radiation is blue, not green! Nuclear and analog are in no way synonymous! The list goes on for quite a while, unfortunately.)
My main problem, though, has to do with the implication that Stacker was dying due to Coyote Tangoâs lack of radiation shielding. I donât care how quickly youâre throwing these robots together; one of the top priorities of working with any radioactive material is ensuring that appropriate shielding is in place, and even the end of the world is no excuse for ignoring that.Â
Even if the conn-pod is close to the reactor, I figure the pilots arenât spending more than a few hours at a time in their machines, and on a fairly irregular schedule at that. I think thereâs enough sheer bulk to a Jaeger to account for appropriate layers of lead and other insulating materials around the reactor, and under normal conditions radiation exposure should be minimal.
My working theory is that while Mark I Jaegers were appropriately shielded under normal operating capacities, the damage done to the machines by the kaiju would have been enough to compromise the shielding and expose their pilots to excess radiation. We know that Coyote Tango was heavily damaged in battle at least once (I have yet to read Tales from Year Zero and am a little fuzzy on details, bear with me) and both Stacker and Tamsin eventually developed cancer. I donât know anything about cancer rates in other Mark 1 pilots, but the Kaidonovskys seemed okay, soâŚ?
Calculating the impact of radiation on the human body is extremely difficult because there are many different variables at work, and this is where my knowledge base gets really thin. Iâd love to hear your thoughts on how and why the pilots were affected, and what that might have meant for the Jaeger program!
I want this discussion to happen.
Related: I reblogged this chain quite a while ago, and it has some relevant theories.
I was curious if you had thoughts/comments about the analog/digital 'divide' in Jaegers because honestly it made my engineer buddy and me look at each other a bit 'u can't b serious' while we were watching. Do you think there's any actual justification for that distinction?
I have a few comments on this, so here goes:
First off, you and your engineer buddy are not alone in having that sort of reaction. I did too, along with several of my friends (with widely varying science backgrounds).
On the other hand, one of my friends told me he interpreted that differently. Iâll let his words speak for themselves.
"That analogue vs. digital thing is a comment more or less on analogue and digital film modes. And even special effects. Itâs also pretty much saying âMan, these digital special effects monsters are nothing when compared to the classic physical puppet monsters.â"
Iâm going to stick to the science rather than comment further on that interpretation (literary criticism was never my strong point), but there you go.
Second, it is incredibly implausible that Gipsy Dangerâs systems (or any Jaegerâs systems) are entirely analog. This is because all Jaegers almost certainly have digital computers in their systems. The control panels and their displays? Those need computers. The holographic displays in front of the pilots? Those need computers. The dual Pons systems? Those really need computers, because thereâs a lot of processing involved in making that interface work. The human brain is complicated. Analog computers do exist, but I highly doubt those would be useful here due to their limitations. (Low precision and having to physically rewire them in order to make changes? No thank you.) So that leaves us with the digital computers we know and love as part of every Jaegerâs systems.
(Related note: nuclear does not imply analog in any way. In fact, modern nuclear reactors are digital too.)
Third, even analog systems can be disrupted by EMPs (Leatherbackâs attack). Depending on the circuits involved it might be harder to disrupt an analog system than a digital one, but thatâs a very flimsy justification.
Before I explain why, let me clarify the difference between analog and digital. Analog signals are continuous, like lengths, voltages, and states of dimmer switches. For any two lengths, no matter how close together, there's always a possible length in between. Digital data is discrete, like the letters in this post and states of on/off switches. There's no letter between 'a' and 'b' in the alphabet. Analog vs. digital is about the data, and is not limited to circuits at all.
What makes a circuit (or a part of a circuit) analog or digital is whether it uses electrical quantities (like voltages) to represent continuous or discrete data. In fact, transistors, which are hugely important to both analog and digital electronics, are sort of like dimmer switches. Digital circuits just use them in the on/off 'positions', while analog circuits mainly use the 'positions' in between. (I say "sort of" because this is a massive simplification, but I'm not assuming a circuits background and I'm not going to teach multiple courses in this post.)
At a low enough level, both analog and digital circuits have electricity running through various materials. And that is exactly the level at which EMPs wreak havoc. Overloading a transistor, or any other circuit component for that matter, will break it no matter what type of circuit it's in.
Fourth, there are more scientifically plausible ways to say âGipsy Danger wonât be disabled by that attackâ. My personal favourite is "Gipsy's radiation-hardened. That provides EMP protection too." This is a simplification, but it's reasonably possible depending on how the systems are designed. It also has the advantage of making sense for Gipsy's stated power source, because any sensible circuit designer putting important and sensitive systems near a nuclear reactor will insist on radiation-hardening them. Especially if they also have concerns like this.
I think there is a justification for some sort of âdivideâ between Jaegers to explain why Leatherback canât disable Gipsy Danger immediately like he did with Striker Eureka. There may be a very good reason for that divide to be analog/digital, but that reason isn't scientific accuracy.