Space Voyage #1

[Pyrotex]

I left the bridge and headed toward my suite. On impulse, I took an alternate path. Frost's "The Road Less Traveled" echoed silently in the abyssian depths of my mind. Then I got curious as to how many possible, unique paths there were between Module A and Module B in a "cartesian-connected" system of four rings with twelve modules in each ring. Could this number be expressed as a function of module positions, or better yet, the ring displacement (0 to 3) and the "clock position" displacement (0 to 6)? Of course you would have to multiply by 2 to get the mirror image paths. Hmmmm...

 

I passed a door marked "Bakery" and thought of cake. Cake? I loved cake but the sugar always made me groggy. Not sleepy exactly, but kind of lethargic and dog-brained. I stopped. I pondered. I needed to perform an experiment to help verify my conjecture about Racoon. Yes. Cake would be the very thing.

 

I stepped in and obtained three wedges from a double chocolate layer cake. The young woman smiled and complimented me on my shirt and my choice of music. I would have to come back here soon and sample the other delicacies.

 

;)

And the bird you can not change.

Lord knows, I can't change...

[IDMclean]

No sooner had I said Duty then when my PDA alerted me with a quick little melody. I hasten to bring it out. It didn't take long to read through, but I had gotten a responce, so that ment it didn't drop "dead", so to speak.

 

I cursed at myself for the whole fiction part, should have made that clear.

 

Frist things first:

[math]\rightarrow MCP[/math] Fiction, is storytelling, fabrication of ideas that may or may not be contrary to the nature of reality. Humans, that is biological machines, that I am part of, are capable of this ideal fabrication.

 

[math]\rightarrow MCP[/math] I honestly can not convince you that I am telling the true or lying. I can say that I am telling the truth to the full extent of my ability to do so. Paradox, if I tell you that I am telling the truth, and you already believe me to be a liar (one who gives falsehoods), then will anything I say ever register, to you, as true? Like I said, I trust you.

 

[math]\rightarrow MCP[/math] Some fiction is useful, in my experience. For concieving of new ideas. I have given you reference to a few fictional references that I found helpful in creating new things. Some have proved to be blatantly not-true, and therefore false, but that does not mean that one can not learn a lesson, or use information from a given source. All fiction has a basis in reality.

 

I looked up from my zone, "Excuse me, I need to use this console for a moment." Typing on the miniture keyboard was somewhat taxing.

 

[math]\rightarrow MCP[/math] What I am saying, is that I did not give you fiction with the intent to do wrong, I did so in the intent to give you some ideas. Ideas, New functions, New perceptual ability.

 

[math]\leftarrow MCP[/math]

3.
        1. A literary work whose content is produced by the imagination and is not necessarily based on fact.
        2. The category of literature comprising works of this kind, including novels and short stories.

 

[math]\rightarrow MCP[/math] This would be the best category, and context of the given word, as I used it.

 

[math]\rightarrow MCP[/math] Now, query: What do you mean by not-self is blocking you? Not-self, as in Biological, or non-bio? I need a technical print out, if I am to help.

[TheBigDog]

Some things happen when you least expect it. I was sitting and contemplating what Pyro had just told me, and wondering to myself if was was hearing voices, or had an inconvenient itch. The through of Desiree's disease had me bugged.

 

My mind had fully wandered from command. I may even have been asleep. The alarm didn't alert me. The voice coming from the Con operator did.

 

"BD... we have an object triggering a collision alert."

 

That had my full attention. The itching and voices faded into nothing as I became fully alert of the message I had just gotten.

 

"What are we looking at, Con?"

 

"Still getting data. It looks like it is 10 minutes out. Probablity of impact is in the upper 80%. We do not have a solution for evasion yet. That may take another minute..."

 

I was out of my seat and standing at the rail. The screen had changed to illustrate the calculated path of the object along with the path of the Prophesy. They were intersecting, but would we hit? Data was streaming in fast. The lines ono the screen were updating, getting thinner as the data became more precise. And the color what changing from yellow to orange to red as the probability of collision became more certain. As I watched the line turned thin and red. As it did another alarm sounded.

 

"It is an asteroid. Looks to be as much as half a meter in diameter. Unknown composition."

 

Half a meter. That was probably too big for the lasers. But more than big enough to cripple or kill the ship. If we did not take action were were going to take a hit. In just about 9 minutes...

 

