Skip to content
View cosgroma's full-sized avatar

Block or report cosgroma

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
cosgroma/README.md

Mathew Cosgrove

GNSS FPGA SysML v2 MBSE Python Docs

I build tools and systems around GNSS software-defined receivers, FPGA/embedded signal processing, MBSE workflows, and engineering automation.

My public GitHub work focuses on reusable lab environments, developer tooling, documentation-first workflows, and experiments that make complex engineering systems easier to set up, inspect, and maintain. Some of my professional work is not represented directly on public GitHub, so this profile emphasizes public tooling, lab kits, and reusable engineering workflows.

Current focus

  • GNSS software-defined receiver architecture and test infrastructure
  • FPGA/embedded signal-processing workflows
  • SysML v2 / MBSE local tooling and model-management experiments
  • Developer tooling for reproducible engineering workflows
  • Agent-assisted planning, documentation, and repository maintenance

Featured public work

Project Focus
mbse-lab Local SysML v2 lab kit for Flexo MMS, SysON, bridge workflows, diagnostics, documentation, and safe model-workspace boundaries.
docker-stacks Reusable Docker environment experiments.
dotfiles Development environment configuration and workflow setup.
database-tools Structured-data and automation tooling experiments.

Systems I like building

flowchart LR
    gnss["GNSS / SDR"]
    fpga["FPGA + Embedded"]
    mbse["SysML v2 / MBSE"]
    tooling["Developer Tooling"]
    docs["Docs + Evidence"]

    gnss --> fpga
    fpga --> tooling
    mbse --> tooling
    tooling --> docs
Loading

How I work

I care about reproducible setup, clear CLI contracts, practical test coverage, safe sharing boundaries, and documentation that helps both developers and technical leads understand what a repository is for.

A good repository should make it obvious:

  • what problem it solves,
  • how to run it locally,
  • what is safe to share,
  • what is experimental,
  • and where future work belongs.

Engineering themes

gnss · sdr · fpga · embedded-systems · sysml-v2 · mbse · python · developer-tools · documentation · automation

Optional contribution visualization

This section is intentionally collapsed. I like keeping animated or decorative GitHub visuals secondary to the main technical profile.

Contact

Popular repositories Loading

  1. qtbooty qtbooty Public

    PyQt App framework

    Python 2 1

  2. framework-core framework-core Public

    Forked from RedhawkSDR/framework-core

    REDHAWK Core Framework

    Python

  3. googler googler Public

    Forked from jarun/googler

    Google Search, Google Site Search, Google News from the terminal.

    Python

  4. sphinx-docxbuilder sphinx-docxbuilder Public

    Forked from guiyomh/sphinx-docxbuilder

    An extension for a docx file generation with Sphinx-1.1.2

    Python

  5. openssl openssl Public

    Forked from openssl/openssl

    TLS/SSL and crypto library

    C

  6. driver driver Public

    Forked from hermixy/driver

    VxWorks dummy driver for fake sensors

    C