You're probably thinking "one cell = one pixel." In fact "one cell = one 8x8 block of pixels"; the specific pattern of colors in each 8x8 block represents the opcodes of that cell's 64-opcode program. So when the replicator takes over the map, it's changing the image to a repeating pattern of 8x8 blocks.
Now, don't quote me on this part, but I think the first replicator to take over is this (minus all the "junk DNA" between the instructions):
[}<,]}],<}[
and the second, more efficient, one is:
{[}<,]],<}[{
The latter means roughly:
--head1;
while (*head0) { *--head0 = *++head1; }
*head0-- = *head1++;
while (*head0) { --head1;
// CUT HERE
which gets pasted together with whatever cell it's breeding with at the time.
When i worked on image pipeline the images were circular and had to be warped to square.
Also the edges of the circular image were darker than the middle, and needed to be brightened.
CPU affinity?
I haven't been able to change priority in task manager since window 8 i think. Cpu affinity seems only to allow which cores get assigned...not really good management.
A battery cell is a long thin ribbon that is rolled into a spiral shape. There's no way you can apply any mechanical agitation to all the layers. It's been tried, but nothing came out of it.
This is largely a misconception that's caused by the fact that EV fires are hard to extinguish with normal water sprays. That is because the bettery packs are designed to be water proof, so it is hard to get the fire patrol's water in. If you can immerse the pack in water, the fire is extinguished without much trouble. That's unlike petroleum fires, where the fuel is lighter than water and liquid, so water spray will boil and spread the fire instead of extinguishing it.
It doesn't need to be extinguished, it just needs to be removed from the ship. Even a second of airtime (and a healthy lateral velocity) might be enough that the ship is out of the explosive radius of the battery.
