Talk:Conway polyhedron notation

message: Perhaps consider seeds: S=(4-simplex), C=(4-cube)Tesseract, O=(4-orthoplex)16-cell, D=dodecaplex, T=Tetraplex
Wendy, can you fill-out or expand this table for 4-polytopes?
: There is a corresponding Conway operator, for each of the Wythoff mirror-edge and mirror-margin constructions, along with a variety of snub operators.  Moreover, since both call down to pennants (simplexes with numbered vertices), the wythoff construction can be used for these figures too.  
:The wythoff mirror-margin operators (j, k, o, m, g) produce figures with single faces and several kinds of vertices, while the wythoff mirror-edge operators, (a, t, e, b, s) produce figures with single vertices and several kinds of face.  
:The 3d operators correspond to the WMM j=omo, k=omm, o=mom, m=mmm, and g=ggg, while WME are a=oxo, t=xxo, e=xox, b=xxx, and s=sss.  In four dimensions, there are four elements, eg d = ooox or ooom.   
:The main difference is that the numbers between the nodes change from flag to flag.  So while xPx still gives a 2P, P changes from node to node.--Wendy.krieger (talk) 10:03, 31 December 2009 (UTC)
thread_title:  Conway operators for 4-polytopes? 

message: I notice that the kis operator is listed among the other "main" operators, and then described again as a shorter alternate notation (knX = dtndX). Is this a mistake? I made a graph of how various polyhedra are related to each other via these operators, and I can confirm that kX = dtdX at least for the Archimedean/Catalan polyhedra.—Tetracube (talk) 20:10, 5 August 2008 (UTC)
replies: text: The n refers to a limited kis, or limited truncation. Like k3 means "kis only triangles", and t3 means "truncate order 3 vertices". Tom Ruen (talk) 05:27, 7 August 2008 (UTC)
thread_title:  Kis operator 

message: Aren't many of the v/e/f entries incorrect?  In particular, ambo should have v+f faces unless I'm mistaken.  Bmreiniger (talk) 01:57, 8 April 2014 (UTC)
replies: text: Errors may exist, but possibly you're missing a spherical Euler characteristic substitution, with f+v=e+2, although this would be incorrect for using it for Euclidean tilings. Tom Ruen (talk) 03:13, 8 April 2014 (UTC)
replies: text:  OK, I see.  In the back of my mind I'm thinking about arbitrary surfaces (when the operations make sense), which this page is not about.  Thanks.  Bmreiniger (talk) 17:15, 8 April 2014 (UTC)

text: The operations could apply to toroidal_polyhedron, although you have really define the surface. Hart's javaScript only works for spherical polyhedra seeds. This alternate script  also works from spherical seeds, but has trouble with nonplanar faces, and doesn't conform points onto a sphere. Tom Ruen (talk) 22:27, 8 April 2014 (UTC)

text: Is there any reason not to list v+f faces for ambo?  I mean, it makes it clearer what's going on; using the Euler formula substitution obscures things by one step.  v+f seems much more natural. I'd recommend the change.  And in any case, the entries for chamfer are wrong: chamfer has e+f faces and 2e+v vertices. Anyone reading this who agrees should go ahead and make the edit to the page itself, or I will if I come back in a while and there's no disagreement. — Preceding unsigned comment added by 98.116.5.101 (talk) 06:07, 12 May 2014 (UTC)
thread_title:  Operations table 

message: What means cab ne see in sentence
The zero index cab ne see to represent vertices...
Jumpow (talk) 19:59, 22 October 2017 (UTC)
thread_title:  What is "cab ne see"? 

message: While this page is a great resource, I'm having a hard time tracking down references for some of the operators that don't appear on George Hart's list, and I kind of suspect that  created some out of necessity. That would fall under WP:NOR. I'm hoping that's not the case and I'm just confused by the article lacking in-line citations. -Apocheir (talk) 21:55, 17 November 2017 (UTC)
replies: text: Neither Antiprism nor Polyhedronisme implement the parameterized uk, wj,k, and vj,k operators. I'm also concerned because Antiprism, Polyhedronisme, and this page have some definitions that conflict, for example n, x, and z. I'm not looking at Wikipedia policy for the sake of policy, it's just that this page is kind of turning into a zoo, and creating new operators ad-hoc is making it more crowded. There's a recent paper here that actually complains about the absence of a systematic organization for Conway operators (page 9 in particular), and it references this Wikipedia page as an example! -Apocheir (talk) 21:40, 27 November 2017 (UTC)

