(01-17-2019, 09:53 AM)RTBoss Wrote: Do you still run 1 week on, 1 week off, like you did with other 5.5G subs? Or are you following the SASRB Shannon set?
Excellent question. 
And pertinent, as I'd been comparing this run against past DMSI runs in today's earlier post. Thanks for pointing it out.
When I was running those past 5.5G subs (including prior DMSI versions that I'd run), there was no SASRB yet, modeled or otherwise. All that I knew at the time was that I was stuck in input mode and not executing anything until I took time off. So I set my time-off schedule for myself.
My SE, PTPA, and USLM1 runs were closer to my old instinctual "Am I stuck in input mode?" determination, but I also wasn't really documenting those, so I wasn't concerning myself with tester reporting. I took personal responsibly for that and was pleased with the results. I did run those with the recommended number of loops and without breaking primary ASRB. It was only SASRB where I was running on my own schedule.
For 3.3, though, especially since I didn't want to break FRM's momentum, I'd adhered strictly to the directions for the first few weeks, up until socializing became a scheduling conflict. My option was to go to my first social event since starting 3.3 or not to go out at all. I chose to go out. That delayed my break by one day. That following week was the moodier week that I'd described in my last post. To get things onto a more convenient schedule in the future (although 3.3.1 will probably saddle us with different loops and SASRB), I also spent an extra day on, pushing my days off to Friday and Saturday for social convenience ahead of this weekend.
So I've mostly stuck to the SASRB instead of following my pre-SASRB input/execute instincts. By my past standards, I may have been stuck in input mode longer and executing for fewer days than on previous versions, which could explain some of the difference in my execution. But, 3,3 is a different level of 5.5G than 3.1 was, so it may be apples and oranges at this point, just like it was when I first started needing to take breaks to execute. I could rely on my instincts, but, for this run, generally speaking, I haven't been.
And pertinent, as I'd been comparing this run against past DMSI runs in today's earlier post. Thanks for pointing it out.When I was running those past 5.5G subs (including prior DMSI versions that I'd run), there was no SASRB yet, modeled or otherwise. All that I knew at the time was that I was stuck in input mode and not executing anything until I took time off. So I set my time-off schedule for myself.
My SE, PTPA, and USLM1 runs were closer to my old instinctual "Am I stuck in input mode?" determination, but I also wasn't really documenting those, so I wasn't concerning myself with tester reporting. I took personal responsibly for that and was pleased with the results. I did run those with the recommended number of loops and without breaking primary ASRB. It was only SASRB where I was running on my own schedule.
For 3.3, though, especially since I didn't want to break FRM's momentum, I'd adhered strictly to the directions for the first few weeks, up until socializing became a scheduling conflict. My option was to go to my first social event since starting 3.3 or not to go out at all. I chose to go out. That delayed my break by one day. That following week was the moodier week that I'd described in my last post. To get things onto a more convenient schedule in the future (although 3.3.1 will probably saddle us with different loops and SASRB), I also spent an extra day on, pushing my days off to Friday and Saturday for social convenience ahead of this weekend.
So I've mostly stuck to the SASRB instead of following my pre-SASRB input/execute instincts. By my past standards, I may have been stuck in input mode longer and executing for fewer days than on previous versions, which could explain some of the difference in my execution. But, 3,3 is a different level of 5.5G than 3.1 was, so it may be apples and oranges at this point, just like it was when I first started needing to take breaks to execute. I could rely on my instincts, but, for this run, generally speaking, I haven't been.
