newtonbase
Premium Member
It does make life a lot easier though after a while you don't have to use it consciously. You just know.I didn’t know this little trick! Nice.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.

It does make life a lot easier though after a while you don't have to use it consciously. You just know.I didn’t know this little trick! Nice.

Yes, whenever you have odd number of targets, you have to do parity.
FYI,
1) if you have odd number of corners, you should have odd number of edge targets. (Exception - some people do swap of two edges to make them even but don't worry about it for now)
2) Number of targets:
- Corner : 7 - solved or twisted pieces + number of cycle break
- Edge: 11 - solved or flipped pieces + number of cycle break
Since you had 9 corner targets, that means you had 2 cycle breaks. But you said only one cycle break - I guess you used OP for corner twist.
So, my guess, you had one corner twist, one cycle break = 7 - 1 (twist) + 1 (cycle break) = 7 targets. (taking out two from the twisted targets).
I can only speak for myself, but for me it's not really counting at all, at least not with arithmetic.The "running sum" is better thought of as a "decreasing sum."
I can only speak for myself, but for me it's not really counting at all, at least not with arithmetic.
I do edges as audio with 4 letter words. A single 11 edge cycle would be two 4-letter words and a 3-letter word, so that's my default "target". Each time I hit a cycle break my target gets longer - so after the first break I'm expecting there will be three 4-letter words, etc. If I am expecting three four letter words and I hit the buffer piece when the last word has only two letters, I know I'm looking for two spare edges. If I then see one solved, I know I'm looking for another one solved or flipped, etc. I'm never really thinking 12 or 13; only where I am relative to my initial target of 4/4/3.
I can only speak for myself, but for me it's not really counting at all, at least not with arithmetic.
I do edges as audio with 4 letter words. A single 11 edge cycle would be two 4-letter words and a 3-letter word, so that's my default "target". Each time I hit a cycle break my target gets longer - so after the first break I'm expecting there will be three 4-letter words, etc. If I am expecting three four letter words and I hit the buffer piece when the last word has only two letters, I know I'm looking for two spare edges. If I then see one solved, I know I'm looking for another one solved or flipped, etc. I'm never really thinking 12 or 13; only where I am relative to my initial target of 4/4/3.
I don't do the maths either any more. It's more like "That seems a bit short"@newtonbase / I don't count it any more but actually, and also in general (can't define the scope of general, though), we (or I) consider flip/twist same as solved when it comes to counting target numbers - at some point, number itself doesn't matter - more to check whether the tracing has been completed or not. At the end of each memo, when there are flips or twists, just add corresponding letter pairs or just visualize them (especially for 3BLD).
What about other folks?
I do the same; twice in the weekly competition this week that led to a DNF for me. :-( So, especially for big cubes BLD, it is probably worth it to keep doing the calculations, unless you're one of the top folks going for WR. A few extra seconds to prevent a DNF is likely worth it.I don't do the maths either any more. It's more like "That seems a bit short"
I do use the maths on 4BLD wings as it's too easy to miss a small cycle. Fingers do the job on centres.I do the same; twice in the weekly competition this week that led to a DNF for me. :-( So, especially for big cubes BLD, it is probably worth it to keep doing the calculations, unless you're one of the top folks going for WR. A few extra seconds to prevent a DNF is likely worth it.
I do use the maths on 4BLD wings as it's too easy to miss a small cycle. Fingers do the job on centres.

I'm looking forward to this. Glad it will be mobile compatibleI've made some adjustments to the letter pair images app from testing on my phone. I want to make sure it's usable on mobile first, desktop is a lot easier to pretty up as long as everything fits on a phone. I have UI elements in place to delete individual images and set them private/public (would allow you to skip certain records from exporting/sharing). They're not wired-up yet or aligned nicely, but they're in place.
Still a lot of bullet points before feature-complete but there is solid progress. Current image search list in a modal:
View attachment 9349
I'm looking forward to this. Glad it will be mobile compatible
I've made some adjustments to the letter pair images app from testing on my phone. I want to make sure it's usable on mobile first, desktop is a lot easier to pretty up as long as everything fits on a phone. I have UI elements in place to delete individual images and set them private/public (would allow you to skip certain records from exporting/sharing). They're not wired-up yet or aligned nicely, but they're in place.
Still a lot of bullet points before feature-complete but there is solid progress. Current image search list in a modal:
View attachment 9349
Yeah, it's 2018 and this is a perfect fit for a phone app: it has to work well in a phone footprint. It's browser based so it should run anywhere you can run a compliant browser. I'll eventually set it up so you can create a home screen shortcut, making it behave more like an app without needing different versions per platform.
I'm in a rare window of opportunity where I can sink my teeth into this in lieu of work under the legit premise that it's going to bolster some areas that will help me a lot for the day job in the coming months. A labor of love is the best learning project. There's some family health stuff going on, adding a little chaos to the mix, but otherwise I've finally had the time to sit and hammer on this idea.
The main thing I want to be careful of is making sure it's flexible enough to be extensible in the future. This is a very niche app but there's also nothing at all like it out there or I'd be using it instead of writing it. It's already a spreadsheet-killer for me in its current state so it has the potential to be a must-have, albeit for a really small audience. I'm already very reliant on the data I have in this thing, once I release it into the wild then others may also. I want to make sure I think it through so we don't end up painted into a corner when it's time to add features.
It will run in Android, I hope? I would want it mainly for my ipad.