text: Agreed, its a problem, and there's no authorative source to set a standard. I have thought to rework the article with multiple operator columns for different generator implementations. I'm less worried about indexed operators like wj,k since it can be seen as a definition of a series, which has some instances derivable from other operations. Tom Ruen (talk) 21:55, 27 November 2017 (UTC)

text: It looks promising. The matrix representation looks interesting, but will take some getting used to. I agree the gallery section is more just examples of what can be done and could be done on a commons page. One of the open questions for me was to see what was possible, so that's why I tried making the derived tables with composite operators. Anyway, since no one had really written up a theory on what is possible or not possible, this article is necessarily exploratory, showing possibilities with the cubic seed starting point. The main theory is apparently that symmetry is preserved, except for chiral forms which can cut symmetry in half if original has reflective symmetry. Tom Ruen (talk) 21:54, 14 January 2018 (UTC)

text: I may have been unclear. I never had an issue with the expand operator. What I was questioning was the "elongation" operator you use. That is not cited, and I'm not sure what you mean by it. -Apocheir (talk) 23:10, 13 July 2019 (UTC)

text: Do you have a citation for what elongation is defined as? And if elongation is not a Conway operator, why include it on this page? -Apocheir (talk) 20:50, 18 July 2019 (UTC)

text: Given that Harry Princeton has not responded to my concerns, and is currently banned due to adding OR to this and other pages, I'm removing it. -Apocheir (talk) 22:35, 4 December 2019 (UTC)
thread_title:  Original research 

message: Apocheir: I have since added a rigorous description to the operations of expand and ortho for uniform tilings which is entirely consistent with George Hart's Conway Polyhedron notation. Ambo connects consecutive midpoints of regular polygons to form new polygons, and expand is ambo applied twice, so I connected the midpoints again. It turns out that there is a compatibility between the ambo regular polygons and the vertex-type polygons as well (the midpoints of both types of polygons coincide and we can express this as a shared linear combination of original vertices). So this operation is undisputed according to George Hart's Conway Polyhedron notation, applied to uniform tilings. Moreover, ortho is compatible with dual superimposition over k-uniform tilings only because regular polygons are symmetric about any edge perpendicular bisector, and each regular polygon only shares up to a single edge with any other regular polygon (no half-edges). In George Hart's words, duality replaces faces with vertices and vertices with faces, and for uniform tilings, the resulting centroid-centroid edges are perpendicular bisectors because of the above symmetry. Thus, orthogonality.
I do feel like I am clear enough on this matter; I have since added the special tilings to the commons page and my sandbox as well. Thanks. Harry Princeton (talk) 15:23, 13 July 2019 (UTC)
replies: text: I may have been unclear. I never had an issue with the expand operator. What I was questioning was the "elongation" operator you use. That is not cited, and I'm not sure what you mean by it. -Apocheir (talk) 23:10, 13 July 2019 (UTC)

text: Do you have a citation for what elongation is defined as? And if elongation is not a Conway operator, why include it on this page? -Apocheir (talk) 20:50, 18 July 2019 (UTC)

text: Given that Harry Princeton has not responded to my concerns, and is currently banned due to adding OR to this and other pages, I'm removing it. -Apocheir (talk) 22:35, 4 December 2019 (UTC)
thread_title:  Special Tilings 

message: We both seem to agree as to how matrix multiplication works (what \mathbf{M}_x\mathbf{M}_d and \mathbf{M}_d\mathbf{M}_x each are in matrix form) but disagree as to which one of xd and dx corresponds to which of those.  Apochier believes that xd = \mathbf{M}_x\mathbf{M}_d and dx = \mathbf{M}_d\mathbf{M}_x, while I believe that xd = \mathbf{M}_d\mathbf{M}_x and dx = \mathbf{M}_x\mathbf{M}_d.  Other places in the article seem to back up my assumption.  Who is correct?  Kevin Lamoreau (talk) 21:49, 17 October 2018 (UTC)
replies: text: I now realize I was incorrect.  What threw me off is that I hadn't realized that the operation itself (the operation of an operator on a polyhedron) has the operator matrix before the matrix representing the polyhedron being operated upon.  I've edited the Operators section to try and show this better, by using the transpose symbol and an actual 3x1 matrix representation of the column vectors. Kevin Lamoreau (talk) 22:56, 17 October 2018 (UTC)
thread_title:  Can someone chime in on a disagreement between myself and Apochier regarding the meaning of '''xd''' and '''dx''' 

