3 ms·
Doesn't actually do the thing that makes the Unknown Pleasures cover somewhat nontrivial difficult to render, which is to let foreground "waves" obscure backgro
by marginalia_nu 4y ago
Doesn't actually do the thing that makes the Unknown Pleasures cover somewhat nontrivial difficult to render, which is to let foreground "waves" obscure background waves.
- jonahx 4y agoAlso, the original waves are much higher in the middle third and almost flat on the outer thirds: https://i.imgur.com/nlxdkGb.jpg https://i.imgur.com/nlxdkGb.jpg
- bcraven 4y agoIndeed they are, as they're recordings of Pulsar CP 1919: >“EIGHTY SUCCESSIVE PERIODS of the first pulsar observed, CP1919 (Cambridge pulsar at 19 hours 19 minutes right ascension), are stacked on top of one another using the average period of 1.33730 seconds in this computer-generated illustration produced at the Arecibo Radio Observatory in Puerto Rico. Although the leading edges of the radio pulses occur within a few thousandths of a second of the predicted times, the shape of the pulses is quite irregular. Some of this irregularity in radio reception is caused by the effects of transmission through the interstellar medium. The average pulse width is less than 50 thousandths of a second.” From “The Nature of Pulsars,” by Jeremiah P. Ostriker, Scientific American, January 1971. https://blogs.scientificamerican.com/sa-visual/pop-culture-pulsar-origin-story-of-joy-division-s-unknown-pleasures-album-cover-video/ https://blogs.scientificamerican.com/sa-visual/pop-culture-p...
- bazzargh 4y agoNot that nontrivial, I did that in my very first program for the bbcmicrobot https://twitter.com/bbcmicrobot/status/1604784926032740352 https://twitter.com/bbcmicrobot/status/1604784926032740352 1MO.4:DIMR(4) 2F.Y=820TO120S.-20 3GC.0,1:MOV.0,Y:DR.1279,Y:F.L=1TO4:R(L)=RND(120):N.L 4F.M=0TO1:GC.0,1-M:Z=Y-8*M:F.L=1TO3:A=200+L*150:MOV.A+R(L)+90,Z+160- R(L+1):MOV.A,Z:PL.81,300,0:N.L:N.M 5N.Y 9PRINT TAB(13,29);"BASIC PLEASURES" You can click through in the 'Source' link in the tweet and see how it did that - by painting the image filled in white first then filled in black slightly lower. (Re your point about the heights of the peaks - I actually adjusted my program to do this immediately after posting, and IIRC posted that too, but it was the first attempt that got all the likes/rts. I tended to do this all the time with these-just post the very first version that barely works, then regret it. I'm still doing that, this version of the vertigo poster... https://hachyderm.io/@bbcmicrobot@mastodon.me.uk/110107562467030317 https://hachyderm.io/@bbcmicrobot@mastodon.me.uk/11010756246... was quickly followed by the fixed one... https://hachyderm.io/@bbcmicrobot@mastodon.me.uk/110107978753711576 https://hachyderm.io/@bbcmicrobot@mastodon.me.uk/11010797875...)
- deleted 4y ago[deleted]
- marginalia_nu 4y agoWell of course it can be solved. My point is that it's not just a matter of rendering a bunch of transposed plots.
- Closi 4y agoIt's a matter of rendering a bunch of transposed points as a path and then applying a fill. Not particularly different, other than that I assume OP's challenge was to see how tiny they could make this and that might expand the code size.
- marginalia_nu 4y agoWell that's exactly my point, if you simplify the rules like that, of course the program becomes very short.