
3x3::k:4608:4608
Probably a Tag Team challenge
Ruud

Untrue with the upcoming version of JSudokuCathyW wrote:I wish you luck guys. I tried the V2 using JSudoku and Sumocue to see if it was really worth spending time on. Got two placements as did Para (including the obvious at r5c5). Neither JSudoku not Sumocue can make another placement without brute force so I'm pretty certain I can't either.
Edit: removed JSudoku logJSudoku wrote:The grid is solved !
Jean-Christophe wrote:Here is the log without naked & hidden singles. I won't clean up the unnecessary moves. I've enough work with my own puzzles !
That's because it will exhaust all possible moves a technique may make before trying the next technique. It had to resort to several Complex XY-Chain to crack it. That's a new technique which is similar to mhparker's step 32.CathyW wrote:I look forward to it JC.![]()
There's a huge number of conflicting combinations for analysis in the log you provided. I'm not masochistic enough, nor do I really have enough time to spend on puzzles requiring such detail. Can mere mortals manage it without solver assistance? We'll see what Para, Mike and anyone else can come up with ...
OK I won't publish logs anymore. Anyhow, it's in tiny text and you don't have to read it!mhparker wrote:Bad move, JC, to post a JSudoku log whilst a tag solution is in progress.The whole point of a tag solution is that it should be a team effort, not an individual effort, as is usually the case with the V1's.
By all means, tell us in future right away if JSudoku can solve something, but please don't publish the log until we've found a solution (or given up trying to do so, as the case may be!). Thanks.
P.S. Yes, I'm very interested in the great work you've been doing, and look forward to analyzing the log, but only after trying a manual solution...
Thanks for pointing that out, JC. I've withdrawn the later steps. I must have been quite tired when I wrote that!Jean-Christophe wrote:Reading your walktrough, I cannot agree for step 35a