Oops
Oops
Hi Ruud!
I noticed a few minutes ago a change you may not be aware of. When optimizing in version 1.17 if the Analyze window was open it would update as the numbers changed.
In version 1.20 it does not.
Even at the completion the analyze window does not update itself.
I just installed the new version and noticed that it installs to a different directory, because of a space between "Sudoku" and "Cue" that was in version 1.17 but not in 1.20.
Thanks!
>>These are messages I emailed to Ruud, no reply after 2 days.<<
I noticed a few minutes ago a change you may not be aware of. When optimizing in version 1.17 if the Analyze window was open it would update as the numbers changed.
In version 1.20 it does not.
Even at the completion the analyze window does not update itself.
I just installed the new version and noticed that it installs to a different directory, because of a space between "Sudoku" and "Cue" that was in version 1.17 but not in 1.20.
Thanks!
>>These are messages I emailed to Ruud, no reply after 2 days.<<
Hi,
I found your mail between the tons of spam I receive daily.
It is easier to ask support questions here on the forum.
About the Analyze window.
I have split the old Analyzer into a new Status window (that keeps track of candidates group status) and the new Analyzer, that also has a detailed step list with alternative count and ratings. You have correctly found that the Analyzer is not correctly updated by the optimizer. I will fix that in the next version.
About the name.
There are several versions of the name in use. You are using "Sudoku Cue", but the name is "Sudo Cue". Because the website also is named SudoCue, I decided to drop the space, so a single name could be used for both the software and the website.
Ruud.
I found your mail between the tons of spam I receive daily.
It is easier to ask support questions here on the forum.
About the Analyze window.
I have split the old Analyzer into a new Status window (that keeps track of candidates group status) and the new Analyzer, that also has a detailed step list with alternative count and ratings. You have correctly found that the Analyzer is not correctly updated by the optimizer. I will fix that in the next version.
About the name.
There are several versions of the name in use. You are using "Sudoku Cue", but the name is "Sudo Cue". Because the website also is named SudoCue, I decided to drop the space, so a single name could be used for both the software and the website.
Ruud.
Thanks, I shall use this forum rather than email. I get spammed too much as well.Ruud wrote:Hi,
I found your mail between the tons of spam I receive daily.
It is easier to ask support questions here on the forum.
I just saw another curious thing. This "puzzle" below when solved by Sudoku Cue shows "This puzzle has no solution" and yet it is solved.
...75.....3..48.2.1.......6.4......879.....312......7.5.......7.8.32..4.....69...
That is with brute force off, if that matters?
Thanks!
Solver options
My experience with using Sudoku Cue to solve puzzles suggests that the settings for the solver are "read" when the puzzle is loaded rather than when the solve is requested, with the exception of Brute Force.
I note that because if a puzzle is unsolvable and I change the solve settings it does not change what the solver can solve, unless brute force is allowed or unless the puzzle is reloaded.
The restart button does work around that, as long as I remember to press it!
I would prefer that the solver settings be updated when you toggle the setting, if you can work that in?
Thanks again for your prompt attentions!
I note that because if a puzzle is unsolvable and I change the solve settings it does not change what the solver can solve, unless brute force is allowed or unless the puzzle is reloaded.
The restart button does work around that, as long as I remember to press it!
I would prefer that the solver settings be updated when you toggle the setting, if you can work that in?
Thanks again for your prompt attentions!
That is a very good idea.zoltag wrote:I would prefer that the solver settings be updated when you toggle the setting, if you can work that in?
I often have to change the solver settings to test a particular puzzle to see what solving techniques are really required and which can be ignored in the solving path. Immediate re-solve after changing the solver settings would save me a lot of time too.
Thanks.
Ruud.
Hi Ruud,
I use optimize frequently. I have bugs and uniqueness turned off and am creating unsolvable puzzles. I tried this puzzle (one of my own).
Version 1170 gives an identical invalid result. 1170 settings were seafood up to jelly, subsets up to triple, no: brute force, uniqueness, coloring, templates , tabling.
Oops again.
I just hit optimize (by mistake) on an empty grid and that mostly crashed SQ.
I use optimize frequently. I have bugs and uniqueness turned off and am creating unsolvable puzzles. I tried this puzzle (one of my own).
Code: Select all
1 . . | . . . | 4 . .
. 2 . | 7 . . | 6 9 .
. . 4 | . 9 . | 3 8 7
---------------------
. 3 . | 6 . . | . . .
. . 5 | . . . | 8 . .
. . . | . . 5 | . 3 .
---------------------
9 4 7 | . 1 . | 5 . .
. 5 3 | . . 2 | . 6 .
. . 6 | . . . | . . 8
Oops again.
I just hit optimize (by mistake) on an empty grid and that mostly crashed SQ.
It has been a week, no response. PING!
zoltag wrote:Hi Ruud,
I use optimize frequently. I have bugs and uniqueness turned off and am creating unsolvable puzzles. I tried this puzzle (one of my own).Version 1170 gives an identical invalid result. 1170 settings were seafood up to jelly, subsets up to triple, no: brute force, uniqueness, coloring, templates , tabling.Code: Select all
1 . . | . . . | 4 . . . 2 . | 7 . . | 6 9 . . . 4 | . 9 . | 3 8 7 --------------------- . 3 . | 6 . . | . . . . . 5 | . . . | 8 . . . . . | . . 5 | . 3 . --------------------- 9 4 7 | . 1 . | 5 . . . 5 3 | . . 2 | . 6 . . . 6 | . . . | . . 8
Oops again.![]()
I just hit optimize (by mistake) on an empty grid and that mostly crashed SQ.
Sorry,
I missed you post completely. Thanks for the ping.
A new version is released soon. There are several enhancements and fixes to the optimizer included in this fix. I will post a message here when it is available. Meanwhile, I will try to see if I can reproduct your error, or that it is already fixed in my version.
Cheers, Ruud.
I missed you post completely. Thanks for the ping.
A new version is released soon. There are several enhancements and fixes to the optimizer included in this fix. I will post a message here when it is available. Meanwhile, I will try to see if I can reproduct your error, or that it is already fixed in my version.
Cheers, Ruud.
zoltag wrote:I noticed today that hitting the optimize button on any puzzle (even valid ones) that the current settings cannot solve crashes the program.zoltag wrote: Oops again.![]()
I just hit optimize (by mistake) on an empty grid and that mostly crashed SQ.
Thanks so much for your prompt response. You are so on top of everything! I now realize that you do not require user input.
As you may have noticed, I'm not always so "on top of things".
I have been very busy developing the new SumoCue program for Killers and Jigsaws. I'm also supplying puzzles to magazines. Had to complete a few large orders.
I read your previous post and planned to answer later, but forgot about it. I hope you do accept my apologies (again)
Here is the answer:
Thank you for reporting the error. I have rewritten a great part of the optimizer, which no longer causes any problems. I'm not releasing this version yet, because I want to do a few more tests on other changes I made. With more than 5000 installs, I have to be careful not to mess up new releases. My hosting service will probably shut my site down if I do 2 releases per month.
So your problems are already addressed and will be available in the next release of the free program.
cheers,
Ruud.
I have been very busy developing the new SumoCue program for Killers and Jigsaws. I'm also supplying puzzles to magazines. Had to complete a few large orders.
I read your previous post and planned to answer later, but forgot about it. I hope you do accept my apologies (again)
Here is the answer:
Thank you for reporting the error. I have rewritten a great part of the optimizer, which no longer causes any problems. I'm not releasing this version yet, because I want to do a few more tests on other changes I made. With more than 5000 installs, I have to be careful not to mess up new releases. My hosting service will probably shut my site down if I do 2 releases per month.
So your problems are already addressed and will be available in the next release of the free program.
cheers,
Ruud.