Jeremy Simons

Background

About Jeremy Simons

I focus on low-power embedded systems for brain computer interfaces. My recent work centers on firmware development and supporting tools for modules related to the Chestek Lab open-architecture effort within the broader HORNET program. The aim is practical, modular systems that let research teams acquire and study neural signals with predictable behavior and clear verification. Day to day I contribute C and C++ on the STM32 platform. I implement fixed point signal paths and DMA based streaming so multi channel data remains synchronized from acquisition through storage. I pay close attention to timing, memory use, and power states so recording sessions remain stable on embedded hardware. I also maintain small analysis tools that measure latency and throughput, check time bases across sources, and generate figures that are easy to reuse across studies. These tools shorten the loop between a code change and a decision about whether it improved the data path. I design them to be understandable by collaborators who work on related HORNET components and I prefer simple, documented interfaces over opaque pipelines so others can extend the work in their own context. Alongside my lab work, I have built a field oriented neural data logger around STM32WB that emphasizes clean storage, watchdog-based recovery from faults, and straightforward power profiling. I also created SMART, a lightweight analysis and visualization tool for one to sixty four channels, with a small plugin surface so groups can add checks without heavy dependencies. Both efforts support the same goal as my lab work, which is to produce reliable data and make verification routine rather than an afterthought. I care about open-source development and shared methods. HORNET’s emphasis on open architecture aligns with how I try to work, which is to write code that others can read, test, and reuse. I am interested in roles where embedded firmware, applied DSP, and reproducible checks come together to move neural interface work forward. If your team is building or testing these systems and needs careful implementation with clear results, I would be glad to connect.