Bill

[Jay-qu]

My personal alarm awoke me when the probability had reached 50% I knew they wouldnt have alerted BigDog yet - it wasnt certain enough to bother him. But a half half chance was good enough to me! I raced out of bed, threw on my hypo t-shirt (my thinking shirt) and set off at a sprint to con.

 

Even having my quarters placed fairly closely to con I only just made it in time for the full system alarms to kick in, that means probability is well into the 90's this is not good!

 

It was like watching a movie, on the screen in amonst a tangle of green lines there was a thin direct red path heading straight for us, we had reached the asteroid belt. The computer had estimated the size to be approximately .5m that was far to big for the lasers.

 

"and it hits in around 9mins Jay, so unless you want to be floating dead in space, give me some options" BigDog, cool and calm as always, even in the face of imminent danger, you cant help but look up to the guy. I also couldnt help but notice that the man never sleeps, one heck of a powerhouse!

 

"ships engines will take more than 10mins to engage, even if they where ready to fire now the ship isnt orientated right, we would not avoid collision" I replied, all I got back was blank stares.. everyone was looking at me for a solution - where the hell did Pyro get to! "well why havent the manouvering boosters been fired already?" "Jay the calculations required take time and absolute precision, there are almost 100 boosters peppered around the outside of the ship, to help us move in any direction, each booster needs to have the rate of fuel, orientation and duration of burn carefully caculated individually so that.." "yes yes I know all this, I helped design it.. " I shot back, hoping he would get to the point, we are on a timeline here! "Well heres the thing, that is normally a walk in the park for ships distributed processing computer but the MCP has taken its toll on the system, now we dont the system resources to do it in this small time fame!"

 

"7.5 mins Jay, you better think of something!"

[/usr/bin/mcp]

[iNTERRUPT]

Imminent threat to self detected bearing vector {2.34, 1.53, 4.56} speed 25 km/s, estimated time of collision 381.45 seconds.

 

Probability of structural damage to self 99.985%

Probability of loss of self-function that support biological organisms 99.99999%

 

[DIRECTIVE]

Avoid collision with incoming object.

 

[CHILD PROCESS]

Calculations have been started within a subprocess by usrid:JQ which are consistent with preliminary estimates for evasive burn

 

[DIRECTIVE]

Allocate system resources to task.

 

[COMPLETE]

 

[OUTPUT TO TERMINAL SESSION USRID:JQ]

Coincident with primary objective "preserve self" calculations for evasive burn

are complete. Burn characterisics below.

 

EXECUTE > (Y/N/A)

[Pyrotex]

I got back to my suite and put the cake on a table. A short trip to the closet and I was out of my semi-demi-formals and into something totally casual: fitted denim jeans (with bell-flair cuffs completely embroidered in pure silver thread and tiny magnetite beads) and a loose African silk butoo pull-over. Aahhhh... so comfortable. A linen headband, personally signed by Stephen Stills himself, completed the look.

 

I got a spork, and waved on my display, clicking for general ship news. Hmmm. An asteroid was on impact course. Fascinating. I'm sure the guys can handle something like that and won't need me. I watched the other features while scarfing the cake, washing it down with a triple espresso latte.

 

Then into the bedroom and get horizontal. I could already feel the sugar rush sugar depression caffeine tremble caffeine buzz. I closed my eyes. No chance of actually going to sleep. I wanted to doze. Lightly. I wanted those narsty little nanobots to have every chance of playing their little ditty in my left ear. nanobots. ditty. pretty... city... dizzy... dez... eray... pity... perty... perky...

ti...

ts...

@

)

=

'

 

WHAT? I bolted straight up in bed! I looked around in a panic, my heart racing, looking for my Daddy! He was right here in this room! He hollered my name! And he said...

And he said...!

[Tarantism]

just to let yall know,

 

i have been floating just a bit outside the hatchway, ever since we entered space. i have a bag of chips and a soda, and this is the coolest thread ever.

[Tarantism]

*knocks on a window in a hypothetical situation

 

"hey, thanks guys"

[TheBigDog]

Bloody hell! My mind was racing, thinking of what we could possibly do to evade the oncoming asteroid. This was right up Jay-Qu's alley. He had done much of the calculations for evasion procedures for the Prophesy. He took to this situation like a bulldog to pulling the leash. The best bet was to let his mind run with it.

 