message: I'm enjoying this article, though I don't have the training to understand  even a fraction of the math and notation, or the patience to work it through and learn it by myself. What I'd really like is examples of what the resultant polyhedra would look like, rather than the formulaic blue-face/pink-face/dot diagrams, which require painstaking mental expansion to produce examples. 
I realize/gather that this would require a lot of work and might well be WP:OR, so I'm not so much asking for it as wishing for it. Still, there's no harm in doing so here on the Talk page.
--Thnidu (talk) 16:27, 6 January 2019 (UTC)
replies: text: Polyhedronisme is a good place to start. It's a web app where you can put in arbitrary strings of Conway notation and it generates a 3d model you can rotate and zoom on. It doesn't implement every operation that's listed on this page, but it has all of the original ones. Antiprism is a more complete implementation, but it's less user-friendly. -Apocheir (talk) 16:53, 6 January 2019 (UTC)
replies: text:  Θanx.--Thnidu (talk) 00:25, 7 January 2019 (UTC)
thread_title:  Actualized illustrations? 

message: Conway's original set of operators can create all of the Archimedean solids and Catalan solids, using the Platonic solids as seeds.
I believe that the previous claims on this page are not correct. Because Truncated cuboctahedron as one of Archimedean solid can not be made by truncate Cuboctahedron (taC=bC). The new face that can be created is not a square, but a rectangle. The same is true for Truncated icosidodecahedron. Kepler also knew the above. Today, see 'Polyhedra' by Peter R. Cromwell.
--中川 宏 (talk) 06:30, 17 May 2019 (UTC)
replies: text: I'm struggling somewhat to understand your comments, but I think you're distinguishing geometric equality and topological equality. Unfortunately the writings on this topic often muddles the two. Many implementations insert an implicit canonicalization step before returning the result. The above statement is true in the topological sense, and is true in the geometric sense after canonicalization, but may not be true when omitting the canonicalization step. This page could be clearer about that. -Apocheir (talk) 17:41, 22 May 2019 (UTC)
thread_title:  about Archimedean solids by Conway original notations 

message: The following Wikimedia Commons file used on this page has been nominated for deletion:
* 
Participate in the deletion discussion at the . —Community Tech bot (talk) 18:07, 18 May 2019 (UTC)
thread_title:  A Commons file used on this page has been nominated for deletion 

message: you were right about the jagged parts of the graphics that were there previously, commons:Category:Polygon_chambers_(red_and_white). I updated them to fix that, and to make the middle lines in the polygons a little thinner. We seem to be converging on the same design for this graphic, so let's cooperate and save ourselves some effort. 
Here are my concerns about the graphic that you want to use.
* It's distracting that each shape is a different size. 
* I do not agree that using the different colors improves the graphic. Having them be the same color emphasizes that it's the same fundamental domain on a different polygon. Doesn't matter what color, though it should be something high-contrast.
* Putting labels in English within the graphic itself makes it more difficult to use the graphic on non-English-language Wikipedia projects. There are at least six other language Wikipedias that have an article on this topic. It's better to put the label in the page text, where it can be searched and automatically translated.
* Relatedly, all the shapes are combined into one file in your graphic. If they're separate, they're easier to label.
* Simple graphics like this are often preferred to be in scaleable vector graphics (SVG) format, so they can be displayed at any size without distortion. It can also produce smaller files. Your PNG graphic is 209 KB, while the SVGs all together only about 1% of that. Not that 209 KB is a huge file, but it can make a difference on poor-quality connections.
Like I said, I'm willing to make changes to the SVG files to create something everyone's happy with. In fact, I already have made some changes, as I mentioned above. 
As a side note, since you seem to have an interest in creating graphics for math articles, you might want to look into a SVG drawing program like Inkscape. -Apocheir (talk) 23:52, 20 October 2019 (UTC)
replies: text: To suggest on the SVGs, vertices at the center may be helpful :). Also, Asymptote tends to perform better on rounded line ends (for the vertices). Harry Princeton (talk) 14:38, 27 October 2019 (UTC)
replies: text:  I can't tell what your suggestion is? SVG can be displayed in any web browser without converting it to a raster file first, unlike Asymptote (vector graphics language), which must be converted to PNG first (which negates the benefits of using a vector graphic format). -Apocheir (talk) 17:48, 27 October 2019 (UTC)
thread_title:  Illustration for [[Conway polyhedron notation#Operators]] 

message: The image for dX, called Conway_dXC.png, is missing a green point on the top surface, in the lower left. (Each side of the cube should have 12 points.) 80.208.70.76 (talk) 17:37, 9 January 2024 (UTC)
thread_title:  Faulty image for the Cross operation