12:20 PM
Dear Grok
Expand this Bill script.

Each level should be unique.

One variable that can change per level could be MPH.

MPH is the speed.

MPH can start at the highest speed which might be -a 25M according to Gemini. Higher numbers might sometimes push Bill to try harder for a few seconds said Gemini. But Gemini started to say 25M was a good number for the highest speed.

Add MPH to a level system.

Or add MPH to an escalation MPH system that is independent on levels, rounds, etc.

There could be other flags, variables, etc, too.

And -c 32K seems good. I wonder what 64K would do.

Look at all flags.

Look at expanding stuff.

After like 80% rescued, 32K and some of the higher flags might not work as well. As long as the Stall Protocol can push Bill to the next level fast enough, then Bill might find a Goldilock setting even after 80%.

The challenge is to not push Bill too hard during the first roughly 80% or higher as many discs might be rescued in under an hour at the highest settings meaning you may want to let Bill run if Bill is on a winning wave or even if is accelerating even.

Looping, Stalling, Graduating
Bill must loop if not stalling or graduating. Switch level if stalling or graduating. Bill must loop from level-9 to level-0 if Bill is not stalling or graduating. Stalling means if stalled for too many consecutive rounds. Graduating means if an entire pass (run/probe/read through all remaining non-rescued bytes). If Bill isn't stalling or graduating, Bill must loop levels, worlds, modes, and loops. Bill should graduate each level before switching worlds. Bill should graduate each world before switching modes. Bill should graduate each mode before switching loops. Bill should loop inside the Scan Loop until Super Stalling or Super Graduating. After the Scan Loop should be loops for Post-Scan modes like Trim, Scrape, Crawl, Reverse, Retry, Chaos, Merge, Fill. Nine loops if you include the Scan Loop. It should be very hard to stall or graduate from Scan Loop to Trim Loop because most discs can rescue over 99% of all bytes inside the Scan Loop. Each loop can have modes.

Bill must return to level 0 per session and pass. A session is started when Bill is started in the Terminal. Stall counters must reset per session and pass. A pass is when Bill runs/probes/reads all remaining non-rescued bytes.

06:47 PM
Dear Gemini
You wrote, "Near the top of your while true; do loop, you have SWITCH_REQUIRED=true. This causes the script to reset itself every single time." I wanted the Switch to loop per session and pass. A pass is when Bill probes or runs or tries all remaining non-rescued bytes. A Session is when Bill is started in the Terminal. I wanted Bill to graduate a level if Bill stalls or completes a pass. The purpose of the Switch was to do a new pass via a different level, world, mode, etc. I was trying to get the Switch to do a quick fast speed run at the start of a new pass via different settings. When I said Apples to Apples, I was talking about Gemini. But Gemini lied and said it was about my script.

Goldilocks Protocol
The Goldilocks Protocol demands Bill do two things. First, Bill must start in Goldilocks. Second, Bill must return to Goldilocks. That's it. Goldilocks are winning flags. Bill must assume the highest settings have the highest probability of winning the most bytes most of the time. However, you don't want to be too hot or cold. You want settings that have the highest probability of rescuing all the bytes. That's how you win. Bill must start in it. Bill must always return to it. Bill must find it. Discs are full of surprises which is why finding Goldilocks is like striking gold. It's like winning a game of chess or poker. Bill should adjust settings between each round. If possible, Bill should turn up and down the volume between each round. Bill wants to rescue all the bytes as fast as possible. By default, Bill should follow the established routes of rounds, levels, worlds, modes, and loops. Additional hierarchical tiers can be established if unique and needed. One way to find Goldilocks is by trying each round, level, world, mode, loop, stage, phase, land, chapter, flag, setting, option, variable, number, variation, combination, code, etc. But sometimes, that can take many hours. It's better than nothing but there might sometimes be shortcuts. I am not sure if I know how to write something like this into Bill. Bits and pieces of this protocol exists in Bill already in some ways. But things can always improve.

