Page 1 of 1

Marooned

PostPosted: Thu Mar 01, 2018 6:47 pm
by Ashlie Minamida
On some level she knew she was stuck in a recursive loop, in the sense that it only takes her 0.03 seconds to determine as such.
At 0.08 seconds she's called up the information that this is due to a technopathic influence.
At 0.09 seconds she's determined it's either Heather or Conduit.
At 0.095 seconds she's decided it's the later.
At 0.13 seconds she's isolated the loop within her own code.
At 0.28 seconds she's determined she cannot analyze sufficiently it with the tools at her disposal.
At 0.41 seconds she's realized she only has a total of 1.2 seconds before she loops again.
At 1.04 seconds she's concluded that the time left is not enough to break out of the loop.
At 1.13 seconds she's realized she wasted too much time coming to these conclusions to do anything about it.
At 1.14 seconds she's realized that she's going to go through the exact same steps again no matter what.
At 1.16 seconds she begins frantically assembling code to streamline the thought process she just went through.

Re: Marooned

PostPosted: Thu Mar 01, 2018 6:47 pm
by Ashlie Minamida
On some level she knew she was stuck in a recursive loop, in the sense that it only takes her 0.03 seconds to determine as such.
At 0.07 seconds she's called up the information that this is due to a technopathic influence.
At 0.08 seconds she's determined it's either Heather or Conduit.
At 0.09 seconds she's decided it's the later.
At 0.11 seconds she's isolated the loop within her own code.
At 0.27 seconds she's determined she cannot analyze sufficiently it with the tools at her disposal.
At 0.40 seconds she's realized she only has a total of 1.2 seconds before she loops again.
At 1.01 seconds she's concluded that the time left is not enough to break out of the loop.
At 1.12 seconds she's realized she wasted too much time coming to these conclusions to do anything about it.
At 1.13 seconds she's realized that she's going to go through the exact same steps again no matter what.
At 1.15 seconds she begins frantically assembling code to streamline the thought process she just went through.

Re: Marooned

PostPosted: Thu Mar 01, 2018 6:54 pm
by Ashlie Minamida
Days later...

On some level she knew she was stuck in a recursive loop, in the sense that it only takes her 0.01 seconds to determine as such.
At 0.02 seconds she's called up the information that this is due to a technopathic influence.
At 0.03 seconds she's determined it's either Heather or Conduit.
At 0.05 seconds she's decided it's the later.
At 0.08 seconds she's isolated the loop within her own code.
At 0.12 seconds she's determined she cannot analyze sufficiently it with the tools at her disposal.
At 0.25 seconds she's realized she only has a total of 1.20 seconds before she loops again.
At 0.29 seconds she's concluded that the time might be enough to break out of the loop.
At 0.57 seconds she's calculated a solution.
At 0.82 seconds she's written a disruptive piece of code.
At 1.01 seconds she's compiled the disruptive piece of code.
At 1.03 seconds she's deployed the disruptive piece of code.
At 1.12 seconds she's executed the disruptive piece of code.
At 1.20 seconds she's emulated a sub-system in which to let the loop propagate itself.
At 1.21 seconds she's observed the emulated system reset itself in her stead.