u/hellerve
-
5points
-
3points
Paper: All the Way Down—MetaCarp, a self-hosting compiler for Carp (cyberwitchery.com)
-
52points
from the sketchbook (old.reddit.com)
-
6points
Carp in Glamorous Toolkit (blog.veitheller.de)
- 9points
- 9points
-
43points
working on my brushes (i.redd.it)
-
31points
Textures, inspired by Tyler Hobbs’ Repetition 2 (old.reddit.com)
-
17points
texture sketches: fur, shell, creased paper, cracked glaze (old.reddit.com)
-
79points
experiment trg 0.4 (i.redd.it)
hellerve
hellerve
Thanks for the heads-up in any case. I’ll hope for the best and this clause:
> Finally, there are some existing projects that are genuine but adopted a more permissive stance towards the use of AI. Usually this is phrased something along the lines of "If you do X, Y, Z then AI is allowed". While I personally believe this is incredibly naive (developers can't be bothered writing documentation, yet you think they will review 10 000 lines written by Claude? Please), I don't yet know how to best deal with these cases. As such we'll tolerate this as long as it's within reason, i.e. "moderator discretion" applies here.
If I get banned, so be it. To each their own.
hellerve
This is a paper and Erik and I have been working on Carp for over 10 years, well before any LLM/AI made an appearance. Does this still qualify?
EDIT to clarify: both Carp and Metacarp have a permissive AI/LLM contributing policy (contribute as long as you disclose it, discussions/RFCs are for humans only). This might mean it qualifies, depending what the letter or spirit of the law is.
hellerve
Thanks for the critique! I actually get more like a 4x improvement when inlining and using type hints together.
One thing about the macros (but I agree that I’m just too into macros):cell expands to aref and is used as a setf place. Replacing it with an inline function requires arranging the corresponding setter semantics. That's not an insurmountable problem, but it's not quite the trivial substitution you suggest in your comment.
EDIT: I updated the post with an addendum. Thanks!
hellerve
Well, that’s a lovely review! Thanks a lot!
hellerve
A variety of algorithms all layered together algorithmically. https://cyberwitchery.com/papers/cw002-teaching-personal-taste-to-silicate.pdf has the info on the selection process (it was an ill-advised attempt at teaching a recommender algorithm compositionality and curation).
On the algorithm front, we have vector fields, watercolor wash through low opacity layered forms, fields with various strokes (here pencil (first piece) and felt-tip pen (fourth piece) via varying stroke width, opactiy, and hue), a variation on the sand creature algorithm to create the scribbles, wiggly vectors of similar hue for the brush strokes/masking tape, and a variation of the water color algorithm for the ink splotches in the third piece (same forms, but also a center and a drip). In general, most of the algorithms try to mimic something physical without trying to recreate physics.
Sand creatures: https://inconvergent.net/generative/sand-creatures/
Similar water color algorithm: https://www.tylerxhobbs.com/words/a-guide-to-simulating-watercolor-paint-with-generative-art
hellerve
Thanks, I’ll take inspired/crazy any day!
One thing to note: Metacarp (https://github.com/cyberwitchery/metacarp), the compiler this runs on, is actually written in Carp. After bootstrapping, no Haskell is involved.
hellerve
Thanks! The low-level client is generated from the OpenAPI specs, and I hope that saves me some work, but yes, I’m also mindful that this will be the hard part. Not sure I have a good story on it yet.
I’ve been following Netbox since 2017 or early 2018, and yes, it’s been a wild ride maintaining plugins etc. We’ll see how it goes!
Good luck to you as well :)
hellerve
Managed to have a typo in my post title. Amazing.
hellerve
I was thinking of sharing a few more of my brushes and textures like this, just haven’t gotten around to it. Chances are if you find a work of mine and are interested in how it works, it was a) made in p5js or Prcoessing and b) I’m happy to share the code.
hellerve
The tips can be made less awkward quite easily by adjusting the trimming factor and varying thickness of individual brushes a bit more.
hellerve
Thanks for tghe write-up, this is really cool!
hellerve
All textures are made by lines, a mixture of straight and bezier curves of varying thickness, color, and opacity (very low opacity used, though, around `(2+rand(2))/255`). The magic of the gradients in 1 is figuring out good ways to cluster these lines effectively, since more overlapping=>deeper orange. Does that help?
hellerve
Beautiful textures!
hellerve
Thank you, that means a ton!
The techniques exhibited here are also fairly easy (triangle subdivisision and lines of variadic thickness), so it’s approachable for most generative tinkerers! We don’t always have to go for the shiniest techniques to produce something pretty :)
Glay you liked it!
I hadn’t pulled it apart into a nice templates for third parties, but I did the preliminary work now, and here’s the gist: https://gist.github.com/hellerve/30912dedcacf86178727c57b8f2c01c8