Non-Deterministic Solution Order

[DougCube]

At least with using --alloptimal option, I have noticed that the output varies from run to run (with identical inputs). It does not appear to be deterministic. I'm guessing this is from the multi-threaded code. This makes it more difficult to debug problems in wrapper programs/scripts that use the output of this tool. Not sure if this issue is well known. Not sure if there should be an option to force a fixed order or if that would hurt performance too much.

[rokicki]

This is a common side effect of multithreading. Use -t 1 to single thread it. Or sort the output solutions yourself. - https://cube20.org/ <http://cube20.org/> - https://golly.sf.net/ <http://golly.sf.net/> - https://alpha.twizzle.net/ / -

…

On Tue, Dec 17, 2024 at 4:02 PM DougCube ***@***.***> wrote: At least with using --alloptimal option, the output varies from run to run (with identical inputs). It does not appear to be deterministic. I'm guessing this is from the multi-threaded code. This makes it more difficult to debug problems in wrapper programs/scripts that use the output of this tool. Not sure if this issue is well known. Not sure if there should be an option to force a fixed order or if that would hurt performance too much. — Reply to this email directly, view it on GitHub <#71>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMOLS6UGWPFF53X6KUYKRD2GC3R3AVCNFSM6AAAAABTZQXBPKVHI2DSMVQWIX3LMV43ASLTON2WKOZSG42DMMZXG42DQMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>