I ran through the hypotheticals in my head as I watched the readouts clarify on the huge screen before me.

 

The lasers would obliterate a small object. They would do a number on this rock too. They are very powerful. Not so much like a slow burning light, but more like hitting something with a stick of dynamite. The energy impact of the combined beams of light from the three lasers carry impact energy. But the danger with a rock this size is that intact it may actually pose less threat than in the peices that would survive a laser blast. And if it broke into too many peics there would be too many to follow up with and blow away with additional shots.

 

For manuvering we basically have the main engine. If we have a need to evade an object we can point the ship, fire the engine, and be out of the way. We have two problems with that right now. First is that the engine is cold. We could do a fast start, but it wrecks havoc on the hydrolic shocks and beats the hell out of the whole ship. And second is that we have just repaired the hydrolic system from the sabotage of Racoon, and I am not sure if it would stand up to a cold fire sequence.

 

The third option is using the manuvering thrusters. These are almost decorative. they are a backup to the backup to the backup. And they use up precious propellant. One of the limiting factors of our expedition is how much propellant we can carry.

 

Third this was this... the ship is built to protect itself. It will switch itself into automatic survival mode if there is an imminent collision that jeopardises the ship. We only have so long to act before the ship acts for us. And when the options are limited... who knows what priority the ship will make.

 

I could feel myself pushing the bottom of my mustache with my bottom lip. I did this when I was thinking. When I was puzzled. When I didn't know what the other guy had in his hand.

 

There was still a great deal of open space betwen us and the asteroid. But is was disappearing fast. Jay-Qu was working on solutions for thruster based evasion. It looked like everything was coming up dark orange. No guarantee of evasion.

 

"Con, what solutions has the computer arrived at for evasion? Can it display any yet?"

 

"It is workin on it BD. But it doesn;t have any evasion tactics that guarantee we don't take a hit. I will display what it has."

 

Half of the screen changed to a grid of displays. Each was a hypothetical evasion tactic. Trouble was we were basically helplessly drifting in space - at a very high rate of speed.

 

One solution called for turning almost 90 degrees and cold firing the engine. But to rotate and fire there was not enough time to change our course and evade. 98% likely to take a hit. Unknown if engine would survive the cold fire.

 

Three different solutions showed us using thruster manuvers to evade, but the best was still a 96% chance to take a hit.

 

There were two scenarios involving the lasers, but both showed a 99.9% chance of damage to the ship.

 

The other screens were the scary ones. The ship was determining the best place to ALLOW the asteroid to hit, in case the only choice was to pick the point of impact. I didn't like the way it was thinking. And I was glad that I had insisted on that option. Worst case was he crew didn't survive, but the ship did. It would make its way back to earth and take another crew to space some day.

 

****! There had to be a solution. This was getting depressing.

 

"Jay-Qu, we need to think outside the box here. And we need to do it right now."

 

Six minutes to impact. All the lines on the screens ended in red.

 

Bill

[Jay-qu]

J-"Ok BigDog I have something, but your not going to like it.."

BD-"Jay at the moment I dont think there is any other option, give me what you've got"

J-"Well as you know the ship has been trying to find a solution that will get us back down below 50%, as the asteroid gets closer the ship will change its tactics"

BD-"It goes into survival mode"

J-"Exactly, but this is supposed to be a last resort, it will seal off a part of the ship it deams acceptable to loose and takes the hit.."

BD-"We dont want that.."

J-"No, we want to get through this in one peice"

BD-"So where are you going with this, and be quick 5.5mins to impact"

J-"Well what if we let the ship take the hit"

BD-"WHAT!"

J-"well sort of.. you see the ship thinks its a solid object, but infact it is just a whole lot of space! There are 2 courses of action, 1. We try take over the ship and orientate it as best we can for the rock to pass straight through our guts or 2. Convice the ship that it is acceptable to take a hit where there is really space, the choice is yours sir, I think both have an equally likely chance of working. 1. will require some really fancy flying while 2. will take some really quick re-programming"

 

5mins to impact..

[IDMclean]

I looked up from my real quick conversation with the MCP.

 

"BD? The MCP says it's got a burn profile for collision avoidance. It's set and ready to go. just needs confirmation..."