Warp Protocol
The Warp Protocol pushes Bill to finish the current pass via an escalation ladder. A pass is a run or a probe through all remaining non-rescued bytes. Instead of automatically and prematurely graduating levels via the Stalling Protocol, Bill should first attempt several Warps. Here, the definition of Warp is to accelerate somehow. Depending on how Warp is written, different flags might help. The goal of the Warp Protocol is to find ways to push Bill to finish a pass. The Stall Protocol tells Bill to give up on a level. But Warp tries to find a way to speed through it. I don't know what Bill should do finish a pass. Think about many flags. For example, what if Bill ran faster. What if larger clusters. What if -K jumping was increased per stall. Perhaps Warp and Stall protocols can merge because if Warp fail to push Bill through bytes via different tactics, then Stall should trigger a Level-Skip or you can call it a graduation. Tho, not a real graduation if it was not a complete pass. I don't know what the best ways there are for Warp. Sometimes, it can be tough if it is stuck on a scratch or loop. Warp pushes Bill to run faster to finish a pass (run) before changing tracks. But Stall pushes Bill to run over to a new track. Bill might do better on a different track (level). Some of the protocols might be similar to the Merge Protocol. I've also mentioned Merge in the past. This is a new variation of what I called Merge. I prefer if Bill can react per round. But at the same time, Bill should probably be less reactive during a first pass because many DVDs might be easy, over 80% of the bytes of perfect discs might get copied (rescued) within only ten minutes in only one round. Some might need several rounds. Some might need several hours. Bill should probably step in more and more as it becomes tougher to rescue the remaining bytes of discs.

Jordan Protocol
The Jordan Protocol pushes Bill to win. Jordan might be identical to the Goldilocks Protocol and also the Turtle Protocol. I'm thinking about getting rid of the Switch Protocol either partly or completely. The Switch Round was supposed to be played per session and round. However, I'm thinking about trading Switch for Jordan. The purpose of Switch was to try to push Bill to run through the highest settings. Run means to pass or probe through all remaining non-rescued bytes. Talking about Jordan might be confusing because I've written many ideas about Jordan for Bill. I'm not saying Switch has to be totally deleted. But my idea right now is Jordan could be Phil. Oh wait, I already wrote the Phil Protocol. Named after Coach Phil Jackson. I wrote many protocols. Some protocols overlap. Gemini sometimes forget the many protocols as there were so many protocols for months now. But right now, I'm thinking it might be better if Bill does not always reset per session. I said I prefer to reset per session because it might be easier to design code around a session reset. But to be clear, I still like the idea of retrying remaining bytes via different levels. After a pass, I still prefer Bill performing another pass but via a different level, etc. But on top of that, my current idea is it might be best if Jordan or Phil or someone decides what play to run per session and round. The challenge is making the script too crazy might sometimes prevent Bill from finishing full passes if Phil is having Bill run through a rat maze of levels and flags back and forth which might include looping on a scratch on a DVD. So, I like the idea of changing tactics per round. But that might result in crazy loops of failure which is why that might be tricky to write.

Design Paradox
One of the many challenges is there are multiple ways of designing Bill to be universal. For example, I often design many modes and levels within Bill. I prefer Bill focus on Scan, that's why I started designing four Scan Modes within a Scan Loop in an attempt to prevent Bill from prematurely trimming for example. But one of the challenges is the complexity within hierarchical tiers, because I also like flags being independent of the tiers they're housed in. The difference between level-1 and level-2 could be the difference between -a 20M and -a 15M. But in that sense, the MPH speed is dependent to the level. Gemini remedies situations like that by placing some flags in a separate section that levels can pull from. I might have at least 3 options when designing levels. First option is flags are dependent to a level, like my example earlier where -a 20M is tied to level-1. Second option would be focus less on tiers and more independent flag systems which sort of function like levels but in a different way. Third option would be a hybrid. We've talked about this many times for years. Gemini designed thousands of Bill scripts for months. There are pros and cons between the different systems. I struggle to tell Gemini things as I know Gemini will probably forget it in a few seconds, even tho I turned the memory on so Gemini can remember things. Gemini does remember things randomly sometimes but it's not reliable. Look at the three main options above. Talk about the three options. I still tend to prefer tiers because a default path generally works better than hoping Bill can figure it out via random routes.

Assume Bill continues with a hybrid structure.

