User talk:Cmglee/archive2020

2O11	2O12	2O13	2O14	2O15	2O16	2O17	2O18	2O19	2O2O
2O21	2O22	2O23	2O24

Topics started in 2020

file:Homograph_homophone_venn_diagram.svg

Hi, your diagram has a few mistakes in it. For once the heading "heteronym" (different name) should be "heterophone" (different sound). Since 'desert' (sandy place) and 'desert' (leave) have the same name but are pronounced differently. Also the way the Venn Diagram is drawn makes it look like the top/middle section 'homonymns' is part of the wrongly-named 'heteronymns' section as well as the 'heterograph' section but while homonyms have the same spelling and the same pronunciation they are neither heterophones (since they do sound the same), nor are they heterographs (since they are written the same) (or 'heteronyms' since that's the opposite of what they are). — Preceding unsigned comment was added by 2001:16B8:5025:2800:4DCB:8AE3:F656:65F7 (talk) 19:50, 23 January 2020 (UTC)

Hi! Thanks for your note. I drew the graphic based on File:Homograph_homophone_venn_diagram.png above. I don't know enough about linguistics to make a judgement call or find appropriate reference. If you can get a consensus on the exact changes required from the English Wikipedia language reference desk, I'll upload a new version. Cheers, cmɢʟee ⋅τaʟκ 01:44, 24 January 2020 (UTC)

File:Cmglee Helen Czerski 2013 Cambridge Science Festival.jpg

File:Cmglee Helen Czerski 2013 Cambridge Science Festival.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

A1Cafel (talk) 15:27, 26 January 2020 (UTC)

Copyright status: File:5 room puzzle minimal.svg

Copyright status: File:5 room puzzle minimal.svg

This media may be deleted.

Thanks for uploading File:5 room puzzle minimal.svg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

Yours sincerely, Magog the Ogre (talk) (contribs) 01:48, 7 February 2020 (UTC)

File:Comparison optical telescope primary mirrors.svg

I really loved your "Comparison optical telescope primary mirrors" artwork. The visuals easily show the variety of telescopes and relative sizes.

While rereading it I noticed that some of the planned dates have slipped. I played with changing a local copy but I wasn't sure how to send the changes back since I know nothing of how this system works. I am hoping you can use a diff:

282c282
<     <text x="-50" y="4em">Chile (planned 2022)</text>
---
>     <text x="-50" y="4em">Chile (planned 2025)</text>
287c287
<     <text x="0" y="2em">Mauna Kea, Hawaii (planned 2022)</text>
---
>     <text x="0" y="2em">Mauna Kea, Hawaii (planned 2027)</text>
303c303
<     <text x="0" y="3em">Chile (planned 2020)</text>
---
>     <text x="0" y="3em">Chile (planned 2029)</text>
476c476
<     <text x="0" y="4em">(planned 2018)</text>
---
>     <text x="0" y="4em">(planned 2021)</text>

I loved the inclusion of the OWL and Arecibo. I included more information for Arecibo.

269c269
<     <text x="0" y="1em" class="comp">Arecibo radio telescope at the same scale</text>
---
>     <text x="0" y="1em" class="title comp">Arecibo Observatory (305m radio telescope) (1963)</text>

I noticed that everywhere the first light dates are last except for the Multi Mirror Telescope so I re-positioned them to be consistent.

407c407
<      <text x="0" y="1em">(1979-1998)</text>
---
>      <text x="0" y="3em">(1979-1998)</text>
412c412
<      <text x="0" y="1em">(1999-)</text>
---
>      <text x="0" y="3em">(1999-)</text>
414,415c414,415
<     <text x="0" y="2em" class="title">Multi Mirror Telescope</text>
<     <text x="0" y="3em">Mount Hopkins, Arizona</text>
---
>     <text x="0" y="1em" class="title">Multi Mirror Telescope</text>
>     <text x="0" y="2em">Mount Hopkins, Arizona</text>

I stopped there but there are little things that could be done like only using one unit (meters) and adding sizes to all.

I saw the page of your other art and it's just amazing. The breadth of interesting topics made for a late night of reading! — Preceding unsigned comment added by Rogerflores92 (talk • contribs) 07:19, 19 February 2020 (UTC)

Updated diagram

Thank you so much for your insightful suggestions and kind words, @Rogerflores92: constructive and specific feedback such as yours inspires me to contribute more diagrams!

I've checked the dates out and modified the diagram accordingly. I've also added FAST and updated ELT's name. I kept "at the same scale" for Arecibo, as I've done for other comparisons, to stress that it is not an optical telescope.

I had to put the MMT dates above as there have been two versions; putting them below dissociates the drawings from their respective dates. Alternatives are

1. Putting the dates for every telescope below its drawing: looks odd to have a date before the name
2. Putting drawings under their labels: to put non-mirrors together and to save space, I wish to put the radio telescopes next to the sports' courts, but starting the diagram with these (at the top) seems odd.

Measurements in inches were added to distinguish different telescopes or lenses at the same observatory, so form part of their names. I think converting them to metric would lose their significance.

Thanks again,
cmɢʟee ⋅τaʟκ 01:02, 24 February 2020 (UTC)

File:Solar system escape velocity vs surface temperature.svg - temperatures

Hi, someone on reddit commented that this diagram has some temperatures wrong. See here for details. --mfb (talk) 23:35, 1 March 2020 (UTC)

Thanks, @Mfb: I've replied on the page that I'm not familiar with the subject, so can't verify the reasoning. I'll update the diagram if someone can link me to an authoritative source e.g. NASA or ESA – a table of escape velocity vs temperature will do. Cheers, cmɢʟee ⋅τaʟκ 22:29, 2 March 2020 (UTC)

File:Nucleosynthesis_periodic_table.svg

About the periodic table, the python code doesn't make sense. Could you tell me what needs to be changed? There were two errors listed by Visual Studio Code. And what am I supposed to do with the output from the python program?

Hi, I've moved your message from the top to better maintain chronology. In what way does it not make sense, and what two errors did you get? I deleted the first line of the SVG file, renamed it as Nucleosynthesis_periodic_table.py and ran it in Python. Both Python 3.8.0 and 2.7.8 generated Nucleosynthesis_periodic_table.svg (the file I uploaded) without error. By the way, what change(s) did you intend to make? Hope that helps, cmɢʟee ⋅τaʟκ 23:26, 26 March 2020 (UTC)

File:Edward Colston statue location map.svg

Many thanks for providing the map here, very useful addition to the article. The "current location" marker could use rewording now that the statue has been moved from the harbour into storage, though (I assume at an unknown location). --Lord Belbury (talk) 09:06, 11 June 2020 (UTC)

Thanks, @Lord Belbury: Does "Dumped location" work? Cheers, cmɢʟee ⋅τaʟκ 10:43, 11 June 2020 (UTC)

Works for me. Thanks for making the update! --Lord Belbury (talk) 12:14, 11 June 2020 (UTC)

Binomial theorem visualization up to 4th power

Hi. I really love the illustrations you make for all the articles. One of the images I was really fascinated by was the visualization of the binomial theorem in this article. I know this is your original work, but which academic publication/book did you use to get this idea of visualizing the binomial theorem? Thanks! --Dh*Phoenix (talk) 10:21, 21 June 2020 (UTC)

Thank you very much for your kind words, @Dh*Phoenix: I was inspired by an image similar to the one on http://reddit.com/r/visualizedmath/comments/8fziii/binomial_cube but expanded it to include more dimensions. The first time I see images such as File:Fourier_series_square_wave_circles_animation.gif, abstract ideas become concrete. I wish I was exposed to such ideas when I was a student, so I try to help the next generation understand concepts better. If you've any other visualisation ideas, I'd sure like to hear about them. Cheers, cmɢʟee ⋅τaʟκ 21:51, 21 June 2020 (UTC)

Thanks for the information! --Dh*Phoenix (talk) 06:43, 22 June 2020 (UTC)

Generation timeline

Updated

The Generation timeline you created and added [1] was very well done! Just two minor corrections:

• Can you change the end point of Generation Z to early 2010s instead of 2012 please?
• And change the end point of Generation Alpha to mid-2020s instead of late 2020s?

The Generation article wasn't really up to date but it seems like another editor has cleaned it up just now [2]. Thank you! Some1 (talk) 21:02, 27 June 2020 (UTC)

Maybe for Generation Z, it could be changed to 1997 - 2012, following this chart by the Pew Research Center: https://www.pewresearch.org/fact-tank/2019/01/17/where-millennials-end-and-generation-z-begins/ft_19-01-17_generations_2019/ Some1 (talk) 01:04, 28 June 2020 (UTC)

Thanks for researching this and for your compliment, @Some1: I've updated it accordingly. Cheers, cmɢʟee ⋅τaʟκ 16:43, 28 June 2020 (UTC)

That looks terrific, thank you so much for updating it! Some1 (talk) 17:10, 28 June 2020 (UTC)

Hi — I love your generations chart. Doing an image search, I don't see anything else like it. I humbly offer a few suggestions — can you have the Korean War and Vietnam rather than (or alongside) the Cold War? Those are more associated with generations than the Cold War, which is not known for a generation fighting in it. I think retirement should start at 65, not 60, and is it possible to feather (soften) the ends from 70-90 so it doesn't look like everyone dies when they're 70? :-) Finally, Millennials is misspelled. Perhaps in future versions, the height of each generation bar could correspond to the population, e.g., Boomers bar taller than the "Lucky Few" — even having the height of each bar vary across time, as birth rates go up or down. Great work! Jordgette (talk) 00:35, 29 June 2020 (UTC)

Hi @Jordgette: Many thanks for your compliments and feedback. Good catch on my misspelling. I tried to make the diagram more international, so picked the ages 60 and 70 as they are multiples of 10, and cover the range from 1962 in [3] (best I could find), and from 1950 for North America and Europe in File:Life_Expectancy_At_Birth_By_Region.png, respectively. Softening it would make it harder to read, in my opinion. The Korean and Vietnam wars were US-centric, but I think are fair additions considering the readership. I like your idea of varying bar height (has to be number born, not current numbers, as the chart will then need to be constantly changed), but don't have the appropriate data. If you know of any, please let me know. Thanks, cmɢʟee ⋅τaʟκ 23:26, 30 June 2020 (UTC)

@Cmglee: Loads of countries were involved in the Korean and Vietnam wars to various extent, so mentioning them explicitly is not necessary U.S.-centric. They were, after all, hot spots of the Cold War. Anyway, this version is pretty good. I like the fact that you packed so much information into so little space, but without overcrowding it. Nerd271 (talk) 20:24, 3 July 2020 (UTC)

Thanks, @Nerd271: kind of you to say that. If you know of any other topics to illustrate, please let me know. Cheers, cmɢʟee ⋅τaʟκ 23:22, 3 July 2020 (UTC)

A few more suggestions I have for corrections you could make:

-Change the Gen Alpha start date on your chart from 2012 to 2013, since Gen Z ends in 2012 on the chart.

-On your chart you appear to have the War on Terror starting in 2002; in actuality it started in 2001.

-You have Web 2.0 and the War on Terror bunched together as starting at the same time; however in actuality, Web 2.0 started closer to around 2004 (when the term was coined) or 2005 (when YouTube came out and Broadband overtook dial up).

-In-between the Cold War and Web 2.0, you could add Web 1.0 which spanned from about 1991-2004/2005.

Template looks really good, nice job.--CherokeeJack1 (talk) 23:50, 4 July 2020 (UTC)

Thanks, @CherokeeJack1: . Agreed, though I understand the start year of Gen Z is not established, but for consistency with other generations, starting the year after end of the previous one seems sensible. Cheers, cmɢʟee ⋅τaʟκ 23:21, 5 July 2020 (UTC)

The start year of Generation Z at 1997 is fine: it matches the Pew Research Center timeline: https://www.pewresearch.org/fact-tank/2019/01/17/where-millennials-end-and-generation-z-begins/ft_19-01-17_generations_2019/

Note that there is an asterisk next to the end point of Generation Z which means that the end point of Generation Z at 2012 is tentative for now. CherokeeJack1 was suggesting that you change the start year of Generation Alpha to 2013, which I disagree with because the end point of Generation Z and starting point of Generation Alpha are still tentative.

Your timeline dates as it currently stands for each generation look fine as it is now; no need to change it any further. Some1 (talk) 23:44, 5 July 2020 (UTC)

Hi @Some1, As the start is "early 2010s", I think starting at 2013 is as good as starting at 2012, yet maintains consistency with earlier generations. Anyway, the caption and description has a disclaimer that dates are approximate. Cheers, cmɢʟee ⋅τaʟκ 23:59, 5 July 2020 (UTC)

I think there's a bit of a misunderstanding(?). The template says "Update as per CherokeeJack1's feedback", but CherokeeJack1 was asking that the start date of Generation Alpha be changed to 2013, but the template currently states that the start date of Generation Alpha is "early 2010s". Anyway, it's not a big deal. When Pew adds Generation Alpha to their timeline (which might be years from now since the oldest of that generation is around 8 years old now), the template could always be updated later. Some1 (talk) 00:21, 6 July 2020 (UTC)

Copyright status: File:Epicyclic gearing animation.svg

Copyright status: File:Epicyclic gearing animation.svg

This media may be deleted.

Thanks for uploading File:Epicyclic gearing animation.svg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

This action was performed automatically by AntiCompositeBot (talk) (FAQ) 00:05, 2 July 2020 (UTC)

A barnstar for you!

	The Graphic Designer's Barnstar
	Thank you very much for your helpful diagram in "Bilinear interpolation". Zangturang (talk) 15:35, 10 July 2020 (UTC)

Thank you very much, @Zangturang: glad you found it helpful. Let me know if you'd like another concept illustrated. Cheers, cmɢʟee ⋅τaʟκ 18:58, 10 July 2020 (UTC)

Question about size-specific SVG programming

I just took notice of all the incredible stuff you do with SVGs, and saw that it's possible to do conditional programming in SVG, and think this might be good for an issue with my tartans. Specifically, once the librsvg generated PNG gets under 25% of the original image size, the mask resolution gets too small to let the lower layer through, and all you get is the weft (horizontal) weave (see the thumbnail on one of my tartan images to see, or generate a PNG rendering at 149px or less). I'm wondering if there would be a way of programming that layer to go to 50% opacity at <25% sizing. If you have any leads for me, I'd be grateful. VanIsaac (en.wiki) 07:26, 23 July 2020 (UTC)

Hi @Vanisaac: Thanks for the compliment. By conditional programming, do you mean make the thumbnail renderer give different output depending on thumbnail size? I've found that thumbnails of some images drastically change at different sizes, such as these:

and

(if they look the same, try changing the zoom level using Ctrl+- and Ctrl+=), but haven't discovered what causes it and how to control it.

A more reliable method is to hack systemLanguage. This might work for your tartans as you don't already have text to translate. Will that work? cmɢʟee ⋅τaʟκ 23:49, 23 July 2020 (UTC)

Copyright status: File:Basic physics formula triangles.svg

Copyright status: File:Basic physics formula triangles.svg

This media may be deleted.

Thanks for uploading File:Basic physics formula triangles.svg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

This action was performed automatically by AntiCompositeBot (talk) (FAQ) 23:05, 31 July 2020 (UTC)

File:Cmglee Powerless Structures Fig 101.jpg

File:Cmglee Powerless Structures Fig 101.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

A1Cafel (talk) 02:49, 3 August 2020 (UTC)

FM Promotion

★ This file has been promoted to Featured media! ★ The file File:Comparison satellite navigation orbits.svg, that you uploaded is now assessed as one of the finest file on Wikimedia Commons, the nomination is available at Commons:Featured media candidates/File:Comparison satellite navigation orbits.svg. Thank you for your contribution. If you would like to nominate, please do so at this nomination page.

/FeaturedMediaBot (talk) 21:00, 9 August 2020 (UTC)

Hi there, the file got promoted to Featured Media on Commons. However, in the discussion/votes, there were a few suggestions on improving the SVG (eg mouse-over functionality), if you're interested. It Is Me Here (talk) 11:08, 13 August 2020 (UTC)

Hi @It Is Me Here: Thanks for bringing it to my attention. The hover effect seems broken; it should fade everything but the object being hovered over. I'll see what I can do this weekend. Cheers, cmɢʟee ⋅τaʟκ 23:18, 13 August 2020 (UTC)

MOTD Notification

⭐ A file you uploaded is on the main page! ⭐ File:Comparison satellite navigation orbits.svg, that you uploaded, is on the main page today. Thank you for your contributions to this project.

//EatchaBot (talk) 00:01, 12 August 2020 (UTC)

Mach Bands gradient overshoot

Added a smooth luminance profile for comparison

This is a very interesting image and a great way to illustrate the phenomenon. Is it possible to add a version where the luminance has a continuous derivative as a counterexample? 22:06, 22 October 2020 (UTC)

Technically, it will always be discontinuous as SVG defines gradients with piecewise-linear functions, but I'll experiment with some approximations to see if it visually looks smooth. Cheers, cmɢʟee ⋅τaʟκ 00:37, 23 October 2020 (UTC)

P.S. I've now added a smooth luminance profile for comparison.

Pyrimaid of the Sun

Hi. I spotted an error in File:Comparison of pyramids SMIL.svg: the height of the w:Pyramid of the Sun is given as 75m. In fact, it is closer to 65m (63m on the Spanish page, and 66m on the English page).—AlphaMikeOmega (talk) 15:17, 29 October 2020 (UTC)

Thanks for your message, @AlphaMikeOmega: w:Pyramid of the Sun gives multiple values, actually:

1. In History, "The second round of construction resulted in its completed size of 225 meters (738 feet) across and 75 meters (246 feet) high..."
2. In Structure measurements, location and orientation, "Height 71.17 metres or 233.5 feet"
3. In the infobox, "Height 65.5 meters (216 feet)"

Not sure which is the correct value, if any. Cheers, cmɢʟee ⋅τaʟκ 22:52, 29 October 2020 (UTC)

File:USA electoral votes 2020 hex cartogram.svg

Ok I am not belong to any political party (I am not even an American!) but I'd guess @realDonaldTrump (and his supporters) will say your map is rigged since apparently there are only 222 hexagons, instead of 232 for Trump... — An Macanese 16:36, 19 November 2020 (UTC)

 Done Thanks very much, @An Macanese: well spotted. Surprised I missed that! cmɢʟee ⋅τaʟκ 01:24, 20 November 2020 (UTC)

And just an FYI, but the AP just called Georgia this afternoon after the recount confirmed Biden's lead. VanIsaac (en.wiki) 06:04, 20 November 2020 (UTC)

Thanks, Vanisaac. I've found the article at https://apnews.com/article/why-ap-called-georgia-for-joe-biden-29c1fb0502efde50fdccb5e2c3611017 . I'll update the diagram later today. Cheers, cmɢʟee ⋅τaʟκ 08:46, 20 November 2020 (UTC)

A barnstar for you!

	The Original Barnstar
	Hello Cmgleeǃǃǃ The only Wikipedian I know ofǃ I just wanted to say welcome, since you thanked meǃ ː-) Also, you may check this... A bug. https://phabricator.wikimedia.org/T268832 Seeker220 (talk) 14:42, 26 November 2020 (UTC)

@Seeker220: Thank you very much for the barnstar. Superb contributions you've made with the Phrabicator, images and math equation copying.

I'd like to help, though I'm unfamiliar with Mediawiki development. I didn't know one can normally paste an image into a page from the clipboard; learnt something today.

Anyway, glad to hear from you and see you around! cmɢʟee ⋅τaʟκ 18:55, 26 November 2020 (UTC)

2O11	2O12	2O13	2O14	2O15	2O16	2O17	2O18	2O19	2O2O
2O21	2O22	2O23	2O24