10:47 AM
Dear Gemini
It seems you are misrepresenting the data I showed you, the biggest thing is the current rate is 0 B/s but was going at around 10 MB/s as it went up to 791 MB in under 10 minutes but current rate is now under 1 MB/s, it might be due to the cops and/or many reasons. On top of that, it looks like Gemini corrupted the map file again like many times for weeks, Gemini breaks Bill which results in the map file breaking resulting rescuing process starting over even as dvd.iso is already 4.7 GB. Before you wrote 53.3, here was the output, Bill was rescuing at around 10 MB/s for almost ten minutes but then it dropped to 0 B/s for the last 11 minutes, there might be many reasons why it dropped to 0 B/s and not simply 1 B/s or something slow. Also, it said 16.95% rescued but the previous percentage was almost 80% but Gemini/Grok may have caused the map file to break.

02:51 PM
I had Gemini create a DVD Bill Map Generator file. Currently running that. To be clear, it was mostly only at 8 MB/s and it peaked above 10 MB/s a little here and there. Currently it is at an average of 6 MB/s at 8 minutes running with 2879 MB generated. It was only at around 15 MB/s for less than like ten seconds is my guess. Probably under 10 MB/s 50% of the time so far. It sounds like the drive is stopping and going now at 11 minutes. The average is now under 5 MB/s.

05:18 PM
Super Man Protocol
Write the Super Man Protocol, unless if Bill can already do it, Bill must be able to either re-mark sectors when Bill needs to and/or switch to other rounds, levels, worlds, modes. Specifically, if there is nothing to do, either Bill can try to like re-mark the sectors or Bill should probably switch. Make sure Bill can either re-mark or switch to other rounds, levels, worlds, modes. For extra credit points, you could add a condition if possible to push Bill to either re-mark or to switch especially if the error rate average doubled or if the read rate average decreased by 50%. The challenge with writing this is it might cause Bill to run around unable to finish rescuing the final bytes which means the Super Man Protocol should probably turn off if 99% of a disc is rescued or in certain conditions where Bill is just switching all the time unable to get anywhere.

Turtle Protocol
Write the Turtle Protocol which is a contrast to the Super Man Protocol, the Turtle Protocol pushes Bill to finish the current project. For example, for a new disc, the default first project via Perfect Mode: World 0: Level 0: Round 0 would be to Speed Scan and hopefully Speed Rescue all the bytes in under five minutes or at least under an hour or as fast as possible. Each level can have infinite rounds. The Turtle Protocol demands infinite infinite rounds until the current project is done. But once all bytes are scanned (0 non-tried bytes remaining), then Bill should progress to the next hierarchical tier. The Super Man Protocol has the power to escalate, that is to intervene, if need be. There is also the Coffee Protocol you wrote earlier as well. If need be, protocols can move Bill to do other projects. For example, in Trim Mode, the project would be to try to trim all the bytes. In Scrape Mode, the project would be to try to scrape all the bytes. The purpose of the Turtle Protocol is to push Bill to finish projects if Bill can. The Super Man Protocol might or the Coffee Protocol might urge Bill to switch. But by default, if Bill can, Bill should try to finish the current project via infinite rounds before switching to other levels, worlds, modes. The stalling system could push Bill to abandon the Turtle Protocol to switch to other hierarchical tiers. The Turtle Protocol must be designed to keep Bill balanced as the Super Man Protocol might prevent Bill from finishing projects.

Stall Protocol
Write the Stall Protocol to push Bill to the next hierarchical tier if stalling too long. Define stalling as not rescuing new bytes. By default, all hierarchical tiers must loop from the last one to the first one. Rounds are infinite per level. Level 9 must loop back to level 0. World 3 must loop back to World 0. Mode 4 (Crawl Mode) must loop back to Mode 0 (Perfect Mode). If 100 consecutive round stalls, switch to the next level. If 10 consecutive level stalls, switch to the next world. If four consecutive world stalls, switch to the next mode. The Turtle Protocol pushes Bill to finish projects before switching to the next level, world, mode. This Stall Protocol functions like a backup plan in case the Super Man Protocol or the Coffee Protocol doesn't end up pushing Bill to switch. The Turtle Protocol pushes Bill to switch only after fully running through the current said project. The purpose of these protocols is to push Bill to continue running through different tactics in a desire to rescue all the bytes. Make sure stall counters in the scrolling non-clear Terminal monitor resets to zero when bytes are being rescued. When bytes are being rescued, then it is by definition not stalling.

Error Protocol
Remaining Time counter is broken. It seems to be just jumping from one level to the next level per round, why? Write the Error Protocol. If 0 bytes are read along with an error rate for ten consecutive rounds, switch to the next level.

