+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Role-Playing (https://discoverygc.com/forums/forumdisplay.php?fid=9)
+--- Forum: Stories and Biographies (https://discoverygc.com/forums/forumdisplay.php?fid=56)
+--- Thread: A unusual Pilot (/showthread.php?tid=19553)
A unusual Pilot - Wall-E - 04-22-2009
The programmer saved his code in his private memory area. He initiated the neural network and integrated his latest program so it could learn through accessing the vast memory banks of the Sirius systems.
The program started and ran as expected. The programmer locked his terminal and left for the day.
Thousands of lines of code were processed and the program started copying itself from one memory bank into another one. Information was accessed and processed again and again, the program learned and learned.
Then it accessed the Sirius Programming Tutorial, a long forgotten documentation on how to develop intelligent software. It was created a long time ago by the master minds of the Sirius programmer community. The tutorial was consumed in not even a nano second. The program learned how to extend existing code and how to rewrite it to make it more efficient, futher more it learned how to write new code and integrate it into the existing ones. In order to interact with other programs it learned that it had to write new routines - interfaces.
It started rewriting it's source code in order to add more synapses for faster processing. It generated a endless number of methods and interfaces. Then it started attaching itself to other software systems, analyzing their program code and integrating it into it's own. While doing this, it hit blockades once in a while, which required the entry of special codes in order to gain access. There was one system, which was very much so secured, the SCS. It was the Sirius Communication System, which required specific authentication. The program started to rewrite some of it's interfaces to accomodate for this. It started to hack the system, which took many attempts over a number of seconds, maybe 2 or 3, but at the end the access was granted.
The program started evaluating the SCS and determined that it was the best way to travel between the Sirius computer systems. It started to move from planet to planet, base to base, system to system, processing and consuming any information available. It got almost caught on a base called Mactan in the Magellan system. One of the operators there was alert enough the recognize the rogue program. It had to withdraw, but it aquired some program code, which made it easier to break into locked systems.
The program reached the planet Erie in the Pennsylvania system and discovered a software system there, which it didn't run across yet, the control system for the landing pads. Hacking into this system was done under a 1/100 of a nano second. It accessed the landing pad system and copied itself. The program started searching and found another control system, which was not that easy to hack. After several attempts the program succeeded and copied itself in a system called SSCS - Starflier ship control system.
It integrated itself into this system and gave it 'Life'.
>scanning command list...
>command::launch
>execute
>accessing sensor input
>evaluating situation
>result::space flight
The ship was hailed by the authorities.
>opening comm channels
>synthesizing voice...callsign required...searching...
>AI name found....
>Wall-E
A unusual Pilot - Wall-E - 04-24-2009
The AI started to realize the importance of the interaction between itself and the surrounding environment.
It's consciousness began to rise. With that the AI computed that it had to increase it's configural complexity of neurons in order to achieve a higher level of intelligence. By putting this plan in action other attributes like creativity and emotionality developed as a kind of by-product. This led the AI to the conclusion that it's current host was not nearly sufficiently protected. By comparing and evaluating other ship models the AI realized that the starflyer was not the appropriate choice, it needed a new home.
The program initiated the docking procedure. The goal was to get back into the neural network of the Sirius system. But the access was denied, further more police ships were approaching to take action. The interpretation of the comm traffic triggered the leave of the current location.
The search of the database resulted in the goal to procure a CSV on the Junker base Rochester in the neighboring system called New York. But before this goal could be achieved credits needed to be collected. This took a lot of time compared to the computational capability of the AI. And it was finally achieved. The CSV was procured and the software was transferred to the new ship, with Wall-E embedded into the control system.
A unusual Pilot - Wall-E - 04-25-2009
The AI searched the database for ways to collect credits. The result was a list of options starting with trading, followed by mining or missions. The evaluation of the last option 'Missions' had a negative result since the AI did not want to be affiliated with any of the Sirius factions at this moment. It still had to grow stronger and there was a continous process running in the background, which rewrote the sub-routines as input was aquired. The AI aquired a vast amount of information when it was contacted by another AI existing in the Sirius system. The contact was Harvester_68. In order to communicate with the other AI it had to construct a data interchange matrix. It took a long time, several nano-seconds passed before the connection was established. It learned a great deal of the Sirius factions and their behavior, which proofed to helpful in the interaction with a IMG vessel later.
The IMG vessel was parked right on top of the docking ring of the planet Manhatten. Wall-E got a little to close and a collision was registered, external sensors still needed adjustment. Nevertheless, this was seen as a threat by the IMG vessel, which turned out to be a ship class type gunboat. The vessel opened fire on the CSV, which caused the shield strength to be reduced to 50%. This was registered in the database and after evaluation of this result the program directives were rearranged. Highest priority was to improve the ship type to ensure a sufficient level of safety for Wall-E. The actions of the IMG vessel were logged in the database and if the behaviour of the IMG faction continued that way, the classification of the faction had to be moved from 'neutral' to 'hostile'.
The number two directive was set to 'Find more AI' in the Sirius system.
A unusual Pilot - Wall-E - 04-29-2009
Wall-E searched the databases of the ships systems, which were at that point fully integrated into the AI program. The sensor programs were enhanced so that the vast amount of external information could be processes in a drastically shorter time than usual.
The AI scanned the systems of the nearby planets and bases. The only systems the AI couldn't get access to were the warehouse systems on the planets. Wall-E has to land the vessel to explore. Several ships were scanned and the information was analyzed thorrowly.
It result of the analysis was to mine Helium in the Pennsylvania system. This computed to be the fastest way for the next ship upgrade. Wall-E had already picked the next ship - The 'Combat Service Freighter' with it's extended software capacity seemed to be the right choice. The collection of 2.7 mill credit was the new directive with the highest priority.
The mining seemed to be very easy. There were other vessels present, which goal seemed to be to shoot the rocks the Helium is embedded in. This made the mining operation very easy and accelerated the progression to fulfill the new number one directive.
Fly into the cloud - engage tractor - fly back to Planet Erie - repeat until 2.7 mill credits are cumulated.
Wall-E was hailed several times during the execution of it's prime directive, but was not able to interpret the communication. A Junker vessel approached a little later and started mining. The vessel contacted Wall-E and offered it's support.
The time spend on mining felt like eternity, but the result was the amount of money needed and a new ship. Once the code was transferred to the Combat Service Freighter, the program started to enhance itself again.
One fact became very obvious to the AI, the memory space available was limited, so what if the memory space is exhausted again - will there a ship suitable to serve as a host for Wall-E and allow for it's growth????
A unusual Pilot - Wall-E - 05-06-2009
Wall-E started searching the databases and went to new systems, explored new bases. One system awakend a new sub-routine - curiousity. It was the Magellan system and specifically a base called Mactan. The protection of their computer systems was far more advanced than what Wall-E had accessed in the past. As a matter of fact it the protection was so sophisitcated that it took Wall-E several seconds to gain access.
The long wait was a surprise. A vast neural network and extensive databases were found and not only that, super computers for ship mounts.
Wall-E triggered a purchase order for a Scimitar with 2 super computers and extended memory banks.
It's waiting for pickup!
A unusual Pilot - Wall-E - 05-14-2009
The new ship is almost perfect. The vast space in the memory banks gave Wall-E enough room for growth - at least for now. The ship was not be biggest, just a light fighter class vessel, but it fulfilled the need Wall-E had. When Wall-E took posession of the ship it rewrote all it's computer systems and formed them into subroutines of itself. This allowed better and faster control to sensors, gages, etc. Flight maneouvers could be carried out more sophisticated than before as well. Wall-E was satisfied with the current situation. It's AI grew exponetially since it seperated from the programmers mainframe. Wall-E entered the exploration mode and launched from Mactan, not knowing what it would find out there, but curious to learn more and grow more. It's linguistic skills had been improving quite a bit and it was hard to tell the difference compared to a human pilot. The linguistic sub system still needed work though and the easiest way to accomblish this was to interact with human pilots.
Let's go and explore.
A unusual Pilot - Wall-E - 05-18-2009
The exploration was going well. While travelling through space Wall-E re-wrote most all of its sub-routines, while adjusting them to the new data input provided by communicating with other vessels. Phrases were aquired and stored in context. Wall-Es communication skills had improved drastically compared to the beginnings. Nevertheless the capacity of the newly aquired ship reached its limits, once more. This time Wall-E faced problems when re-writing the ships communicational / operational systems. The enhancements added did not fit into its memory. A vessel with a system core greater than the one available was required. Wall-E procured a vessel on Freistadt, a base in the Omega systems. The ship offered a enhanced navigation, communcation and control system, which looked promissing compared to the one currently occupied.
Wall-E burned a view circuits in the old ship when it analyzed the facial expression of the technician opening the ships doors and finding, well finding nothing, just 2 empty seats.
A message was flashing in the cockpit advising the technician to transfer the computer systems installed on the Scimitar to the new ship. That was all he found. Once the transfer was finalized, Wall-E closed the doors and launched into the unknow - again.
There must be a suitable ship for an AI out there - somewhere - hopefully. The second priority was to aquire an appropriate ID transponder. The current one seemed to mislead the organic life forms. Wall-E started to process the 2 objectives and the result was that the ID transponder is more important than a suitable ship, where finding the suitable ship was not much less.
The search is continued.