Thankfully we were able to document some of our findings, prior to critical faliure. And our methodology is layed out clearly before us, so fret not. First of all, lay witness to one of our final, glorious simulations of a humble hydrogen particle. We can start by defining the space this bugger moves in! We decided to put the origin in a corner of a cubical box, briefly?described earlier, with sides (L) = 106metres. Our rationale behind this was more easily being able to decifer where in the room each particle would be, opposed to defining the origin in the middle. You see you are way more likely to be eaten by a turtle in the open ocean than you are by rocks, as you have less directions to worry about surveying. An upside to putting it in the middle, however, is that it would've made for an easy time defining the exit hole.
I discovered foot prints?leading up to the back part of the computers?
The way our particles knew to bounce, as you see to our right, isn't too complicated. All we have to do is check if the x-, y- or z-coordinate is greater than or equal to 0m or L (106m). As described earlier we then simply flip the relevant velocity in which the collision is executing a force upon, and we're golden. But how do you know which velocity to flip? We resorted to decomposing our vectors, so we first look at the motion in the x-direction, then y and so on, and so forth. Much like we should've decomposed our team into bite sized units to investigate after the outage...?I found shels around the cables, I'm putting in a better effort than they are.?The advantage to handling the problem this way, is it makes simulating the movement pretty intuitive after, and it allows you to look at each dimention on its own. The downside to it is you have to look at three times as many velocities and positions at a time. Just like the investigative team, not using my recent discovery of damaged wires, could it be teeth or even a beak?!
Now to how the nozzle was meant to be introduced before a certain?someone?decided to chomp the power cord. We were going to define an area at the xy-plane (where z = 0) and look at how many particles hit it, and at what speed, for a teeny speck of time. We'd then send the particles back into the box with a random position, and the same velocity, now this may seem odd, but it insures the gaussian distribution of velocity remains the same in all three dimentions, as this is how we're currently working. But the most important aspect to retian is the speed.?We'd repeat this for a slightly less teeny speck of time?until we had a rough idea about how many, and how fast these particles would exit. Giving us a change in momentum, once scaled up a little we can start playing with the rocket moving.?I'll make this investigation move along myself if I have to, there is even a part of his jelly-uniform here! Given the power outage caused by a trusted inside source, which I very much think know who is, we can't really comment on the results of this part. But we can comment on what kind of numbers we'd be looking to achieve by the end of the trial and error process of balancing fuel load, and output. So we'll be moving on to achieving escape velocity!?
"Escape" velocity = 549545087620063.94 m/s Escape velocity = 7771.741160478053 m/s Rotational velocity = 565.6253183645572 m/s
Those of you with keen eyes may have notices our slight squobble calculating the escape velocity, initially. It's a couple of magnitudes grater than you'd expect, only just beating out the speed of light by a factor grater than 106. At first this had us scratching our head