Shannon's Journal Discussion

[Shannon]

ASRB-related question/suggestion for Shannon: To offset compounding 5.5G exhaustion, could more tightly-packed contiguous loops benefit from progressively longer ASRB silences? You've only mentioned constant ASRB values per sub, but exhaustion is more cumulative than constant. Have you tested any linear or logarithmic incremental increases in silence duration? Less noise-silence ratio, more data pipeline management?

I'd also wonder if it wouldn't help to explain why AOSI (which has even more borrowed 6G tech to exhaust us than E2) favors shorter daily loop counts, if a measly 15 minutes of rest is more optimal by loop 2 than it is by loop 12. I've set my computer to auto-increment sleep values between loops, which works well for me and maximizes daily loop count without me having to space them out manually (the goal of ASRB, I'd assume), while others on the forum have started to mention more ad-hoc/manual methods of spacing them out. Yesterday, I set the increments as a multiple of the Fibonacci sequence for fun. Today, I might try the Mandelbrot set. This may also be a definition for the word "fun" of which no one in their right minds was previously aware.

ASRB ratios are calculated specifically for each program according to the exact intensity of the technologies used in it's unique script. That is why we have 20:2 for E2, and 60:15 for AOSI V1. It will likely be a unique ratio for each program as a result of this fact.

You're assuming that 6G tech will always increase energy consumption and exhaustion. That is not necessarily the case. It depends on which specific technologies are included in one script, how they interact, and how complex the goals of the program are.

That said, the ASRB values are constant because if I made them dynamic, calculating proper usage patterns would become a true nightmare. So they are constant, and we determine the optimal number of loops as a result.

AOSI is designed for contiguous loops, not manually spaced loops. That's why I have the constant ASRB ratio. It's designed to "power up" most efficiently through contiguous loops, and the rest periods are not really intended so much for rest, as for execution.

If we input only, too much energy is spent in processing, and not enough in execution while the program is being loaded. The ASRB gives me the ability to do as a bird taking off vertically does - downthrust enough to get itself into the air and reset it's wings for another downthrust, which it can then deliver at the apex of the previous upward movement. The effect is much more efficient at getting the bird into the air than one huge thrust.

ASRB is calculated to get "maximum thrust and effect" for each program according to the specifics of the script.