A simple tool to figure out just how much LLM generated code has been used in a project. Obviously not perfect, but it automates the task of going through commits for "co-authored by" statements and other signs. In the off chance you don't want to use the CLI, there's also a web app!

Updated version of https://quokk.au/c/[email protected]/p/1081324/spr-ule-ing with correctly labeled aircraft.

Based on a true story...

Based on a true story...

I am trying to mathematical model a passive Magnetorheological damper. Broadly speaking, this would work by having a magnet sit on the damper shaft near the damper body. As the shaft moves, it would induce an eddy current in the damper body, creating a magnetic field. Not only would this magnetic field oppose the magnet's motion, but it would increase the viscosity of the magnetorheological fluid inside the damper body. On paper, this would rapidly increase the damping forces with increasing shaft speeds, allowing for more controlled shaft speed.

Fortunately, I found a paper discussing a damper similar to my ideas. Unfortunately, I don't really understand the math, and I need the damping force equation in terms of velocity to validate the application I have in mind. Linked is the paper I am referring to.

For my purposes, I would also want to model separate traditional high and low speed compression and rebound circuits moving through traditional mechanical damping circuits, along with some other damping features. However, that's a problem for future FedX, right now I really just care about the broad differences in damping characteristics as a function of shaft velocity.