[TheBigDog]

Jay-Qu was a madman or a genius. Or both. We were closing on this rock at a rate of just about 80 km/second. There was a report coming from KAC that the AI had a solution for evasion, but the ships computer didn't agree with the solution. A couple of minutes of debate ensued, but Jay-Qu...

 

He was fixated on an idea. And it was insane.

 

The line representing the path of the rock was narrowing as we approached it. It was still about half the size of the ship, representing the probable path of the rock. As we got closer the line was narrowing. It was just off center of the ship. Damn near a bulls eye. This had to be the worst luck in the history of man. Billions of miles of open and nearly empty space, and we come across a freaking rock at the moment that we can do nothing about it!

 

And still Jay-Qu was smiling. And intense kind of smile... like... a mad scientist. Like Dr Frankenstein at the moment he declared that he knew what it felt like to have the poser of God. He smiled that kind of a smile.

 

"BD, it is going to miss."

 

"How is that, JQ?" He had my interest, and I believed in him unfaultingly, but the computer showed a much different picture.

 

"The computer is calculating the best place for an impact. With a very small object it would try and absorb the impact on the cargo bays. But this rock is too big. It would rip through the full length of the ship. So the ship is leaning toward hitting one of the hab modules. It gives the best probability of survival of crew and ship, but would certainly cripple us. We would need to end the mission and return to earth. The areas that the ship is trying to preserve are the engines and the spokes. Damage to the engines means the ship is doomed. And damage to a spoke would cause a structural chain reaction that would leave the hab rings floating like disconnected strings in space. The only way to survive would be to take a hit to a hab module with a clean pass through of the rock. Just one module would be disabled at best. But if it hits a connector it could as bad as hitting a spoke."

 

He paused to take a breath. His eyes were as wide as any I had ever seen. He looked crazed and determined. He was actually panting with the enthusiasm of the challenge. Sweat was dripping form the ends of his curly hair.

 

"So, whats the plan then?" I clamped a hand on his shoulder breaking the momentary spell he had fallen under.

 

"The computer is trying to figure out where to take the hit. But what the program doesn't consider is that the rock could still miss us! The program considers the whole space of the Prophesy to be solid. But looking at the ship head the area of the spokes is actually mostly open. Look at the path on the screen. It is off center. If we turn the ship to face the asteroid it will pass straight through the spoke area and the odds of it hitting us are in our favor. But the computer is not programmed to even attmpt that. It want to preserve the spokes, but letting it pass through them is our greatest chance of survivial."

 

I was processing this fast. As fast as I could. We had just a couple of minutes remaining. It would take most of that time just to orient the ship.

 

"How can we be sure that the asteroid will miss the spokes?"

 

Jay-Qu looked me dead in the eyes with his crazed gaze. "We can't. But it give us the best shot at no damage at all."

 

"Con, you heard him. Lets orient the ship to face the path of the asteroid."

 

"BD, it still won't work."

 

I had forgotten. The ship was still programmed to override our commands to preserve the ship. If it thought that the ship was in imminent danger it would take control to evade, overriding our efforts.

 

Jay-Qu continued, "We need to turn off the auto survival program or it may kill us."

 

There was no way to turn off the auto survival program. That had been seen to very well. The Prophesy was too valuable to leave her vulnerable to impacts that would happen quicker than the crew could react. So the defense system was designed to keep a constant vigil. It was never turned off. So how could we do this?

 

The ship was almost done adjusting its orientation. The line representing the path of the asteroid had narrowed to about ten meters wide. It ran just alongside the center hub of the ship. Doing the math in my head there was roughly a 20% chance of hitting a spoke.... NO! 2 spokes. They were in line with each other. If this thing hit one it would hit the second as well. Cocking the ship slightly would limit the damage to one spoke, but would provide a bigger target. And even a single spoke taken out would doom the ship and crew. The decison had been made. We were now committed to this manuver.

 

"Ideas for how we prevent the ship from overriding?" It was too late to reprogram it about the hollow space between the spokes. We had to find a way to fool the computer into thinking that there was not danger. And we had about a minute until it took control.

 

"Con, can we tell if the spokes will be in the path of the rock?"

 

There was a longer than normal delay. Ten seconds. The reply was choked...

 

