Skip to content

Instantly share code, notes, and snippets.

@pnappa
Last active December 22, 2023 22:20
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save pnappa/fab64adc9b43e80817b2f23b2f16eebd to your computer and use it in GitHub Desktop.
Save pnappa/fab64adc9b43e80817b2f23b2f16eebd to your computer and use it in GitHub Desktop.
@mkitzan
Copy link

mkitzan commented Oct 4, 2022

y

@mkitzan
Copy link

mkitzan commented Oct 4, 2022

@pnappa
Copy link
Author

pnappa commented Oct 6, 2022

(if you're referring to what I think you're referring to) we can do even better, it isn't needed to be dynamically created, so can just generate the (3d) voronoi crackle and embed it into the code

the more annoying part is coming up with a fast (in python) way to find the corresponding crackle region given the 3d coordinate (sub microsecond?) so we're gonna need to do something that doesn't involve crummy pointer dereferencing & jumping all over the place? the current solution uses kd-trees, which computationally quite tight in big-o notation, but the library I'm using isn't very fast, and I can't be bothered writing a C library for the task

as we're able to do all this computation before hand, I was thinking moreso coming up with a closed-form solution in the form of a small number of (linear?) equations that you sub in the three variables (r, g, b) and spits out the resulting matching terminal colour

the EVEN more annoying part, is bothering to program it

@mkitzan
Copy link

mkitzan commented Oct 12, 2022

@pnappa
Copy link
Author

pnappa commented Oct 13, 2022

ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment