GW CPU Spotlight work

From this "Spotlight" this came into my mind... I thought I would share.

I established a contact with my friends who have observed my voluntary experiment of me living on this planet (for a few local decades now). They've been slowly circling on an intergalactic orbit quite far away, so before I left for my journey here it was originally a challenge how the bidirectional data transmission would be done effectively. But we came up with the idea to use the omni sensing space-fabric scanners (OSSFC, based in adaptively coherent laser beams) on the wings of our Class 7 Mass cruiser ship.

We decided to try forcing a controlled intervention into a gamma-ray burst that a neutron star (located moderately nearby) was ejecting. We were able to get the calculations right. Actually, my friends up there I mean. I was never very good with imputting the seed data for our neuronics that would then do the end point calculations. Beginning the intervention at an exact moment and using the re-programmed lasers for precise lensing effect they redirected a selected amunt of the outer layers of the burst and pulse-modified it to carry data to me.

I was originally transported here with some tools in my backpack. A portable receiver to begin with. It prooved to work very nicely for years, but sadly we hadn't quite taken into account the rise of CO2 level in the atmosphere. That has changed the internal fluid dynamics and therefore magnetic fluctuations on this planet. The relevant bias values on the laser lensing formula 'up there' begun to produce just slightly wrong summing effect. A consequence: I had to wait through a communcation blackout for three years until another one of our ships made a closer visit and re-scanned the atmosphere in higher resolution. Normally that ship is performing dual-dimensional cartography duties somewhere in the most empty places, so it had very good equipment for probing. But that ship will proceed with these kind of low-priority tasks only when the time or timing is right. Lucky me after all... I won't complain.

We have to remember that the incoming signal temporarily forms a whole in the atmosphere, having a diameter of 72nm. Whatever regular particles are in the atmosphere on the route of these incoming transmission beams... will be flashed into dark quark matter (consisting of what we call 'nepleons'). That 72nm was precalculated and was enough to make a clear way for my reply data stream until those atmospheric conditions recently changed here too much. My receiver has some basic auto-adjusting capabilities. It can tune into their nicely controlled beam if I'm close enough, and it tells me what direction I should move to polish the signal to perfection. And as a precaution, the receiver tells me where I must NOT stand here at the surface. The pre-selected transmission locations for establishing our contacts were originally surprisingly well picked. I must say we succeeded on that one. No harm to any mammal nor bird size type species have been caused by all our transmissions. I always consider though the importance before requesting any additional out-of-schedule contact up there, to avoid any unnesseccary risks.

We had a scheduled contact today. I had some foggy moments in the afternoon and asked them if I should tell here that... now as the cpu work units are available again... I'm running a fresh linux installation. They responded "why not, try and observe for any reaction".

I'm crunching these 'spotties' with a linux host that is running Ubuntu 20.10 groovy gorilla daily-live build, currently boosted with kernel 5.9-rc2. Seems to be working alright.