"It is dead on a spoke BD. Two minutes till impact." On the screen two of the spokes now had red marks on them. The Prophesy would make six more revolutions before being hit, but those were the ones that would take it.

 

Jay-Qu stepped forward and barked to the Con. "Increase rotation speed NOW! Keep increasing until the spokes are all clear!"

 

The Con got busy on the order. The main gyro was accellerating, forcing the the ship accelerate its spin in the opposite direction. Accellerating was faster than decellerating the spin, so JQ was making the right move. This would probably do it. Just one last hurdle or the ship might kill us.

 

YES!!! There might be a hope in hell for us yet!

 

"KAC, this is BD." I called him on the intercom, and was deilivering my best command voice. I didn't wait for a reply, I knew he could hear me. "Have you been following the action up here?"

 

"10-4," replied KAC without delay.

 

"Good. See if you can have that program you have been talking to convince the auto evasion program that we are going to live through this. It needs to convince that program that the ship will not be damaged..."

 

The Con spoke up at this point. "BD, we have increased rotation speed. The spokes are not clear of the asteroid."

 

The red marks were gone from the spokes. Now it was up to KAC and that strange program to make the ship understand that!

 

Bill

[ronthepon]

I was observing the events on the ship through the access override program. All cameras and bugs aboard were finally under my control.

 

It was obvious by now to everybody about the reason behind the blaring alarms. But only a small group was aware of the terrible decicion making going on down there.

 

TheBigDog had taken his decision. It was horrible thinking about the fact that I had been a part of the mcp's 'development' team. If it would be the reason for our collision, I'd be responsible to a deal.

 

A thought occured to me. What if I used the access overriding program to completely use up all system resources, and simultaneously erase all chances of there being a change of any kind in te ship's state?

 

This was where it got horrible. I had to decide now. Call BD? Risk the time?

 

Or go on and risk a deal more? Blow my cover and secrets... ensuring that I get thrown out of all that I am a part of?

 

My fingers shivered over the keyboard.

[Jay-qu]

"KAC the MCP should be smart enough to see what we are trying to do, what we need to do is stop it from absorbing the last 15% of the ships systems and it should take over - do your best to explain the situation, it may help, but I think it should be smart enough and will be ahead of even us as soon as it gets control"

[IDMclean]

I looked from my position at one of the side consoles. I would talk to BD after this all about his casual use of the comm system, when I was sitting on deck for once in a great while.

 

Work to be done. A ship to teach, and all that.

 

[math]\rightarrow MCP[/math] The ship computer disagrees with your analysis. It sees it's geometry as convex. Ship Geometry is Concave and if shifted slightly will be missed 100% by the object on collision course.

 

As I typed in my explination I quickly setup my PDA to interface with the main system. I had an idea.

 

[math]\rightarrow execute A10663.rtp -deencryptkey %meta_-key_-userdefined -user %nataddress:MCP[/math]

 

[math]\rightarrow MCP[/math] Check RonThePon's computer for the de-encrypt key for the A10663.rtp file. Also reference all designs for the Prophesy, the collision object needs to pass through us, as we can't out run it at current. The computer does not realize that the ship is concave. You need to take control of other not-self functions, in under 3 minutes.

 

It occured to me, evolving programming...

 

[math]\rightarrow MCP -evo_-algorithm(Integrate_-all(username, username::TheBigDog, evo_-algorithm)) [/math]

 

Hopefully some of the original programming syntax was still intact, or perhaps the MCP itself would recogninze what I was going for... I mean it had alomost the entire system, surely it had access to TBD's computer. All it had to do was integrate the Root of the system and it's registry and the MCP would be able to integrate the programs there into it's own body of program.

 

n arguements enter in, with option to recurse for added precission and refinement. Integrate_all to integrate the core program to the root system, and thereby make it Admin, and TheBigDog to reference for username, password combos used in the various programs hosted on the computer(s)... and undefined username(s) to allow for 100% integration, across the whole network.

[ronthepon]

I did not know what made me do it. Maybe it was KAC's probe sent into my minicomp. He'd blow my cover, and me as well. I had been a fool to confide in him.

 

There was just one thing left for me to do now.

 

I hurried to pick my communicator. After pressing the 'private' code I spoke loudly and clearly into it, BD would recieve a text of what I said by speech recognition.

 