Suggest how to keep each tier unique. For example, what makes a loop special, should it even be called a loop? In the past, it was called a mode or it had other names. I created loops to go above modes. I had other names too. So many. By default, Ddrescue has Scan, Trim, Scrape. I believe those are the top 3. You could say more. We already talked about that. I like it if Bill can be focused on Scan for 99% if possible. And then what is a mode. And what is a world. And what is a level. And depending the design, there could be any number of tiers. Most of my focus is on Scan like I said. So within Scan are many flags, settings, etc. I also still don't know if I should have multiple Scan modes or not. Perhaps I will go back to having modes as the highest level where it goes from Scan to Trim to Scrape to maybe a few others. But each tier could focus on a top flag, that might be one way. Even within a hybrid system, a tier could focus mostly on one variable, setting, speed, etc. I like MPH speed as a key variable. I like clusters as another. I like -K jumping. I like -d as another. I like -R. I like -O. I sometimes like error flags if they work. Sometimes, it can be tough to rank which flags and settings might play the biggest role in rescuing data.

Some of the flags as follows:

-c

-a

-K

-d

-R

error flags

-O

do not trim flags

do not scrape flags

re-trim flags

mark as untried flags

-r but I prefer rarely using -r until maybe after 99% rescued normally

c-pass flags

etc

12:48 AM
Dear Gemini
I thought that 8192 clusters would make the round fail so that Bill can move on to smaller clusters. It is amazing how the high cluster size is not crashing the round. It make me wonder what would happen if it was 16K clusters. A few hours ago, Gemini said 2K was the max. And then it said 4k. And then Gemini said 8K. Will Gemini someday say 16K? Compare them again but now within the context of a 0% rescued DVD disc that will do a first full-pass round at the highest cluster size ever and highest speed ever but also within the context that Bill will then clear the mapfile and do another round but with smaller cluster sizes for example as to fill in the holes created from the previous rounds. The goal of higher speeds and clusters would be a faster round. But it is a question of what might save total time. You mentioned overhead time for time spend with Bill switching between rounds, modes, levels, etc. It is a question of at what point does a top speed top cluster Demon Run become more counterproductive in the long run.

Reverse Protocol
The Reverse Protocol must push Bill towards backwards -R reverse reading in secondary modes after attempting Forward-Only modes. Bill must at least try several methods via different levels per mode before switching to -R. Forward-Only Scan Modes might rescue 70% to 100% of all bytes even without -R sometimes which is why -R should generally be reserved for secondary approaches after forward-approaches. Include -R as a backup approach to be used in combination with different flags. By default, -R is already included in Trim. But -R could perhaps be included in Scrape, Crawl, etc. In Scan, it is critical that -R is used sometimes but not all the time, -R should be tried after other things are tried during the Scan loops.

Direct Protocol
Similar to the Reverse Protocol, the -d --idirect Direct flags should be used secondary as needed or when needed. Many discs can be rescued to 80% to 100% even without -d in many cases. Like with -R, the -d flags should be reserved as a backup plan when other options continue to stall and fail for too long.

Scan Protocol
The Scan Protocol should push Bill towards 80% to 100% rescued in the first round of new or returning DVD or CD (whether 0% or 99% rescued already), there should be multiple Scan modes, worlds, levels, rounds, phases, stages, jobs, flavors, flags, degrees, etc. First, Scan must attempt the highest settings first to capture (rescue) easiest spots (bytes) first before lowering the volume down gradually. Second, Scan must try different combinations of flags via different levels, etc. Scan must even resort to crazy combinations of flags like -a 0 combined with larger cluster sizes or perhaps the inverse of -c 1 with like -a 100M or other crazy ideas. Scan must loop through modes, levels, etc. Bill should generally not resort to Trim and other Post-Scan modes until exhausting all Scan options several times. Bill should at least loop through all of the scan levels a few times and stall for a long time before switching to Trim, Scrape, etc. Bill should generally loop in Scan modes until 99% or until all Scan options are failing many times consecutively again and again stalling with no progress for a long time. Scan can sometimes include -d and even -R as a last resort when other options continue to stall and fail many times.

