On Sun, Mar 15, 2015 at 7:24 AM, Bill Gosper <billgosper@gmail.com> wrote:
On Sat, Mar 14, 2015 at 2:11 AM, Bill Gosper <billgosper@gmail.com> wrote:
(http://www.blurb.com/books/2172660-minskys-trinskys-3rd-edition , p13) Backing up his rational multipliers to their previous convergent jumps the period from 2759393 to 4101126: gosper.org/boxstar5.png Pretty nearly to pixel scale. Julian probably found this already--he had a *much* larger one.
Six times.
--rwg I also tweeted two very small ones: https://pbs.twimg.com/media/CAC8iuLWoAAfNW4.png https://pbs.twimg.com/media/CAC6cmDWUAAf636.png
Just keep repeating: "These are *circles*."
Julian hadn't seen it, but suggested coloring the points mod 6. gosper.org/color4meg.png This is about 1/3 the resolution required to keep the pixels from overlapping, which the actual gridpoints magically avoid.
Rez ipsa loquitur: gosper.org/color4megstar.png
When hexagons get boring, we have pentagrams: https://twitter.com/wolframtap/status/577057734438330369/photo/1 But so far without the trusswork.
Finer: gosper.org/pentaflake.png <http://gosper.org/pentaflake.png> Does anyone have a dimension for this thing, or an IFS for it or its interior? I also tweeted Julian's original star: Graphics[{PointSize[Tiny],Point[NestList[{#, #2+Floor[#*7!/7381]}&[#[[1]]-Floor[#[[2]]*7381/7!],#[[2]]]&,{-19/24,-1015/121},2759393]]}]//tim 44.095003,1 [timing printout by tim] [pic] which apparently crashed their server. Presumably they have a 60(?) sec TimeConstrained and some sort of MemoryConstrained, but these apply only to the *back end*, which computed the 2.76M points in 44 sec. But then the *front end* (where <mumble>Constrained is powerless?) took many *minutes* to render my graphic, despite my experimental 60sec timeout. This apparently dismayed the Tweet server. --rwg .