Re: 2nd Solve--LaGard 3330
Yes, you are correct to absolutely suspect that the low point you find during your check of the wheelpack every ten increments may turn out to be a gate. That's why I also do this:
flywheel wrote:5. Use step 3 low for W3, step 4 low point for W2, and brute force W1 in increments of 2 beginning with low spots from step 1
If you consider that each gate is approximately 3 increments wide, and you assume that your lock will read a single wheel when moving the entire wheel pack, you actually have a 30% change of catching a gate when you do the initial wheel pack map (you are actually checking 99,0,1 & 9,10,11 & 19,20,21, etc for a total of 30 increments checked). If, on your lock, two wheels can be read when the entire wheel pack moves, you can double that to 60% of finding a gate. Or to think of it another way, we use 2.5 increments as the standard when searching for a gate...that's 40 readings on the dial...so searching 10 increments is actually doing 25% of the total work required for a full spin around. Naturally, the world doesn't always follow these convenient probabilities, but the point is that those first ten readings are worth paying attention to even after you've found a gate!
Altashot wrote:Isn't it weird how it works sometimes?
Right?! I start a manipulation with a picture in my head of what is going to happen, and then all of a sudden the lock does something unexpected and the plan has to change! What's the expression? "No plan survives initial contact with the enemy..."