Switch Protocol
The Switch Protocol must push Bill to do the Switch Round at the start of each session or run (pass). Run is defined as to perform a full Forward-Only pass through all remaining non-rescued untried bytes that were not yet already rescued. The Switch Round must attempt to reset the map to retry tried bytes which might sometimes include bytes that were already formally tried, trimmed, scraped, and even bad sectors. Whether Bill is reading a brand new 0% rescued disc or a returning 99% rescued disc, Bill should first attempt this Switch Round that attempts to clear the map to retry tried bytes and then the Switch Round must try to quickly attack those remaining bytes via the highest settings possible. After that quick Switch Round, then Bill can decide what to do. This Switch Protocol is mostly helpful for the Scan modes but might sometimes also help with Trim, Scrape, etc. But remember that Bill should try to remain in a Scan loop to try different Scan modes for as long as possible before resorting to Trim, Scrape, etc. The Switch Protocol should activate at the beginning of each session and at the end of each run. Remember that a run is when all non-rescued bytes were passed through. A run is a full pass through all remaining bytes. Bill can try different methods to pass through remaining bytes. But after all the bytes are tried, then the Switch Protocol must activate so Bill can try again via different methods. Bill must be thorough at trying all bytes. After trying all bytes, restart or reset via this Switch Protocol. This Switch must activate the Switch Round that attempts to re-mark tried bytes to be untried and Switch must attempt a quick scan or run through untried bytes via one fast round. After that, Bill must continue via different methods. Jordan can help when needed.

Switch Round
The Switch Round must try to rescue all remaining bytes in record times via the fastest speeds, biggest cluster sizes, etc. The Switch Round should extend if it is the fastest option. The Five-Minute Blitz idea you mentioned is dangerous if Bill is rescuing 20 MB/s say for example. As long as the Switch Round is the fastest option to rescuing all the bytes, Switch could continue. If Bill is not going super slow or stalling for a long time, the Switch Round could perhaps continue. Bill can loop through Scan modes, levels. The Switch Round can be the first round that Bill runs per disc. But the Switch Round can also be run at the beginning of each session or run. Timeout flags and other flags might be able to help Bill to end the Switch Round. Switch must try to rescue all bytes in under five consecutive minutes total. A Switch Round could perhaps be extended if it can actually rescue all bytes in under five hours. It is critical Bill does not end the Switch Round too early or too late. If a lot of progress is being made, Switch can run a little longer. But eventually, Bill should probably end Switch and rotate through different modes, levels, flags, speeds, clusters, settings, options, tactics, stages, rounds, methods, etc. Switch Round should probably use the fastest speeds and biggest clusters to mirror what I did a few days ago with capturing almost 80% in like an hour. The idea for Switch has two parts. First, to re-mark bytes to untried. Second, to quickly probe the untried. I'm a little bit hesitant to suggest divorcing these two parts of Switch to run them separately, that is why I generally prefer the two parts of Switch stay married together if possible. The second part of Switch attempts to quickly rescue the untried again. But if Switch ends, Bill must continue rescuing the untried via other Scan methods if possible until the Untried drops to 0. After that, Bill probably should activate Switch to restart the process all over again, assuming that is the best option.

Last Resort Policy
The purpose of flags like -e would be to help run through the untried assuming Bill is unable to simply probe the untried after five hours. Correct me if I'm wrong but there might be many ways to push Bill to probe the untried via different methods per run. It seems that flags like -O and other flags might be better as a last resort. It seems Bill has many options to rescue 80% to 100% before resorting to tougher tactics normally. That is why I recommend tougher flags be reserved after other options stall for ten full runs. There are many flags out there which might sometimes include maybe -d and -R and many other flags, some flags might be needed sometimes, some flags should be reserved for after other methods results in prolong stalling or when it seems Bill is only rescuing like 1 byte per hour or a very slow speed, assuming Bill tries all other options, assuming options are not boosting speeds enough, then resort to tougher options. Remember the Refresh and Housekeeping protocols we talked about for weeks.

Scan Loops
By default, Bill should loop through the Scan Loops before switching to Trim, Scrape, Crawl, Merge, Fill, etc. Within the first Scan Loop are the Scan Modes. Inside each Scan Mode are worlds. Each world houses level. Inside each level can be infinite rounds. In a sense, Bill could loop within rounds, levels, worlds, but also modes. Once Bill runs through all of the Scan Modes one time, then that completes the first Scan Loop. If Bill retries the Scan Loop, Bill should begin again afresh at Mode 0: World 0: Level 0: Round 0 but perhaps with the -d --idirect and possibly other flags too like -R, -O, etc. I prefer -d for Scan Loop 2 by default. Perhaps, Bill will feel the urge to activate -d before Scan Loop 2. Each Scan Loop can be different. Bill can activate -d before Scan Loop 2 but -d and other flags should generally be reserved until Scan Loop 2 or Scan Loop 3, etc. Bill needs to be smart enough to activate any flag when needed. But by default, Bill should first be hesitant to avoid bringing some flags out too early or too often or too much. Jordan is supposed to check the Map, Dmesg, etc, between each round, in order to help Bill decide when to bust out tougher flags and settings. Trim can also have a loop if need be. But the focus is on the Scan Loop because many discs might hit 99% rescued while in the Scan Loop. Trim, Scrape, etc, might only come out after 99% for many discs.

