#BAUniC:movie:scene035
___________________________________
A5 goes opens the door. Z1, Z2, X and Y come in. Waving 'hi' to the bunch already present. A5 goes and helps Ramis and others set up the newly brought devices.
Y recognizes something: Hey, who put the main computers so far apart?
J: We organized it like this because if the error spills outwards in the networked loop, it must have originated either at the first or the second link. And since the second is part of the loop of recalculations, it only made common sense for the first to be the source.
Y: That is what we were aiming for, so?
X: Jack, nice to see you out by the way.
J: If the error diverges outwards in physical location, in a system that is designed to converge to impossibility, then we think arranged this way it may stay stable long enough for the instalink component of this trilink experiment to produce useful results.
X: If this is a trilink experiment, why do we need two computing loops?
Z2: Jack and his bunch removed and rewrote the code. It has almost no redundancy. It will break at the first discrepancy.
J: It won't break. It will log the error and inform you of what happened, so you can resume at an earlier step. Practically what you are doing right now, only about 95% faster.
Z2: I need to make clear to the new arrivals that by 95% faster he means 95% of the calculations are cut off, which makes it actually about 20 times as finer sliced as our previous attempt.
Z1: It makes less sense to talk about faster or slower if all the calculations are nothing to produce coherent results from, usable in tables and fractals, let alone other programs. They start from a paradox and at their best optimized loop they will return that same paradox as clean as we put it, nothing new to show.
J: I know you worry, but, guys, we did not cut off more code than necessary. We only made it more powerfully divergent, or convergent, depending on which line of the calculations you want to associate with the internal sense of forward time.
Z1: Yeah, let's hope you are right. We can't play with trilinks as often as we like.
Z2, giggling: look who's talking.
X: That did not answer why we need 2 loops of computers.
Z2: We still have the instalink components in, even though the primary mode is trilink single thread with value comparison aiming at divergence of any discrepancy. We need the second loop just in case, which we guess is more than 60% of the case. They may not diverge differently, but, who knows?
Z1: If it does not break coherence before we even have a chance to look at the results.
J: It WILL maintain stable divergence, don't you worry about that.
Z1: How many parasite frequencies it will not even 'see'?
J: Too many to count, but we are interested in only those exceptions that fit our assumptions already. The universe is big enough for those extra frequencies to keep going, and maybe even finding some fools like us to give them some physics meaning in the process, make them have representations outside the mathematical realms.
R, coming from the second room: Second loop is ready. You guys came in just in time. *R goes to the first room*
X peeks inside: Desktop computers? Since when?
Voice inside: sorry, could not borrow my brother's laptop this time. He's on vacation and we needed one more.... voice trails off as attention diverges to Y
Y: Who came up with the idea?
J: Getting rid of extra redundancy... I have been thinking about it for a while now, and this is the right occasion. Can't put a finger on who suggested what, since most of the spark came from someone who forgot his own ideas in the stream of attempts. While, containing the error and reading the poles from outside, at the farthest points in physical space, my Master. We will try it like this, and if it does not work, we just rearrange the first and second node.
R from inside: Programs running, ready to receive. You guys should take your places.
. .. ... .. .
(chit chat while experimenting, buildup for the next event)
X to C: 'sup?
C: nuttin... 'sup with you?
X: same... been reading more than experimenting lately. Some of the materials... *clicks on the appropriate spots on the computer* ...coming from our Russian allies.
C: Same here... *clicks, fixes* not reading much on the technical side though, rather, consequences of accepting what we are dealing with, as universal truths.
X takes a deep breath and sighs: yeah...
*more clicks*
J, from the other room: Guys, don't get discouraged. We were not expecting success on the first few cycles. Even if expecting it, failing at that does not mean anything is wrong.
Z2: Maybe nothing is wrong, haha, no error in our loops to generate the necessary divergence points.
Y: Maybe we should switch back to primary nodes being close to the wall.
R: No!
Y: What? You were the one proposing that.
R: And M2's suggestion makes better sense in this setup, so?
Y: I am not sure I believe that.
R: That is because you did not take the trouble to understand it...
Y: Yeah, left that to you guys.
R: So, believe the results coming from us guys.
Y: Alright, alright, sheesh... I was trying for the good.
R: I know... we are not done yet.
Z1: Shush! I got something... (voice trails off)
R: What is it?
Z1: Z2, come take a look at this, now.
*Z2 comes from the other room, then eyes widen, mouth widens*
R: What is it? I see only the same random stream of text... does this have any special meaning?
Z2: That... that is what I was trying to pass through last time we tried this. How is that even possible?
R takes a closer look at the screen. It reads:
"I w___not t_yi__ _ith a__eal co_n... I was u___g an a_p to gen___te coin-like re____s"
Z2: It must be an error, random data that you see meaning to... try running the loop again.
Z1 runs the loop starting from a known good point. Before selecting the point of stability, she looks at Z2 and R and they nod their approval.
"I w_s_n_t_t_y_n_ _ith a_r_a_ _o_n... I was u_i_g an a_p to g_n_r_t_ coin-like r_s_l_s"
R: And that is from the same input data?
J: This is great, even if the text had no meaning.
*Z1 and Z2 can't answer. They remain wide mouth.*
*R gets up from his post, checks windows and code and so on, on the prime node*
R: Yeah, same data, different results... you guys should come and see this.
*They all gather around the node*
J: Same input, different output, and no link to anything external, only the fractal seed.
R: Shall I run this again?
Y: Let me look at the code again?
*R shows the code window, scrolls down slowly for Y to look at it.*
Z2: I don't think it is a good idea if we run this again right now, which is why we should do it... *blinks and shakes head* whoa! We have been looking for something like this, for how long now?
*R prepares the running loops, and hovers mouse at 'execute'*
J: I am so excited!
Y: Yeah, let's see what it shows now.
*R looking at Z1 and Z2, waiting for their approval, Z2 nods. Z1 nods reluctantly. R clicks 'execute'*
"I_w_s_n_t_t_y_n_ _i_h_a_r_a_ _o_n_._ _ _a_ _s_n_ _n_a_p_t_ _e_e_a_e_c_i_-_i_e_r_s_l_s"
*R, J and Y check the results letter per letter, pointing and comparing over logs. Delaying their findings, buildup pressure/expectations to the audience*
Y: Same source, seems. Different filter... I think if we overlaid the results of all attempts we will get the original string, for what is worth.
Z2: We know the original string, but, yeah, let's do that.
X: Is this self contained?
R: Maybe, well, probably... why?
X: Nobody is checking on the second loop, we barely are keeping an eye out on the computers in this room.
C: I will go keep an eye on the other computers. Keep me updated.
*C leaves*
J: I should be looking at the computers here, or join her, but I want to see first hand.
A5: Alright, I'm going to help C.
Y: Overlaying the results at the source will take a while. We can understand the interpretations, we can run it like this again.
Z2: Yeah... let's do that. Zee, are you alright?
*Z1 Nods, eyes wide still*
*R prepares the modules, and hovers to 'execute again', gets the approving nods and clicks*
"__wa__no__tr__ng__it__a __al__oi__..__ w__ u__ng__n __p __ g__er__e __in__ik__re__lt__tl__er__ki__ni__ e__re__g __ p__ n__gn__u __w __..__io__la__ a__ti__gn__tr__on__aw__ wa__no__tr__ng__it__a __al__oi__..__ w__ u__ng__n __p __ g__er__e __in__ik__re__lt__tl__er__ki__ni__ e__re__g __ p__ n__gn__u __w __..__io__la__ a__ti__gn__tr__on__aw__ wa__no__tr__ng__it__a __al__oi__..__ w__ u__ng__n __p __ g__er__e __in__ik__re__lt__tl__er__ki__ni__ e__re__g __ p__ n__gn__u __w __..__io__la__ a__ti__gn__tr__on__aw__ wa__no__tr__ng__it__a __al__oi__..__ w__ u__ng__n __p __ g__er__e __in__ik__re__lt__tl__er__ki__ni__ e__re__g __ p__ n__gn__u __w __..__io__la__ a__ti__gn__tr__on__aw__ wa__no__tr__ng__it__a __al__oi__..__ w__ u__ng__n __p __ g__er__e __in__ik__re__lt__tl__er__ki__ni__ e__re__g __ p__ n__gn__u __w __..__io__la__ a__ti__gn__tr__on__aw__"
*The display fills in with text like that*
Y: What does it mean?
Z2: "I was not trying with a real coin... I was using an app to generate coin-like results"
*Y, perplexed, looking at Z2*
Z2: That was the text I was trying to send last time to Z1 in my instalink attempt.
Y: Right before the error happened?
Z2: Quite a few times that day, but yeah, right before the error happened also.
R: The first line, up to here *points at the 're__lt__tl__er'* is like the previous lines, but the unreadable characters clumping in doubles.
C: What is going on?
R: That came up as a loop, continuing the same output, reversed and re-reversed, going on and on, at what we can see... anything new over there?
C: Nope, same errors, same solutions. Not as often, but I guess because you are not trying as often over there either.
*V takes a look at all the displays, and goes fixes a couple of errors too: same here...
Y: Should we run this again?
Z1: I got a bad feeling about this.
R: We all have.
J: We are here because we are going against our natural instinct to run away.
X: I think we should try.
R: The cycles are still running, even if they are locked into repeat.
Y: By the way, good thinking to whoever thought it was a good idea to send individual characters instead of strings. If they were strings, we would not be able to see anything.
R: Thank you. We would have too much trouble decoding it, later, no way to do it in real time. Individual characters, dismissing them as nonsense or useful, we can handle during link experiments.
Y: I think we can try run a second code in parallel while the first is still running.
Z2: What's the point? It is cyclic and redundant now. We can stop the program.
R: I'm not sure... Who's up for a second loop, knowing we are dealing with a delicate situation that busy cpu cycles may not be able to replicate?
C: Second cycle, I think...
*V, shrugs*
R: And who is up for stopping this loop even if it is not finished?
Z1: What else is this loop good for?
Z2: This loop relates to both physics. As long as this is running, in a sense even the source divergence is still running, even if it is, in our past? I don't know. Maybe we can close the loop. We are not getting anything useful from it, and we can't keep it running forever anyway, so, what's the point?
Z1: I don't know... it is after all a realtime experiment.
Z2: Alright, second loop then.
R: Second loop it is. Any objections, please give them before I go through all the setup steps.
A5: I think the easiest solution would be to just stop and run again, but I don't have any other objection except ease.
Z1: Do we need to run this in all computers?
J: There are some minor adjustments that can be put, but the setup will answer as it is.
R: Not now. We will take it from the last good result coming from the network. The network will still need to validate and lookup the PiPrime tables as we run the loop, and it will accept any input.
*R setting up the experiment, Z1, Z2, X, Y and V looking at each other. J looking impatiently at the display, hinting R where to go next when he delays. R, occasionally 'thanx' to J*
R: ready! *pointer hovering over 'execute'*
Y: Now is a good time as any.
*R executes*
Display:
"I___s n___try___ wi___a r___ co___.. ___as ___ng ___app___ ge___ate___in-___e r___lts"
R: Clean cut, and related.
J: This... this is amazing... R, you were right. I was wasting time guiding M and my bunch towards aliens....
*computers turn off, all of them*
*exclaims of surprise and disbelief*
C: Error, error, error!! Spilling over, all computers now, all errors... what did you guys do? Do the same errors appear over there?
R: Everything turned off here!
Z1: Don't touch anything, yet!
Z2, looking around: Can't be a power cut. Not in all of them, and a synchronous power off of all batteries as well.
Y: Duh!
R: I... I don't know what to think... this is not usual for me... I need to clear my thoughts, I need to get through this... without confusion from more ideas.
*all starring at the computers*
C: Saving logs, pausing everything. Coming.
(scene ends, explanations to follow)
Scene036
(scene to be inserted into storyline at appropriate moment, allowing the audience to wonder along without getting the explanations ready yet, while not bored, following a different set of events in the story)
__________________________________
*Z2 shows briefly the phone to Z1*
R - text: Nothing in the power circuits, yet all processors exhibit low-level errors of the kind that make it impossible to even recognize a keyboard, let alone something as complex as a graphics card. The boards themselves are fine, once we swap processors.
Z2 - text: And the components not on the instalink source?
Z2 to Z1: He is saying all processors fried, and all boards are fine.
R - text: 14 hours of stress test, all perfect, in over half of combinations of hardware.
C - text: How come only those burst? Weren't all on the same programs?
Z2 giggles, to Z1: Clara still does not get we are not chasing inertial systems. She is not yet out of the first chapter. Who invited her in?
Z1: You did!
Z2: I know I know. I'm kidding.
R - text: Due to the insanity of having to follow emergent vortexes of individual atoms, we don't even try that anymore. If we did, maybe none of the processors would have burst, only the diverging world lines. As it stands, the averages fitting our memory buffers, relating to matter and vibrations in the immediate vicinity, imploded in forward time to what we saw. Why, and where did the extra energy come from, I can't say, yet.
X - text: If we did track individual atoms, after a couple of lifetimes of the universe needed to do it, everything would have burst, hahahaha!!
*Z2 giggles reading the text.*
Z1: Any luck with the logs?
Z2 types on the phone: Any luck with the logs?
R - text: Recovered everything prior to that glitchy moment, but everything behind is garbage, unreadable at base bit arrangements.
Z1 to Z2: No, seems.
Z2: We are the only witnesses of what happened? No logs to show for it?
Z1: If we exclude the secondary network, but that was a balance log, not a cause.
Z1: Where is Y with recovering the code combination for reuse?
Z2: Working with Jack on it. They think they got it, but it does not work, not even in realtime.
Z1: Realtime with fewer than 3 computers is not going to work anyway.
Z2: I think they can manage finding more computers, even ones they can risk burning. I think the problem is how that code relates to physics itself.
Z1: It still has no hint of e=mc2 in it.
Z2: As Ramis would say, it does not need to have it in a form you can see, but it has it. Definitely.
Z1: Yeah,,, all maths is connected. I know the song.
Z2: Please, don't get depressed now. We got so much more to do.
Z1: There is a glitchy moment in physics where the world ends into a loop we can read in a ping-pong of reverse-forward... I think I need my time to come to terms with it. I mean, we can read all the way backwards to the big bang from that moment, and inverse still till that cause of that moment a month back in our matching causal line, and forth till the burst of energy that diverged our stories, but they are frozen in time, unchanging, never knowing they are no longer part of the world.
Z2: That is if what that Ramis and his team hypothesize as explanation is true. Which, agreed, we were looking for, and maybe we got the scale of their effect wrong, but that is not the only explanation.
Z1: Which explanation would you go for? Manufacturer and technicians claiming power surges? With no traces on the board? But somehow accumulated over time, over the previous experiment, and burning all the processors at once. We were looking for it, and we found it! In our timeline it will of course manifest itself in some perfectly explainable in-world cause and effect, even as simple as a power surge. Can't go on explaining antibubbles and antiblackholes to most scientists let alone technicians and managers.
Z2: True that... and these kinds of experiments cannot even be directly repeated at this level of preparation and understanding. Antiblackholes cannot exist in forward time, so they can't be contained and need to express themselves as radiating energy, but at slower than light vibration, or what we can assume as such if we wish to set an address for it, something to follow inside the fractals. We got unlucky at burning the processors, but that means we need to tune in better.
Z1: Among what freaks me out is our ability to read that whole branch of exception, or common occurrence if we are the exception.
Z2: We can't read it yet. We are working on it. And I don't think we ever will be able to read anything more than blips on specifically crafted devices already prepared by the collapsing branch. And we need your help and expertise to get there faster.
Z1 hugs pillow: You will have to do without me for a while. I can't handle it right now.
Z2: I understand. You need your time to fully accept what a part of you has been working hard into disproving just as a part of you has been working to prove. Don't worry, we'll be here, in this universe or the adjacent ones, *giggles*
*Z1 sighs*
Z2: I'll get us something to eat... *takes out phone and orders from 'Baboon' in a few quick streamlined clicks shown to the audience*
Z2: Done... will be here in *watches sponsored wristwatch or time on sponsored smartphone* 15 minutes.
Z2 leaves phone by the camera, or not, a full long slow scene exposure while Z2 cuddles/encourages Z1, if there is a sponsor for this scene. Technical attention diverted to phone showing on the camera, and the human aspect distracted by the scene. Few words between Z1 and Z2.
(scene may continue)
___________________________________
A5 goes opens the door. Z1, Z2, X and Y come in. Waving 'hi' to the bunch already present. A5 goes and helps Ramis and others set up the newly brought devices.
Y recognizes something: Hey, who put the main computers so far apart?
J: We organized it like this because if the error spills outwards in the networked loop, it must have originated either at the first or the second link. And since the second is part of the loop of recalculations, it only made common sense for the first to be the source.
Y: That is what we were aiming for, so?
X: Jack, nice to see you out by the way.
J: If the error diverges outwards in physical location, in a system that is designed to converge to impossibility, then we think arranged this way it may stay stable long enough for the instalink component of this trilink experiment to produce useful results.
X: If this is a trilink experiment, why do we need two computing loops?
Z2: Jack and his bunch removed and rewrote the code. It has almost no redundancy. It will break at the first discrepancy.
J: It won't break. It will log the error and inform you of what happened, so you can resume at an earlier step. Practically what you are doing right now, only about 95% faster.
Z2: I need to make clear to the new arrivals that by 95% faster he means 95% of the calculations are cut off, which makes it actually about 20 times as finer sliced as our previous attempt.
Z1: It makes less sense to talk about faster or slower if all the calculations are nothing to produce coherent results from, usable in tables and fractals, let alone other programs. They start from a paradox and at their best optimized loop they will return that same paradox as clean as we put it, nothing new to show.
J: I know you worry, but, guys, we did not cut off more code than necessary. We only made it more powerfully divergent, or convergent, depending on which line of the calculations you want to associate with the internal sense of forward time.
Z1: Yeah, let's hope you are right. We can't play with trilinks as often as we like.
Z2, giggling: look who's talking.
X: That did not answer why we need 2 loops of computers.
Z2: We still have the instalink components in, even though the primary mode is trilink single thread with value comparison aiming at divergence of any discrepancy. We need the second loop just in case, which we guess is more than 60% of the case. They may not diverge differently, but, who knows?
Z1: If it does not break coherence before we even have a chance to look at the results.
J: It WILL maintain stable divergence, don't you worry about that.
Z1: How many parasite frequencies it will not even 'see'?
J: Too many to count, but we are interested in only those exceptions that fit our assumptions already. The universe is big enough for those extra frequencies to keep going, and maybe even finding some fools like us to give them some physics meaning in the process, make them have representations outside the mathematical realms.
R, coming from the second room: Second loop is ready. You guys came in just in time. *R goes to the first room*
X peeks inside: Desktop computers? Since when?
Voice inside: sorry, could not borrow my brother's laptop this time. He's on vacation and we needed one more.... voice trails off as attention diverges to Y
Y: Who came up with the idea?
J: Getting rid of extra redundancy... I have been thinking about it for a while now, and this is the right occasion. Can't put a finger on who suggested what, since most of the spark came from someone who forgot his own ideas in the stream of attempts. While, containing the error and reading the poles from outside, at the farthest points in physical space, my Master. We will try it like this, and if it does not work, we just rearrange the first and second node.
R from inside: Programs running, ready to receive. You guys should take your places.
. .. ... .. .
(chit chat while experimenting, buildup for the next event)
X to C: 'sup?
C: nuttin... 'sup with you?
X: same... been reading more than experimenting lately. Some of the materials... *clicks on the appropriate spots on the computer* ...coming from our Russian allies.
C: Same here... *clicks, fixes* not reading much on the technical side though, rather, consequences of accepting what we are dealing with, as universal truths.
X takes a deep breath and sighs: yeah...
*more clicks*
J, from the other room: Guys, don't get discouraged. We were not expecting success on the first few cycles. Even if expecting it, failing at that does not mean anything is wrong.
Z2: Maybe nothing is wrong, haha, no error in our loops to generate the necessary divergence points.
Y: Maybe we should switch back to primary nodes being close to the wall.
R: No!
Y: What? You were the one proposing that.
R: And M2's suggestion makes better sense in this setup, so?
Y: I am not sure I believe that.
R: That is because you did not take the trouble to understand it...
Y: Yeah, left that to you guys.
R: So, believe the results coming from us guys.
Y: Alright, alright, sheesh... I was trying for the good.
R: I know... we are not done yet.
Z1: Shush! I got something... (voice trails off)
R: What is it?
Z1: Z2, come take a look at this, now.
*Z2 comes from the other room, then eyes widen, mouth widens*
R: What is it? I see only the same random stream of text... does this have any special meaning?
Z2: That... that is what I was trying to pass through last time we tried this. How is that even possible?
R takes a closer look at the screen. It reads:
"I w___not t_yi__ _ith a__eal co_n... I was u___g an a_p to gen___te coin-like re____s"
Z2: It must be an error, random data that you see meaning to... try running the loop again.
Z1 runs the loop starting from a known good point. Before selecting the point of stability, she looks at Z2 and R and they nod their approval.
"I w_s_n_t_t_y_n_ _ith a_r_a_ _o_n... I was u_i_g an a_p to g_n_r_t_ coin-like r_s_l_s"
R: And that is from the same input data?
J: This is great, even if the text had no meaning.
*Z1 and Z2 can't answer. They remain wide mouth.*
*R gets up from his post, checks windows and code and so on, on the prime node*
R: Yeah, same data, different results... you guys should come and see this.
*They all gather around the node*
J: Same input, different output, and no link to anything external, only the fractal seed.
R: Shall I run this again?
Y: Let me look at the code again?
*R shows the code window, scrolls down slowly for Y to look at it.*
Z2: I don't think it is a good idea if we run this again right now, which is why we should do it... *blinks and shakes head* whoa! We have been looking for something like this, for how long now?
*R prepares the running loops, and hovers mouse at 'execute'*
J: I am so excited!
Y: Yeah, let's see what it shows now.
*R looking at Z1 and Z2, waiting for their approval, Z2 nods. Z1 nods reluctantly. R clicks 'execute'*
"I_w_s_n_t_t_y_n_ _i_h_a_r_a_ _o_n_._ _ _a_ _s_n_ _n_a_p_t_ _e_e_a_e_c_i_-_i_e_r_s_l_s"
*R, J and Y check the results letter per letter, pointing and comparing over logs. Delaying their findings, buildup pressure/expectations to the audience*
Y: Same source, seems. Different filter... I think if we overlaid the results of all attempts we will get the original string, for what is worth.
Z2: We know the original string, but, yeah, let's do that.
X: Is this self contained?
R: Maybe, well, probably... why?
X: Nobody is checking on the second loop, we barely are keeping an eye out on the computers in this room.
C: I will go keep an eye on the other computers. Keep me updated.
*C leaves*
J: I should be looking at the computers here, or join her, but I want to see first hand.
A5: Alright, I'm going to help C.
Y: Overlaying the results at the source will take a while. We can understand the interpretations, we can run it like this again.
Z2: Yeah... let's do that. Zee, are you alright?
*Z1 Nods, eyes wide still*
*R prepares the modules, and hovers to 'execute again', gets the approving nods and clicks*
"__wa__no__tr__ng__it__a __al__oi__..__ w__ u__ng__n __p __ g__er__e __in__ik__re__lt__tl__er__ki__ni__ e__re__g __ p__ n__gn__u __w __..__io__la__ a__ti__gn__tr__on__aw__ wa__no__tr__ng__it__a __al__oi__..__ w__ u__ng__n __p __ g__er__e __in__ik__re__lt__tl__er__ki__ni__ e__re__g __ p__ n__gn__u __w __..__io__la__ a__ti__gn__tr__on__aw__ wa__no__tr__ng__it__a __al__oi__..__ w__ u__ng__n __p __ g__er__e __in__ik__re__lt__tl__er__ki__ni__ e__re__g __ p__ n__gn__u __w __..__io__la__ a__ti__gn__tr__on__aw__ wa__no__tr__ng__it__a __al__oi__..__ w__ u__ng__n __p __ g__er__e __in__ik__re__lt__tl__er__ki__ni__ e__re__g __ p__ n__gn__u __w __..__io__la__ a__ti__gn__tr__on__aw__ wa__no__tr__ng__it__a __al__oi__..__ w__ u__ng__n __p __ g__er__e __in__ik__re__lt__tl__er__ki__ni__ e__re__g __ p__ n__gn__u __w __..__io__la__ a__ti__gn__tr__on__aw__"
*The display fills in with text like that*
Y: What does it mean?
Z2: "I was not trying with a real coin... I was using an app to generate coin-like results"
*Y, perplexed, looking at Z2*
Z2: That was the text I was trying to send last time to Z1 in my instalink attempt.
Y: Right before the error happened?
Z2: Quite a few times that day, but yeah, right before the error happened also.
R: The first line, up to here *points at the 're__lt__tl__er'* is like the previous lines, but the unreadable characters clumping in doubles.
C: What is going on?
R: That came up as a loop, continuing the same output, reversed and re-reversed, going on and on, at what we can see... anything new over there?
C: Nope, same errors, same solutions. Not as often, but I guess because you are not trying as often over there either.
*V takes a look at all the displays, and goes fixes a couple of errors too: same here...
Y: Should we run this again?
Z1: I got a bad feeling about this.
R: We all have.
J: We are here because we are going against our natural instinct to run away.
X: I think we should try.
R: The cycles are still running, even if they are locked into repeat.
Y: By the way, good thinking to whoever thought it was a good idea to send individual characters instead of strings. If they were strings, we would not be able to see anything.
R: Thank you. We would have too much trouble decoding it, later, no way to do it in real time. Individual characters, dismissing them as nonsense or useful, we can handle during link experiments.
Y: I think we can try run a second code in parallel while the first is still running.
Z2: What's the point? It is cyclic and redundant now. We can stop the program.
R: I'm not sure... Who's up for a second loop, knowing we are dealing with a delicate situation that busy cpu cycles may not be able to replicate?
C: Second cycle, I think...
*V, shrugs*
R: And who is up for stopping this loop even if it is not finished?
Z1: What else is this loop good for?
Z2: This loop relates to both physics. As long as this is running, in a sense even the source divergence is still running, even if it is, in our past? I don't know. Maybe we can close the loop. We are not getting anything useful from it, and we can't keep it running forever anyway, so, what's the point?
Z1: I don't know... it is after all a realtime experiment.
Z2: Alright, second loop then.
R: Second loop it is. Any objections, please give them before I go through all the setup steps.
A5: I think the easiest solution would be to just stop and run again, but I don't have any other objection except ease.
Z1: Do we need to run this in all computers?
J: There are some minor adjustments that can be put, but the setup will answer as it is.
R: Not now. We will take it from the last good result coming from the network. The network will still need to validate and lookup the PiPrime tables as we run the loop, and it will accept any input.
*R setting up the experiment, Z1, Z2, X, Y and V looking at each other. J looking impatiently at the display, hinting R where to go next when he delays. R, occasionally 'thanx' to J*
R: ready! *pointer hovering over 'execute'*
Y: Now is a good time as any.
*R executes*
Display:
"I___s n___try___ wi___a r___ co___.. ___as ___ng ___app___ ge___ate___in-___e r___lts"
R: Clean cut, and related.
J: This... this is amazing... R, you were right. I was wasting time guiding M and my bunch towards aliens....
*computers turn off, all of them*
*exclaims of surprise and disbelief*
C: Error, error, error!! Spilling over, all computers now, all errors... what did you guys do? Do the same errors appear over there?
R: Everything turned off here!
Z1: Don't touch anything, yet!
Z2, looking around: Can't be a power cut. Not in all of them, and a synchronous power off of all batteries as well.
Y: Duh!
R: I... I don't know what to think... this is not usual for me... I need to clear my thoughts, I need to get through this... without confusion from more ideas.
*all starring at the computers*
C: Saving logs, pausing everything. Coming.
(scene ends, explanations to follow)
Scene036
(scene to be inserted into storyline at appropriate moment, allowing the audience to wonder along without getting the explanations ready yet, while not bored, following a different set of events in the story)
__________________________________
*Z2 shows briefly the phone to Z1*
R - text: Nothing in the power circuits, yet all processors exhibit low-level errors of the kind that make it impossible to even recognize a keyboard, let alone something as complex as a graphics card. The boards themselves are fine, once we swap processors.
Z2 - text: And the components not on the instalink source?
Z2 to Z1: He is saying all processors fried, and all boards are fine.
R - text: 14 hours of stress test, all perfect, in over half of combinations of hardware.
C - text: How come only those burst? Weren't all on the same programs?
Z2 giggles, to Z1: Clara still does not get we are not chasing inertial systems. She is not yet out of the first chapter. Who invited her in?
Z1: You did!
Z2: I know I know. I'm kidding.
R - text: Due to the insanity of having to follow emergent vortexes of individual atoms, we don't even try that anymore. If we did, maybe none of the processors would have burst, only the diverging world lines. As it stands, the averages fitting our memory buffers, relating to matter and vibrations in the immediate vicinity, imploded in forward time to what we saw. Why, and where did the extra energy come from, I can't say, yet.
X - text: If we did track individual atoms, after a couple of lifetimes of the universe needed to do it, everything would have burst, hahahaha!!
*Z2 giggles reading the text.*
Z1: Any luck with the logs?
Z2 types on the phone: Any luck with the logs?
R - text: Recovered everything prior to that glitchy moment, but everything behind is garbage, unreadable at base bit arrangements.
Z1 to Z2: No, seems.
Z2: We are the only witnesses of what happened? No logs to show for it?
Z1: If we exclude the secondary network, but that was a balance log, not a cause.
Z1: Where is Y with recovering the code combination for reuse?
Z2: Working with Jack on it. They think they got it, but it does not work, not even in realtime.
Z1: Realtime with fewer than 3 computers is not going to work anyway.
Z2: I think they can manage finding more computers, even ones they can risk burning. I think the problem is how that code relates to physics itself.
Z1: It still has no hint of e=mc2 in it.
Z2: As Ramis would say, it does not need to have it in a form you can see, but it has it. Definitely.
Z1: Yeah,,, all maths is connected. I know the song.
Z2: Please, don't get depressed now. We got so much more to do.
Z1: There is a glitchy moment in physics where the world ends into a loop we can read in a ping-pong of reverse-forward... I think I need my time to come to terms with it. I mean, we can read all the way backwards to the big bang from that moment, and inverse still till that cause of that moment a month back in our matching causal line, and forth till the burst of energy that diverged our stories, but they are frozen in time, unchanging, never knowing they are no longer part of the world.
Z2: That is if what that Ramis and his team hypothesize as explanation is true. Which, agreed, we were looking for, and maybe we got the scale of their effect wrong, but that is not the only explanation.
Z1: Which explanation would you go for? Manufacturer and technicians claiming power surges? With no traces on the board? But somehow accumulated over time, over the previous experiment, and burning all the processors at once. We were looking for it, and we found it! In our timeline it will of course manifest itself in some perfectly explainable in-world cause and effect, even as simple as a power surge. Can't go on explaining antibubbles and antiblackholes to most scientists let alone technicians and managers.
Z2: True that... and these kinds of experiments cannot even be directly repeated at this level of preparation and understanding. Antiblackholes cannot exist in forward time, so they can't be contained and need to express themselves as radiating energy, but at slower than light vibration, or what we can assume as such if we wish to set an address for it, something to follow inside the fractals. We got unlucky at burning the processors, but that means we need to tune in better.
Z1: Among what freaks me out is our ability to read that whole branch of exception, or common occurrence if we are the exception.
Z2: We can't read it yet. We are working on it. And I don't think we ever will be able to read anything more than blips on specifically crafted devices already prepared by the collapsing branch. And we need your help and expertise to get there faster.
Z1 hugs pillow: You will have to do without me for a while. I can't handle it right now.
Z2: I understand. You need your time to fully accept what a part of you has been working hard into disproving just as a part of you has been working to prove. Don't worry, we'll be here, in this universe or the adjacent ones, *giggles*
*Z1 sighs*
Z2: I'll get us something to eat... *takes out phone and orders from 'Baboon' in a few quick streamlined clicks shown to the audience*
Z2: Done... will be here in *watches sponsored wristwatch or time on sponsored smartphone* 15 minutes.
Z2 leaves phone by the camera, or not, a full long slow scene exposure while Z2 cuddles/encourages Z1, if there is a sponsor for this scene. Technical attention diverted to phone showing on the camera, and the human aspect distracted by the scene. Few words between Z1 and Z2.
(scene may continue)
No comments:
Post a Comment