Main Console
A continuous research surface for physics, code, AI systems, markets, and political economy.
Ronnie's Lab reads like a technical notebook rendered as a live interface: archival, responsive, and unfinished in the right way.
Current Build
Reframing the site as a durable archive instead of a portfolio shell.
Lab Map
Workstreams should switch focus inside the same system.
Selecting a stream activates the adjacent detail pane instead of sending the user away.
Foundational Practice
Physics, code, and technical fundamentals kept sharp in public.
The base layer of the lab: C++, Verilog, electromagnetism, optics, simulation habits, and the slow work of technical fluency.
Outputs / formats
- • method cards
- • study logs
- • small simulations
- • stream recaps
Tools / focus areas
- • C++
- • Verilog
- • field solvers
- • breadboard notes
Constraint / active edge
Keeping first-principles work visible instead of hiding it behind finished results.
Archive
Records should preview in place and only route outward when necessary.
The default archive behavior is scan, filter, preview, then deepen.
Type
Domain
Preview
mlworkshop: Scientific ML, Hybrid Models, and Transformer Systems
`mlworkshop` is the core research repository behind my work in scientific machine learning, structure-aware modeling, and training systems.
Record previews stay inside the shell until a full route is genuinely useful.
Notes / Logs
The notes layer should feel alive, filterable, and adjacent to active work.
Type filters swap the visible note set without leaving the current surface.
Filter by note type
Active note
mlworkshop: Scientific ML, Hybrid Models, and Transformer Systems
`mlworkshop` is the core research repository behind my work in scientific machine learning, structure-aware modeling, and training systems.
About
Mission, principles, and negative space should sit inside the same shell.
This keeps identity close to the work instead of isolating it in a detached bio page.
Ronnie's Lab is a public home for rigorous learning and visible iteration. The aim is to leave a usable record, not to perform expertise.
Support the Lab
Support should feel like continuity infrastructure, not conversion theater.
Selecting a support mode reveals the detail panel in place.
Research Backing
Support independent workstreams, tools, and long-horizon study.
Best for patrons who want to help sustain open notes, experiments, and archival publishing.
- • Back archive maintenance and public note-taking.
- • Fund time for foundational technical work and system experiments.
- • Support prototype tooling, media prep, and live research output.
Contact / Collaborate
Clean communication routes for serious work.
Outreach should arrive with enough context to act on.
Collaborations
Joint research, technical build reviews, or design-system work.
contact@ronnieslab.systemsBest outreach includes: the problem, the reason Ronnie's Lab is a fit, and the desired format or timeline.
For direct record sharing, the archive detail routes remain the cleanest deep-link format.