the answer is a resounding yes: https://github.com/seanwevans/pynq_butterfly

For stuff like this, definitely. It’s already exciting. Claude et al are surprisingly competent with real hardware. I’ve also had good success debugging basic issues with micros - not via the debugger, but giving datasheet and written analysis. I’m sure it could do things like capture from a connected oscilloscope (Salaeae have an MCP integration for their logic tools). Also for SPICE which I never bother with because the tools always felt stuck in the 90s, but having some serious automated analog review would be nice. I’m really excited to play with peripherals like the RP2040 or Beaglebone real time logic blocks, or improving/adding real USB support instead of USB serial.

For circuits I would trust a netlist or DRC/ERC review, checking a design against reference circuit values, probably not placement as that tends to be guided straight from a datasheet where it makes a difference and I like the artistic side of it.

that's FPGA firmware isn't it?

yes. my people.

https://github.com/seanwevans/pg_gpt2

https://github.com/seanwevans/pg_shell

https://github.com/seanwevans/pg_os

how bout Grorange

woah this is really neat!

this is excellent typesetting

Thank you! AI clearly helped a ton, but the number of rounds of me having it render different fonts / formats was staggering. And, I was fortunate enough to come across justif (https://justif.lyall.co/) - I found via HN! ... It perfectly implemented the system of justification I needed.

yeah who cares what tools you used to make it: this is a beautiful reproduction

this is so cool

I have done similar as well: https://github.com/seanwevans/pg_gpt2

agree:

https://github.com/seanwevans/pg_os

https://github.com/seanwevans/pg_git

https://github.com/seanwevans/pg_gpt2

etc...

I feel like I did this one already: https://github.com/seanwevans/4splat

Well there's your problem, you didn't say you wasted a million dollars doing something an expert can do in an afternoon.

I mean it’s probably in the training data too

Do you know what kind of compression ratios you get out of curiosity? Presumably it would be lower than this format (because this format is meant to be lossy not lossless) but very curious as a baseline.

Admittedly just scanned this but that’s lossless, right?

Wow dude. That is a hell of a README. Great job!

Your readme is really mobile unfriendly, FYI

spatiotemporal data

they takin er jerbs