11:58 PM
Time remaining counter at the top is broken. Error Protocol counter did not reset even at 12/10. Eventually the counter did reset when rescuing bytes. The rounds stall counter and error counter match at 31 but the first is 31/100 and the second is 31/10. It says, "STALLS: R:31/100 L:0/10 W:0/4 | ERR-PROT: 31/10." I don't want that. Trim Mode | WORLD: 1/4 | LEVEL: 0/9 with -d --idirect -c 2048 --no-scrape -M ran with 341 B/s error rate and 0 B/s averate read rate which failed to trigger the Error Protocol or the Super Man Protocol.

08:19 PM
Dear Gemini
Levels could be built around major themes. I like the modes and worlds I designed. To built on top of that design, the question would be what what are all the themes out there. One theme might be the --min-read-rate flag. Talk to me about different strategies for the read rate because I would do a minimum of 100m for perfect mode and 30m for scan mode. I don't think 100m is literally possible but Gemini suggested it. Perhaps 100m would just push the drive to go as fast as possible. The limits for my discs and drive right now might be under 25m or at least most of my discs. Therefore, 30m might be identical to what 100m tries to do. In the past, I would have Gemini write several speeds where Bill would start with the fastest speeds like 30m for a minimum read rate and gradually go to lower speeds like 20m, 10m, 1m, and so on. That is one tactic. Another tactic might be the reverse of that. First off, perhaps not using --min-read-rate flag might do better in some cases than 30m or 100m. Beyond that, perhaps a lower rate might help if it saves overall time in trying to rescue many bytes. I don't know the math, the averages, the probability, etc. Talk me through different tactics as it relates to different --min-read-rate flags speeds, settings, the debate on when to use the flags versus NOT using the flags, whether to start at lower speeds or higher speeds, talk about the pros and cons between different approaches relating to these types of flags and themes.

09:06 PM
Dear Gemini
Write instructions for Gemini for writing Bill to develop the Speed Switch which will also be called the Max Per Hit (MPH) as a parody of Miles Per Hour. Instead of pinning and fixing the --min-read-rate flags to specific modes, worlds, levels, or even rounds, keep the MPH gauge pinned to the Speed Switch. The challenge is writing triggers, the if this then that part of the code, I would love if the MPH could change even during rounds but I would settle for having the MPH fluctuate per round at the very least. The challenge like I said is in determining which variables might trigger the MPH to go up and down. I want the MPH to free to fluctuate between any round, level, world, or even mode. There are probably millions of ways to write code for a system as complex as this gauge. In my head, I can think of many different ways to writing MPH. There are many challenges as many things can go wrong with a MPH system like this one. Before I decide to give you all of my many ideas relating to MPH, I want to give you Gemini an opportunity to write as much as can as it relates to this. The following speeds:

30 MPH: --min-read-rate=30m
20 MPH
15 MPH
10 MPH
9 MPH
8 MPH
7 MPH
6 MPH
5 MPH
4 MPH
3 MPH
2 MPH
1 MPH
900K MPH
800K
700K
600K
500K
400K
300K
200K
100K
90K (with --timeout=5s perhaps)
80K
70K
60K
50K
40K
30K
20K
10K
5 K
1 K
500B
100B
1B
No flag null

Those are suggested speeds. And/or think about what if sometimes the MPH could be determined based minimum, maximum, and/or average speeds. So say for example if Bill is reading at 226.34567 kilobytes per second, what if the MPH Speed Switch locked onto that rate as to try to force that speed to continue for a period of time as to try to skip over slower spots.

In writing a MPH system, it can be challenges, many moving parts, many risks. One of the questions might be relating to which routes might save more time. To use an analogy, the turtle won the race because the turtle was consistent. The turtle was slow but was focused. The rabbit might be faster but might end up on roads that are thousands of times longer. What is tough is you may not know which routes the turtles and rabbits might take resulting in a hard time knowing how to do the math in guessing probabilities between different approaches. The rabbit might not only be on a longer road but might also stop and go more. Each time the rabbit stops, the rabbit might be wasting time. Perhaps a good MPH system needs a default route that takes in account all of these factors to come up with a balanced compromise that is founded on the highest probability of working, that is efficiency, effectiveness. The default MPH might be to start on off mode. However, I don't totally know as most of my discs probably have many scratches on them which sort of makes me want to focus on flying by as many scratches at the beginning as I can. But I know some might have only a few scratches. So, trying to create a universal Bill might be very challenging to do.

10:29 PM
If a 4.7 GB DVD has 400 MB of bad sectors in 4,000 spots all over the drive. Talk about everything that might help and hurt me in this type of situation, talk the pros and cons, all of the flags, speeds, settings, the cops, the variables, etc.

Shine bright while you're shooting for the stars because you might get stuck up there. Might as well make it count.