joshwa
Individual models may have supplemented their training with things that look like structure (e.g. Claude with its XMLish delimiters), but it's far from universal.
Ultimately if we want better fidelity to the concepts we're referencing, we're better off working from the larger/richer dataset of token sequences in the training data--the total published written output of humanity.
I made my own version of this a while back, and it lets you create your own cutting methods, plot the statistical distribution, and share your ideas via permalink. It also lets you tweak onion parameters, such as number of layers and the layer thickness distribution curve).
Along the way I discovered two things:
1. I came up with my own method ("Josh’s method" in the app above) where the neither the longitudinal cuts nor the planar cuts are full depth, so the number of cuts at the narrower core is less than at the wider perimeter.
2. After all this hyper-optimization about size, it turns out what really matters when cooking is the THICKNESS, since ultimately determines the cooking rate. The only way to avoid thin outliers that burn long before the rest are cooked is to discard more of the tip of the onion, where the layers are the thinnest.
The 3D version of the simulator is still in progress--turns out 3D geometry is a lot harder than 2D. :)
Pull requests are welcome! https://github.com/joshwand/onion-simulator
I got a cheap MLX90640 off aliexpress for target detection and a grove vision AI V2 module to use with IR cam for classification/object tracking. Esp32 for fusion and servo/solenoid actuation.
Collab?
SWE-Bench tainted by answer leakage; real pass rates significantly lower
A centrifugal spin on a 500-year-old air compressor design
2. Write a new tool that is dead simple, opinionated (your opinions), convention over configuration, etc
3. Post to HN
4. Achieve adoption
5. As more people use the tool, feature creep ensues
6. In order to satisfy diverse use cases, make everything modular and configurable!
7. Tool slows and becomes impossible to manage
8. GOTO 1.
A centrifugal spin on a 500-year-old air compressor design
The Rise of Digital Neo-Colonialism
Ask HN: Does this exist yet? UGC video clearinghouse for protests/etc.
I was inspired by OSINTHK's work during the protests in HK--assembling multiple videos of single incidents to provide as much context/evidence to fight the public relations battle.I'm sure something like this must exist already--a collaborative public OSINT platform for correlating UGC by timestamp and location? Where users can upload video and based on the metadata you cluster them into...
(email in profile)
Also described as: "how to be old, for young people"
Possible answers:
• Legit technical or cost/benefit reasons
• Probably a good idea but no budget/time for the effort
• Somebody already tried and it was a disaster
• No manager has been stupid enough to humor the devs
https://nelsonslog.wordpress.com/2020/01/07/facial-recogniti...
https://www.bellingcat.com/resources/how-tos/2019/12/26/guid...
Fairway Was Mismanaged and Looted by Private Equity
Wenyan: A programming language that follows the grammar of classical Chinese
1. Become frustrated with complex build tool
2. Write a new tool that is dead simple, opinionated (your opinions), convention over configuration, etc
3. Post to HN
4. Achieve adoption
5. As more people use the tool, feature creep ensues
6. In order to satisfy diverse use cases, make everything modular and configurable!
7. Tool slows and becomes impossible to manage
8. GOTO 1.
“Harbinger households”: neighborhoods that consistently buy products that fail
My adventures in 3D printing: Prime number sieve
https://www.researchgate.net/publication/271673255_Large-sca...