Comment by tzs
13 hours ago
It says "512 MB RAM, 1 vCPU, 20 GV SSD" and "General Purpose". It was whatever was the cheapest when I made it.
Looking at the instance creation page it looks like it is no longer available. The cheapest now has 2 vCPU and the same other specs.
If anyone would like to run it on something else for comparison I've put it Pastebin [1].
Normally, a script converts the puzzle into a header file that describes the puzzle in terms of the data structures the solver uses, and then the solver is compiled with that header included via #include, but for benchmarking I manually included the header, so it is just a single C file that you simply compile and run. Add a -q flag to have it just find and count the solutions but not display them. For this particular puzzle it is fine to let it show the solutions. For some puzzles with a ton of solutions it displaying them can take significant time.
If anyone actually wants a Pips solver to solve Pips puzzles, there's a copy of mine along with the scripts that convert puzzles from the JSON format the NYT provides for download to the header file for the solver and some other stuff as a shar archive on Pastebin [2]. Pastebin's download link messes up something with that, so click the raw link and copy/paste from the browser.
Note: I'm still doing a lot of experimenting with it, both in the solving algorithm and in how the display the results, and am not at a point where I'm able to accept outside contributions. There are other Pips solvers that have been put on Github (and even posted on HN) that are (1) more sophisticated than mine, and (2) almost certainly more open to contributions. Just use mine if for some reason you want a fairly simple (aside from the damn display stuff...) brute force solver in C and aren't going to expect anything else from me :-)
Fun!
Interesting username