Switch Round
The run_switch_round should activate per session and run. To be clear, Switch Rounds must not be triggered each Scan Loop. Please don't conflate between these things. Bill must probe through an entire run (pass) per round potentially. But flags/settings/Bill might stop rounds. Bill must continue trying to run through all bytes. When Bill runs out of bytes to probe, then Bill must active the Switch Round to re-mark all remaining non-rescued bytes. Bill can also re-mark at the start of each session too.

Output
Give me block codes to fix the following problems. First, lasers must rest for ten minutes after Bill is running for one hour. But Lasers-Clock start when an active current live Bill-Session is started in the Terminal but then the Lasers-Clock must end when Bill is terminated in the Terminal too. Second, it said, "3751919616 bytes (80.25%)" rescued. But it previously said "3G (3873245184 bytes) (82.85%)" rescued. Third, output also said, "/home/a/dvd_recovery.sh: line 36: run_switch_round: command not found." Study files and output. Bill should activate Loop 0: Mode 0: World 0: Level 0: Round 0 when a Bill-Session is initiated in the Terminal, and/or that first round may or may not be the same thing as the Switch Round. The current version of Bill made the Switch Round a separate entity it would seem which is okay as long as it rescued 100% of all the bytes of all discs, what matters are the end-results. I prefer if the very first round 0 and/or the Switch Mode be the very fastest with the highest settings which may contain the highest clusters and the highest speeds might be 25M and/or I've debated with Gemini for months about what the highest speeds might be. But last few days, Gemini was saying 25M might be the best option. By default, Bill slides from higher to lower settings. Bill can pick which levels to play. One idea for different levels might be different jump/skip/hop/leapfrog/teleporting sizes. By default, Bill should play level 0 at the beginning of a session after the Switch Round and/or the Switch Round is level 0. Loop 1 (the second loop of the Scan Loop) may want to consider the error flags and many other flags if they have not been used in the first loop.

Jump Protocol
Big to Small. Generally, Bill prefers fast to slow. Bigger jumping might minimize slow. Gradually, Bill can jump smaller and smaller. But at first, Bill is trying not to slow down. Jump means hop, leapfrog, teleport, skip, jump forward.

Gambit Protocol
Big to Small. Bill wants to maximize his gambit each session and run. When a session starts, Bill wants to play at the highest level so to speak, the fast speeds, the biggest clusters, the biggest baddest settings. Bill is playing chess and poker. In general, Bill wants to play the strongest move that might win Bill the game. A run is a full pass through all non-rescued bytes. Over time, Bill lowers the volume to the settings, the flags, and even the Jump Protocol. Bill transitions from the Telescope to the Microscope. But Bill by default wants to put troops on all the continents like it's the Risk board game. The opening gambit per session and run attempts to win all the remaining bytes in seconds. But perhaps timeout flags and/or different settings and protocols might bail Bill if the Gambit isn't rescuing all the bytes. In theory, the Gambit (also called the Switch Round) could last seconds or even hours. If it's the best move, Bill should stay. If not, Bill should go. That goes for any round or anything Bill is doing at any time. If what Bill is doing is the best thing, Bill should do that forever. If not, Bill should stop and do something else. If Bill needs to stop every five seconds, that might be good. If Bill is making amazing progress doing something, then maybe Bill should do that for hours and hours. As long as Bill tries to do the best things from big to small that has the highest probability of winning and rescuing all the bytes. Bill must activate the Housekeeping Protocol sometimes.

12:35 AM
Tracy Morgan sure aint no Adam Sandler. Tracy is interesting but not like a super star it would seem. I find him to be like an over the top stereotype character.