Fractionated Morse auto-solver issues.

[RanTheLab]

          Circling back to this one:

Today I'm working on this quote: I used some magic to make some fog laugh. It was mist tickle.

Here are some places where the auto-solver made decisions I didn't understand:
Key: HOMESICK
Crib: IUSED

• In this case, it predicts the keyword length to be around 2, which is going to be impossible at a glance.

This seems to have follow-on consequences for the possibilities it predicts for the letters between K and N - a human solver would know these have to stay within the first half of the alphabet. 

Same quote, key: FORECASTING
Crib: MAGIC

• Its initial suggestions of the letters that can appear between D and J is too wide a range. A human solver would know it should be letters that fall within the range surrounded by D and J.
• It also thinks D, B, and A are all likely to be in the keyword. A human would quickly decide that of these, only A is likely to be in the keyword.

This might be the same issue in two different instances, but I leave that to you.

Originally posted by @Agilus in #410 (comment)

[RanTheLab]

Thanks for the feedback.

For HOMESICK, the code algorithm 'approximates' the keyword length. It obviously isn't always accurate. I do know the keyword length, but let the algorithm display its approximation in the output. One (easier) thing I can think of is if the approximation is vastly different than the actual length, display a message (along the lines of 'Pick a different keyword/crib combination). The more difficult (and correct) approach is redesign the algorithm to come up with a better approximation, especially since I already 'think' K is in the keyword. The crib of IUSED isn't a great choice because it only gives 4 mappings, even though that crib covers 7 cipher characters, there are 3 Ms and 2 Rs.

For FORECASTING, the approximation for keyword length is 10, in reality it is 11. The letters between D and J are all possible. But then something goes horribly wrong that is a real issue.

This is going to take some digging into to get working, but we appreciate the feedback...it makes the tool better and that helps everyone!

[Agilus]

Thank you! I agree that the crib isn't great - that's why I opened a second issue about the suggested keyword length on these, because I was working along various axes trying to get the right difficulty level. It was a struggle to get this one where I wanted it this morning.

[RanTheLab]

I have the autosolver to the point were everything I have thrown at it can be solved. I have also upped the points scale so it is more in the range of 350-400, give or take.

[Agilus]

Has the points update been pushed out yet? I just created one that came up at 256 (242-282).