501–510 of 1001 posts
My intent is to stream development of both the libraries I develop/contribute to (graphql_flutter, built_graphql, gql), as well as complete examples that I will deploy and release
A fully local, tag-based system for annotating/searching a number of different "data sources" (i.e. browser bookmarks, local files, twitter bookmarks) that all get unified under one interface. You set it up to monitor some data source and then it keeps track of when items are added/removed to/from it. The items from all data sources can be tagged, have notes attached to them, etc.—then quickly re-discovered through t…
Out of the box with minimal configuration, my telemetry platform has:
- Support for many common telemetry protocols, for example: (NMEA 0183, Mavlink, CAN-bus, VE.Direct, Key-Length-value strings)
- Realtime data streaming, play/pause/replay, time scrubbing
- Dashboard editor and component library (charts, gauges, text displays, instrument panels, etc)
- Data syncing in realtime between servers and the cloud; dashboards can be shared and viewed anywhere
My background in this is from my work at the University of Rochester leading a manned electric boat racing team. A need we saw across teams at our competitions was the ability to integrate realtime data from many embedded devices into a single data stream, plot data live on dashboards during races, store data for later analysis, and easily share that data among team members. Building out the infrastructure to do this gave our team a great advantage as we were able to back up high-level decisions with quantitative data we received from our system.
For example, where other teams would guess based on sparse data the ideal propeller pitch for a desired event, we had exact data on the RPM/torque from our drivetrain and current draw on the motor, and were able to quantitatively compare our propeller selection in different events to optimize for speed, efficiency, etc.
The professional ecosystem in this area is huge:
- ROS is the dominant telemetry platform across hardware systems
- The Mavlink protocol is used for drone communication
- CAN-bus and other hardware standards are used in the vehicle industry
- Matlab is commonly used for data collection & analysis among researchers
Across all these systems there is a common problem for beginners: There is a huge amount of domain knowledge and setup required before you can effectively build complex systems. Across almost every amateur project that does hardware data collection, people are repeating the same steps: Set up a custom protocol for streaming from an MCU over serial, write a program to receive/store that data, use an external tool to load, process and chart the data, etc.
On some level, that experience is really valuable, and I'm building the platform not to force you into a certain method: Using one piece of the system does not require buying into every feature. For example, you could just use the server for data collection, and read data points directly from the server into your own UI. conversely, you could use the server/UI to point at a ROS instance and just use the UI as a UI layer for dashboards.
Overall, I'm really excited because I think that building a ready-to-use server and a powerful UI into a single package represents a real step forwards. There's a real need for this type of system that I've seen time and time again in the field from makers, researchers, and anyone else building hardware systems.
A visual debugger for Haskell, that will graph data structures, sharing, and laziness as data is updated and then GCed.
I bought an old trench coat from a thrift store and outfitted it with 350 programmable LEDs , an Arduino to control them, and a 24 AA battery bank for a music festival last year, it was a hit. I'm currently working on adding another 150 LEDs, fixing the power system (I burnt out the Arduino after a couple hours), and looking into adding a microphone and learning some sound programming to make the suit change colours…
Most of them will cut power after a minute of so if you don't draw more than like 100mA of current, but that shouldn't be a problem with 350 LEDs. It'll save your Arduino's voltage regulator some grief, too :)
Remember when we/our parents would save newspapers and magazines of significant events? We lost that now that so many publications have gone 100% digital.
This site is an exploration of that idea.
It makes recurring screenshots of different/ popular/niched news sites and magazines from around the world.
It builds on the simple screenshot site, a separate open-souce screenshot-as-a-service project.
I should mention the Newseum's "Todays Front Pages"[1] site had the same idea long before I did. This exists in the context of a proper Mesuem with dedicated resources and curators. Their front pages are really nice, high fidelity PDFs of the dailies. They also offer mobile applications. Check them out!
https://www.friendlyskies.net/intj/the-balance-first-approac...
It's helped me personally avoid a lot of overwork issues during the pandemic, and so far the feedback on it has been pretty good...I still have lots of new modules to publish as well.
https://github.com/thejefflarson/little-cpu
I’m four instructions away from implementing the compressed extensions, and probably next week I’ll tackle the control and status registers. It uses an open source tool chain and is formally verified using riscv-formal. My hope is to eventually be able to compile some rust and get an fpga to blink an led :)