As the tag line suggests, this blog is about science, mathematics, and computing. I spend my time in my day job as a mathematician, or a computer scientist, or an engineer, depending on the situation, preferably in that order, but usually in reverse. I also love teaching, and so I tend to fall into pedagogical rants from time to time.
Subject matter typically deals with my day-to-day encounters with mathematical or scientific ideas that I find beautiful, valuable, interesting, amusing, or (less often) infuriating.
I am also a fan of free software. When my interest in a problem survives long enough to yield code that others might find enjoyable, useful, or otherwise interesting, I try to make it available here, and on GitHub.
Possibly Wrong 
I work for a charity in Cornwall. Could we use your image of the compass on an activity sheet we are putting on our new Access to Nature Cornwall website. I can provide you with more details but the basic ethos of the project has been to encourage and inspire people to use the outdoors more.
Sure, no problem. I assume you mean this image?
I’m using your arbitrary precision library for one of my projects, and I needed arbitrary precision floats, so I wrote my own using your library as a template. I formatted it differently, but it is essentially the same plus arbitrary precision floats and a separate file that calculates constants (pi, e, and ln(2). I also added square root, natural log, and power functions so far and intend to add more soon. May I submit it as a contribution on github? If so, would you be willing to help optimize/debug it? The only bug I am aware of is in the << operator. I know exactly what triggers it but not how to fix it.
Brian– this sounds interesting. If you’re asking if you can create a new repository that includes some/all of my code, but possibly significantly modified (I’m not sure how extensive changes are implied by “using as a template” and “formatted differently”), then sure, no problem. My use of the UNLICENSE is intended to signify that the code is in the public domain, so you’re free to take it and do with it what you will; I certainly appreciate any reference/credit/attribution as courtesy, but it’s not required.
Re helping to optimize/debug, I can try to help if I can. Let me know when you get a repository setup and I’ll take a look.
I’m here for thank you for your inspiring articles. I used your code in my project in these scripts:
https://github.com/neozhaoliang/pywonderland/blob/master/src/cftp/cftp.py
https://github.com/neozhaoliang/pywonderland/blob/master/src/gifmaze/example_ust.py
https://github.com/neozhaoliang/pywonderland/blob/master/src/gifmaze/example_hilbert_curve.py
also thank you for your helpul discussions in the below the post.
Just out of curiosity, how did you make the image in your header? I made something a few years back that can generate similar-looking images so it’s cool to see someone else with the same idea! https://github.com/TheGuywithTheHat/ImageGen
Thanks! I like the images in the linked gallery, very cool!
The header image is just a cropped portion of a larger “allRGB” image, that contains every (24-bit RGB) color in exactly one pixel. See details here. This particular one results from taking a breadth-first traversal through the vertices of a uniformly random spanning tree of the 4096×4096 grid graph (one vertex for each pixel), assigning colors to each vertex/pixel according to a parallel traversal of the 256x256x256 RGB cube in Hilbert curve order.
I am a big fan of your blackjack program. I was able to modify it to create strategy charts for Bingo Blackjack, which is a really wild variation on standard blackjack. Your code and classes are really well thought out. It didn’t take me long figure out how to add the Bingo multipliers to the EV calculations. Thanks so much for publishing the code.
Thanks! It’s rewarding to hear that you’ve found it useful. I wasn’t familiar with the bingo variant, I’m glad the code was helpful in extending to handle that case.
I’ve recently published open-source code to make large Penrose tilings. In the documentation are multiple unproved assertions, and multiple things of possible interest to your readers — few previously have seen the paths, rather than the tiles.