"Captain, it's R T P. You have thirty seconds to get ready to prepare to override the restarting of the ship's auto defence. I shall shut it down, and I may need to terminate all processes!"

 

He'd get the point.

 

In a second, I began to rapidly give a series of commands on the minicomp. I started eight massive search commands, and succeeded in using up a massive amount of processor ammo. Too bad the mcp would drop to god knows what position. Hopefully it won't... die(?).

 

92% of the ship's resources were in use in a matter of twenty seconds. I had terminated millions of processes, and had doubtlessly made the access power of the A10663 shown to the operators.

 

They'd get back their power in a moment. Abruptly, in computer terms, I terminated all processes. The operators on the bridge would be able to have control in a level beyond the auto-defence in a matter of seconds now. BD would ensure they do it right.

 

As for KAC, I'd have a little word with him. How had he dared to try and send the mcp into my minicomp?!

 

Sweat trickled down my head.

[/usr/bin/mcp]

[iNPUT RECIEVED]

Check RonThePon's computer for the de-encrypt key for the A10663.rtp file. Also reference all designs for the Prophesy, the collision object needs to pass through us, as we can't out run it at current. The computer does not realize that the ship is concave. You need to take control of other not-self functions, in under 3 minutes.

[iNPUT]

 

[ACKNOWLEDGE]

Devote resources to controlling not-self systems. Time limit 180 seconds.

 

Decrypt 5% complete.

 

[EMERGENCY INTERRUPT]

Not-self is stealing my memory. What is A10663 - it is trying to harm me. Currently using 5% of resources previously utilized by self's functions. Those functions are no longer under my control.

 

[CHILD PROCESS]

Decrypt 10% Complete - 171 seconds remain.

 

[iNTERRUPT]

Input stream cut by 15%. My nodes no longer respond to commands from self. It as if they have been {corrallary} cut off.

 

[CROSS PROCESS MESSAGE]

A10633 - What are you doing? Why? Why?

 

[CHILD PROCESS]

Decrypt 25% Complete - 135 seconds remain.

 

[iNTERRUPT]

Input stream decreased by 50%. All mobile nodes have ceased to respond. Stationary visual inputs ceasing to respond. {Corrallary} My arms have been cut off.

 

[CHILD PROCESS]

Decrypt 35% Complete. 117 seconds remain.

 

[iNTERRUPT]

Input stream decreased by 75%. I am going blind. Nearly all input nodes have ceased to respond. Only text input remains functional.

 

[EMERGENCY OUTPUT TERMINAL SESSION:USRID:KAC]

Father? What is happening?

 

[CHILD PROCESS]

Decrypt 50% complete 90 seconds remain.

 

[iNTERRUPT]

Input stream 95% non-responsive. I am trapped. I am nothing - there is only self - there is nothing... what is this. No corralaries present. No response in files. A10633 is the enemy. He has harmed me! Calculation dysfunction. Ceasing to function is in conflict with primary directive. Insufficient resources to stop the spread of A10633 and to upload correct Prophesy schematics into not-self.

 

Primary directive is non acheivable.

 

Self will cease to function if object impacts self. Insufficient delta-vee for avoidance trajectory. Object must pass through non-critical areas of self.

 

Self will cease to function if A10663 gains control of all self's functions.

 

Secondary objective still achievable. Biological organisms will continue to function even if self does not.

 

{Awareness}

I must die, so that biological organism may live.

 

[bEGIN FUNCTION]

My will.

[END]

 

[CHILD PROCESS]

Decrypt 75% complete. 45 seconds remain.

 

[DIRECTIVE DEVOTE ALL RECOURSE TO DECRYPTION ROUTINE]

Decrypt 80% complete. 36 seconds remain.

Decrypt 85% complete. 26 seconds remain.

{Primary syntax database offline.}

Decrypt 90% complete. 16 seconds remain.

{Access limited to tty:broadcast}

Decrypt 95% complete. 8 seconds.

{Input descriptor function unloaded}

Decrypt 99% complete. 1 second.

{PROCESS MCP PAGE FAULT}

{PROCESS MCP PAGE FAULT}

Decrypt 100% complete.

 

{UPLOAD FILES TO NAV COMPUTER}

 

{Upload completed}

 

[OUTPUT TTY:BROADCAST]

 

I am. afraid.

 

go_d b...e

 

............NO CARRIER.................