Thread: "Cuboid parity-esque situation on a {6}x{4} duoprism [2 Attachments]"

From: =?UTF-8?Q?Luna_Pe=C3=B1a?= <scarecrowfish@gmail.com>
Date: Sat, 2 Dec 2017 21:40:14 +0000
Subject: Re: [MC4D] Re: Cuboid parity-esque situation on a {6}x{4} duoprism [2 Attachments]



--f403045dd5cc9e8408055f625400
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I did actually attempt a single turn of the central face and then a
resolve, because I had a different set of pieces swapped in the same way,
but I just got back to there. And anyway, wouldn't the result not be a 5
cycle, but a 3 cycle and a 2 cycle, which is impossible? Or am I missing
something?

I was trying to think if there was some false equivocation somewhere, or
some 4d rotation that could do it, but I can't think of one.

I can't check the files right now, but I will tomorrow.

Thanks though. ~Luna

On 2 Dec 2017 21:33, "zhulama@gmail.com [4D_Cubing]" <
4D_Cubing@yahoogroups.com> wrote:


[Attachment(s) <#m_3727043479442679428_TopText> from zhulama@gmail.com
[4D_Cubing] included below]

I didn't solve this, but I have a feeling that there is no "swap two
pieces" algorithm, only "cycle 3 pieces".
"swap two pairs" is actually "cycle 3" two times...
The biggest issue I see is that you have a single 2-color problem and a
single 3-color problem while everything else is done, 4-color pieces
included! My solving methods don't allow me to solve this without
destroying the rest of the cube, lol.:D

My gut tells me that this parity issue can probably only be solved by doing
a twist of the middle hex face.
This will make the whole thing have only 1 two-color piece in place and 5
two-color pieces not-in place, then you can solve those five by doing
3-cycle algorithms.
This will screw up all the 3-color and 4-color pieces as well!

...and that's only for two color pieces, the 3 color parity might be solved
by this, it might not...

I did some "test work", files attached



--f403045dd5cc9e8408055f625400
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I did actually attempt a single turn of the central =
face and then a resolve, because I had a different set of pieces swapped in=
the same way, but I just got back to there. And anyway, wouldn't the r=
esult not be a 5 cycle, but a 3 cycle and a 2 cycle, which is impossible? O=
r am I missing something?

">I was trying to think if there was some false equivocation somewhere, or =
some 4d rotation that could do it, but I can't think of one.=C2=A0>

I can't check the files =
right now, but I will tomorrow.=C2=A0

dir=3D"auto">Thanks though. ~Luna
o">
On 2 Dec 2017 21:33, "lto:zhulama@gmail.com">zhulama@gmail.com [4D_Cubing]" <=3D"mailto:4D_Cubing@yahoogroups.com">4D_Cubing@yahoogroups.com> wro=
te:
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">












=20

=C2=A0







=20=20=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20
bottom:20px">[428_TopText">Attachment(s) from rget=3D"_blank">zhulama@gmail.com [4D_Cubing] included below]
=20=20=20=20=20=20=20=20
=20=20=20=20=20=20

I didn't solve this, but I have a feeling that there is no &qu=
ot;swap two pieces" algorithm, only "cycle 3 pieces".

v>"swap two pairs" is actually "cycle 3" two times...iv>The biggest issue I see is that you have a single 2-color problem and a =
single 3-color problem while everything else is done, 4-color pieces includ=
ed! My solving methods don't allow me to solve this without destroying =
the rest of the cube, lol.:D

My gut tells me that this p=
arity issue can probably only be solved by doing a twist of the middle hex =
face.
This will make the whole thing have only 1 two-color piece =
in place and 5 two-color pieces not-in place, then you can solve those five=
by doing 3-cycle algorithms.
This will screw up all the 3-color =
and 4-color pieces as well!

...and that's only=
for two color pieces, the 3 color parity might be solved by this, it might=
not...

I did some "test work", files at=
tached




=20=20=20=20=20

=20=20=20=20







=20=20









--f403045dd5cc9e8408055f625400--





Return to MagicCube4D main page
Return to the Superliminal home page