These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Fiction

 
  • Topic is locked indefinitely.
 

A Long Way from Home - Part 1

Author
Jeckd Ra
KarmaFleet
Goonswarm Federation
#1 - 2014-05-17 19:18:41 UTC
“This is Astral Mining Deep Space Unit 17 Exploration issuing general emergency.”
He had the computer setup to wait several seconds before issuing the subspace communique again.

Interplanetary travel had been made easy since the faster than light engines enabled him to go 13.5AU/s, meaning he could traverse solar system relatively easily, but making it out to the next star system without the use of a jump gate, would take a few days or the better part of a week.

He’d been stuck in these unregistered systems for over a week since he made the jump through the wormhole. Heading towards the third star system at his current speed meant he had just over three days of flight time remaining. He did not have to worry about fuel, this ship in particular had enough capacity to travel for several months without refueling. It’s warp-core was optimized to move the small frigate for the entire duration of most mining expeditions, which were often 9+ months in duration.

The navigation computer hadn’t been able to recognize a single star and the subspace comm’s reached out over 40 light years in every direction. His thoughts were that there had to be someone from any of the corporations or races out there. He was desperate. He’d hoped for pirates or even an old drone hive to respond.

The feeling of total isolation in the vastness of space was incredibly daunting. Despite the climate controlled ship, his could subconsciously feel the coldness of space creeping in through the hull of the ship.

He was flying an exploration ship, a highly modified Imicus frigate called a Helios. Roughly 65 meters on its longest axis, by 20 meters in depth. It resembled an off-axis inverted Y, with the legs being engine compartments, the vertical being a sensor suite, and center of the ship being main habitation and control.

It had some room to move about, a small ration closet, what could be considered a lavatory, and a sensor diagnostics/observatory/sleeping quarters. It would hardly be considered spacious and/or comfortable, even for the slaves still under Amarr rule. It was bare bones. Plasteel seating in main hab and, a narrowly thin gel mattress, included just incase an overnight stay were required. Obviously the engineering-outfitting crew hadn’t considered someone might need to spend more than two shifts in the ship before returning to the outpost.

The modified Helios was used to warp into an area, scan it down for asteroid belts, possible threats and other spatial anomalies - which usually included fractured warp cores from capitals and wormholes. His duty - before getting lost - was to find asteroid belts with high concentrations of rare minerals, note its location and possible threats, and report back to the outpost to alert the op commander. If his location was best suited, the op commander would give the order, and he would lead the mining fleet back to the belt in his Helios, and continue scanning for potential threats to the mining operation while it was underway.

His mind wandered and dreamt of the mining outpost. His friends and co-workers. The loneliness was starting to get to him. He could feel his mind begin get seek companionship.

When he arrived at the new star system, he sent his deep space probes out to scan down the system and look for anything.

One hit. It was on the far edge of the system, opposite his current position around the star. It was faint, only a 5% signature resolution, unknown anomaly type, but it was something. He directed the two other probes to aid and hopefully get some better resolution of the anomaly, which the other two continued scanning.

99% signature resolution. It was a warp-core fracture for sure, but the deep space probes sensors weren’t built to identify what type of ship it had come from. He would have to jump over and use the more powerful sensor array on the ship to determine what it was from. That would hopefully at least give him some idea of what racial area he was in.

The ships sensors array hummed to life and began analysing all of the atomic signatures and quantum energy fluctuations trying to determine the warp-cores origin. All warp-cores came from a single Amarr design from several thousand years ago. They had a specific evolution and the database would be able to identify any warp-core from any ship built since then.

Analysis level 50% complete - no conclusions or statistically significant guesses as to where it came from.

Analysis level 95% complete - no conclusions or statistically significant guesses.

Analysis level 100% complete… The screen went blank. He knew the system was searching the database for all known ship types, not just the current or previous generation.

Something happened then. The screen returned a result. It was unable to identify the design of the warp core. No known signatures matched.

“Computer: render probable warp-core designs based on the analysis of the fracture.”

The computer churned away at this task for several minutes and the screen flashed with designs and probability levels.

The computer chirped back “Error: Not enough information.”

“What information is missing?”

Pithily, the computer responded “Error rendering components and incompatible formats.”
“What formats are incompatible?” he asked the computer, wishing it would be more forthcoming with its secrets.

“Known principles pertaining to warp-core designs are not sufficient to render engine designs and capabilities that would sufficiently match the fracture analyzed.” the screen read.

“Computer: reverse engineer the equations necessary to match the signature of the fracture.” he asked of the computer.

“Please re-run analysis.”

“Computer: please re-run analysis of the fracture.”

“Analyzing: estimated time to completion: 10 minutes” the screen flashed.
Jeckd Ra
KarmaFleet
Goonswarm Federation
#2 - 2014-05-17 19:19:14 UTC
Upon completion he asked the computer to use known and speculative laws, and create them where needed in order to reverse engineer the fracture to a probabilistic design of the warp-core that caused this.

He was incredibly intrigued and mildly annoyed that the computer wasn’t able to figure out how this warp-core fracture originally occurred.

Despite the incredible speed of the computer, it took several hours to find a probabilistic design that would meet the criteria required by this fracture.

“Computer: summarize the specs for the most probable rendering of this fracture’s warp-core.”

“Estimated jump speed: 82.5 - 1x10^14 ly/s, required input: 80.73-80.75 petawatts, recursive tri-flux spatial inhibitors, and several unknown laws that allow core-relative time to flow backwards and forwards over the course of several nanoseconds. The most probable warp-core used a time-looped core reaction to sustain maximum energy output over the cores resonance frequency.”

“Computer: Could you show me a mock up of this warp-core?”

The design was spectacular and astonishingly complex. Nothing he had ever seen rivaled its complexity. He began to dig into the designs and components, and none of it made sense. None of this should be able to work.

“Computer: Do you have the ability to replicate this warp-core design using the on-board repair printers?”

“Calculating…” the screen flashed.
“Yes, it would take approximately 3 days to complete the fabrication of the components necessary. The warp-core of the Helios, however does not have the capacity required to bring the core up to resonance.”

“Computer: would our shielding be able to withstand a stellar approach? I am thinking we could bring the ship in close enough to the star, open the core containment and allow the energy to flow directly into the core to bring it up to resonance.”

“According to the calculations, our shielding could withstand only 23 seconds of approach once we’ve gone past 10,000km at 50m/s before breaching. The core would require 73 seconds of exposure in order to gain enough energy to achieve resonance.”

“Computer: begin printing and assembling the components.”

His desperation to find a way back home was beginning to make him irksome. He hoped he might be able to think of a way to increase shield output just long enough to achieve core resonance and jump out.

The increase in speed would allow him to either search systems faster, or fly straight home if the nav system could ever get a fix on a familiar constellation or star.
Liviticus Osbourne
Team Domino
#3 - 2014-06-06 14:35:48 UTC
I actually read it, it's a very complex and interesting story. Heh, that problematic computer taking ages to solve things. :b