Tomas Rokicki

Ahh, you raise a good point. Two, in fact. But I don't like the "default" (no distinguish-all) to calculate "impure" orders as I think that's a special case and dependent...

To generate the "additional" moves, we need to know the order of a move (so we know what additional moves to generate), and an empty (null) move has 0 order,...

The intent is that all the moves remain in the .tws file, and you use --moves to restrict the move set for solving/searching. But all moves from the .tws file...

Bottom line is, I fail to see justification for "null moves" in .tws files. Given our discussion, can you motivate the need for these? On Thu, Nov 9, 2023 at...

Understand. And interestingly I am also working on the same sort of thing, perhaps even for the same puzzle! Generally what you want to do is leave the .tws file...

The --omit is exactly for this case. You can --omit CORNER_EDGE --omit PIECESET33 --omit FOOPARITY99 or whatever else you need. But you can also get the *effect* of --omit in...

This is unfortunate. I understand why this happens, but I don't have an excellent fix for you. A workaround is, instead of using --omit, use identical pieces and orientation wildcards...

Sorry about that. I'm working on a fix, but it won't be coming along for a bit. In the meantime, you can do what you want fairly easily (but it's...

Wow, what a well-thought-out and carefully written proposal! The main drawback I see is that twsearch is intended to be very general, and at the moment to do this it...

Here's a link to join the slack (this can also be found on the "New Issue" page on cubing.js). https://join.slack.com/t/cubing-org/shared_invite/zt-8ok0y7cl-CffvDqFxnp9LheabPzmfgw -tom On Mon, Jul 11, 2022 at 2:00 AM Gregor...