Hi everyone,
It has been a week since I solved 3^4 and then joined this group. I've alwa=
ys been loving the 4D geometry. For example, my desktop wallpaper is an exp=
loded view of the 120-cell, which was made by myself using Mathematica a fe=
w years ago. But this is the first time I actually play something in 4D. Th=
is is definitely a thrilling experience.
In this week I have solved the hypercubes from 2^4 to 5^4, and Simplex-2. A=
lthough I am only a beginner here, I would like to share some of my thought=
s. Melinda, thank you for encouraging me to do it.
Sometimes I build long algorithms based on short algorithms. Unfortunately =
when I record a macro, it is not allowed to call another macro. Here is wha=
t I did. I created an empty log file, performed all the turns in the long a=
lgorithm including calling macros, and saved the log file. I went into the =
log file, copied the sequence of moves, pasted it into the macro file, and =
added certain information like the name of the new macro and reference stic=
kers. I guess some people also do this. But I haven't found discussion abou=
t it. Maybe that's because I haven't read much in the archived mails.
When I solved 4^4 and especially 5^4, it was very hard to see and distingui=
sh 1C pieces. I really hope that I can toggle some buttons and choose to se=
e only certain types of pieces, like only 1C pieces. I've seen someone talk=
ing the same thing, and I know it's not trivial to add this feature. I woul=
d benefit a lot from this feature because my solution is type by type, not =
layer by layer. I found this feature in MC7D, but I don't understand how to=
make a turn in MC7D yet.
So what's next for me? I will not join the competition tomorrow because I d=
on't have time to prepare more macros and practice today. I don't want to m=
ove to 5D yet, because I'm not ready for the challenge of another dimension=
. I'd like to stay in 4D. I like to play more regular polytopes. But it see=
ms like among all six regular polytopes, only {4,3,3} and {3,3,3} can be fo=
und in MC4D. {5,3,3} is too daunting. Melinda has already warned me. {3,4,3=
} (24-cell) would be an interesting puzzle. Since it has no analog in all o=
ther dimensions. Even for tesseract, there are other ways to cut it. Like i=
n 3D, we have Skewb or helicopter cube. I really hope some day I can play t=
hem.=20
Nan
LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpPbiBG
cmksIDE3IFNlcCAyMDEwIDE5OjAwOjQyIC0wMDAwDQoic2NodW1hIiA8bWFuYW5zZWxmQGdt
YWlsLmNvbT4gd3JvdGU6DQoNCj4gU29tZXRpbWVzIEkgYnVpbGQgbG9uZyBhbGdvcml0aG1z
IGJhc2VkIG9uIHNob3J0IGFsZ29yaXRobXMuDQo+IFVuZm9ydHVuYXRlbHkgd2hlbiBJIHJl
Y29yZCBhIG1hY3JvLCBpdCBpcyBub3QgYWxsb3dlZCB0byBjYWxsDQo+IGFub3RoZXIgbWFj
cm8uIEhlcmUgaXMgd2hhdCBJIGRpZC4gSSBjcmVhdGVkIGFuIGVtcHR5IGxvZyBmaWxlLA0K
PiBwZXJmb3JtZWQgYWxsIHRoZSB0dXJucyBpbiB0aGUgbG9uZyBhbGdvcml0aG0gaW5jbHVk
aW5nIGNhbGxpbmcNCj4gbWFjcm9zLCBhbmQgc2F2ZWQgdGhlIGxvZyBmaWxlLiBJIHdlbnQg
aW50byB0aGUgbG9nIGZpbGUsIGNvcGllZCB0aGUNCj4gc2VxdWVuY2Ugb2YgbW92ZXMsIHBh
c3RlZCBpdCBpbnRvIHRoZSBtYWNybyBmaWxlLCBhbmQgYWRkZWQgY2VydGFpbg0KPiBpbmZv
cm1hdGlvbiBsaWtlIHRoZSBuYW1lIG9mIHRoZSBuZXcgbWFjcm8gYW5kIHJlZmVyZW5jZSBz
dGlja2Vycy4gSQ0KPiBndWVzcyBzb21lIHBlb3BsZSBhbHNvIGRvIHRoaXMuIEJ1dCBJIGhh
dmVuJ3QgZm91bmQgZGlzY3Vzc2lvbiBhYm91dA0KPiBpdC4gTWF5YmUgdGhhdCdzIGJlY2F1
c2UgSSBoYXZlbid0IHJlYWQgbXVjaCBpbiB0aGUgYXJjaGl2ZWQgbWFpbHMuDQoNCkhleSBz
Y2h1bWEsIEkgZG8gdGhpcyB0b28uICBJIGhhdmVuJ3Qgc2VlbiBhbnkgZGlzY3Vzc2lvbnMg
YWJvdXQgaXQNCmVpdGhlci4gIFRoZSBtYWNybyBmb3JtYXQgc2VlbXMgaHVtYW4gcmVhZGFi
bGUgZW5vdWdoIHRoYXQgdGhpcyBpc24ndA0Kc3VjaCBhIGJhZCBwcmFjdGljZS4NCg0KRm9y
IGV4YW1wbGUsIEkgYnVpbHQgc29tZSBsb2cgZmlsZXMgdG8gZGVtb25zdHJhdGUgYSBjb3Vw
bGUgMy1jeWNsZXMNCmhlcmU6DQoNCmh0dHA6Ly9nYW1lcy5ncm91cHMueWFob28uY29tL2dy
b3VwLzREX0N1YmluZy9tZXNzYWdlLzEwNzQNCg0KVGhlIGNvbW11dGF0ZWQgY29tbXV0YXRv
ciBtYWNybyB3YXMganVzdCBhIHF1aWNrIGVtYWNzIHNlc3Npb24uDQoNCldpdGggTUM3RCB0
aGVyZSBpcyBlc3NlbnRpYWxseSBhIHNlcXVlbmNlICJzdGFjayIgd2hlcmUgeW91IGNhbiBw
dXNoDQptb3ZlIHNlcXVlbmNlcyBvbnRvIHRoZSBzdGFjayBhbmQgdGhlbiBwb3AgdGhlbSBv
ZmYgaW4gdGhlaXIgaW52ZXJ0ZWQNCmZvcm0uDQoNClNvIGlmIHlvdSBhcmUgbWFraW5nIGEg
Y29tbXV0YXRvciBjYW4gZG8gcHVzaCBTLCBwdXNoIFgsIHB1c2ggWSwgcG9wIFgsDQpwb3Ag
WSwgcG9wIFMgYW5kIGdldCBbUywgKFgsWSkgUyddLg0KDQpBbmRyZXkgbWVudGlvbmVkIHRo
ZSBpZGVhIGhlcmU6DQpodHRwOi8vZ2FtZXMuZ3JvdXBzLnlhaG9vLmNvbS9ncm91cC80RF9D
dWJpbmcvbWVzc2FnZS85MTUNCmFuZCB0aGVuIGltcGxlbWVudGVkIGl0IGFuIGRvY3VtZW50
ZWQgaXQgaGVyZToNCmh0dHA6Ly9nYW1lcy5ncm91cHMueWFob28uY29tL2dyb3VwLzREX0N1
YmluZy9tZXNzYWdlLzkyNw0KDQpJIHRoaW5rIE1DNEQgY291bGQgYmVuZWZpdCBmcm9tIHRo
aXMgZmVhdHVyZSBtb3JlIHRoYW4gbWFjcm8gbmVzdGluZy4NCkJvdGggd291bGQgYmUgdXNl
ZnVsIHRob3VnaC4gIEkndmUgdHJpZWQgdG8gd29yayBvbiBNQzREIGluIHRoZSBwYXN0DQpi
dXQgSSBuZXZlciBjb3VsZCBnZXQgRWNsaXBzZSBzZXR1cCByaWdodCB0byBidWlsZCB0aGUg
cHJvamVjdC4gIEkgbmVlZA0KdG8gYnVnIFJvaWNlIGFuZCBNZWxpbmRhIGFib3V0IGl0IGlu
IGEgZmV3IHdlZWtzIHdoZW4gSSBoYXZlIG1vcmUgZnJlZQ0KdGltZS4NCg0KQnJhbmRvbg0K
DQotLS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUtLS0tLQ0KVmVyc2lvbjogR251UEcgdjIuMC4x
NiAoR05VL0xpbnV4KQ0KDQppRVlFQVJFQ0FBWUZBa3lUenFFQUNna1FxYUdQekFzbDk0SzBO
Z0NlTzJnT1pSTlJwZ0NJZWszMTFsNU81QmswDQpMVElBb0syOXVidStKRXNFeStWT3JJcnNq
ekhIQ3oxMw0KPWJSYXENCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K
--------------040305000201000304080701
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 9/17/2010 1:24 PM, Brandon Enright wrote:
> "schuma"
>
>> Sometimes I build long algorithms based on short algorithms.
>> Unfortunately when I record a macro, it is not allowed to call
>> another macro. Here is what I did. I created an empty log file,
>> performed all the turns in the long algorithm including calling
>> macros, and saved the log file. I went into the log file, copied the
>> sequence of moves, pasted it into the macro file, and added certain
>> information like the name of the new macro and reference stickers. I
>> guess some people also do this. But I haven't found discussion about
>> it. Maybe that's because I haven't read much in the archived mails.
> Hey schuma, I do this too. I haven't seen any discussions about it
> either. The macro format seems human readable enough that this isn't
> such a bad practice.
>
> For example, I built some log files to demonstrate a couple 3-cycles
> here:
>
> http://games.groups.yahoo.com/group/4D_Cubing/message/1074
>
> The commutated commutator macro was just a quick emacs session.
>
> With MC7D there is essentially a sequence "stack" where you can push
> move sequences onto the stack and then pop them off in their inverted
> form.
>
> So if you are making a commutator can do push S, push X, push Y, pop X,
> pop Y, pop S and get [S, (X,Y) S'].
>
> Andrey mentioned the idea here:
> http://games.groups.yahoo.com/group/4D_Cubing/message/915
> and then implemented it an documented it here:
> http://games.groups.yahoo.com/group/4D_Cubing/message/927
>
> I think MC4D could benefit from this feature more than macro nesting.
> Both would be useful though. I've tried to work on MC4D in the past
> but I never could get Eclipse setup right to build the project. I need
> to bug Roice and Melinda about it in a few weeks when I have more free
> time.
>
> Brandon
Nested macros are definitely in the MC4D wish-list. Hacking the macro
files is a clever workaround. I definitely would have loved this feature
while performing my one and only solution to the 3^4. :-) This is issue
61
issue tracker. I've added some comments there from this thread and
bumped it's priority to major. We would /love /it if Brandon or any
other programmers in the group would like to help work on the code.
Please message me privately if you need help building the project. Roice
is probably the person to ask about connecting to the project's source
control system.
-Melinda
--------------040305000201000304080701
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
http-equiv="Content-Type">
On 9/17/2010 1:24 PM, Brandon Enright wrote:
"schuma" <mananself@gmail.com> wrote:
Sometimes I build long algorithms based on short algorithms.
Unfortunately when I record a macro, it is not allowed to call
another macro. Here is what I did. I created an empty log file,
performed all the turns in the long algorithm including calling
macros, and saved the log file. I went into the log file, copied the
sequence of moves, pasted it into the macro file, and added certain
information like the name of the new macro and reference stickers. I
guess some people also do this. But I haven't found discussion about
it. Maybe that's because I haven't read much in the archived mails.
Hey schuma, I do this too. I haven't seen any discussions about it
either. The macro format seems human readable enough that this isn't
such a bad practice.
For example, I built some log files to demonstrate a couple 3-cycles
here:
http://games.groups.yahoo.com/group/4D_Cubing/message/1074
The commutated commutator macro was just a quick emacs session.
With MC7D there is essentially a sequence "stack" where you can push
move sequences onto the stack and then pop them off in their inverted
form.
So if you are making a commutator can do push S, push X, push Y, pop X,
pop Y, pop S and get [S, (X,Y) S'].
Andrey mentioned the idea here:
http://games.groups.yahoo.com/group/4D_Cubing/message/915
and then implemented it an documented it here:
http://games.groups.yahoo.com/group/4D_Cubing/message/927
I think MC4D could benefit from this feature more than macro nesting.
Both would be useful though. I've tried to work on MC4D in the past
but I never could get Eclipse setup right to build the project. I need
to bug Roice and Melinda about it in a few weeks when I have more free
time.
Brandon
Nested macros are definitely in the MC4D wish-list. Hacking the
macro files is a clever workaround. I definitely would have loved
this feature while performing my one and only solution to the 3^4.
:-) This is
61 in the issue tracker. I've added some comments there from
this thread and bumped it's priority to major. We would love it
if Brandon or any other programmers in the group would like to help
work on the code. Please message me privately if you need help
building the project. Roice is probably the person to ask about
connecting to the project's source control system.
-Melinda
--------------040305000201000304080701--