Hello everyone,
It's been a while, so I thought I should update the group on my progress wi=
th my paper. Obviously, I didn't finish it over Spring Break! I have once=
again been distracted by school and other projects, but now that summer is=
starting I plan to return to it as soon as possible. I have completed 7 o=
ut of 13 sections, and have tried to ensure that everything is as clear and=
accurate as possible. Roice has helped me very much in this regard, provi=
ding many corrections and suggestions, and in one case completely eliminati=
ng a line of reasoning that I had come up with, so my thanks go out to him.
I am still planning to write a paper on the n^5 cube and to try to discover=
an n^d formula after this paper is completed. I am hopeful that the paper=
and my other work will be a positive contribution to the group, and that t=
he paper will shed some light on my formula for those who choose to read it=
.
Also, thanks Roice for letting us know about the void and mirror cubes, I'm=
going to get both of them! I also like the idea of solving the mirror cub=
e blindfolded, Melinda.
I look forward to sharing my paper with everyone, hopefully it will not be =
too much longer. :)
Best wishes,
David
Hello all,
I just wanted to let everyone know that I have made some minor clarificatio=
ns and corrections to the 4^4, 6^4, and 8^4 Cube sections of my paper. Als=
o, I realized that the link I provided for my formula in my last post was n=
ot the most convenient, here is an updated link:
http://www.gravitation3d.com/david/n%5E4_Cube.pdf
Thanks everyone!
All the best,
David
--001485f040a4287009046cfd59da
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Dear All,
I got a stomach sinking email today from a member who accidentally overwrote
an almost completed solution in Magic120Cell. 17000 moves had been done.
MC5D and Magic120Cell do not make any automatic backups of log files
(something I now plan to change). When using MC4D, I've always made copies
of my log files at milestone points from paranoia, and I think this is a
good habit when investing so much effort in a solution.
As with many programs, be aware that using "Save" instead of "Save As..."
can be dangerous if you are not making log file backups yourself. What
happened in this case was that the puzzle type was switched to investigate
something (which reset the state in the older version of the program being
run), then "Save" was used. In the version that has been online since
September, you'd have to go more out of your way for an accidental overwrite
like this because changing the puzzle type no longer resets the state.
You'd have to manually reset the state from the options menu, then save.
That behavior is perhaps reasonable, but I will also make the program more
defensive by making "Save" do a "Save As..." if the puzzle has been reset.
Thoughts on other ways to improve the defensiveness are welcome, but I
wanted to send out this notice to help avoid this happening (I really hope
to avoid this kind of grief again). I also encourage people to make sure
they have the latest versions if they are actively working on solutions.
Take Care,
Roice
--001485f040a4287009046cfd59da
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable