PiTracLM · connorgallopo · Sep 29, 2025 · Sep 29, 2025
@@ -42,7 +42,7 @@ jobs:
           path-to-document: "https://gist.github.com/jamespilgrim/e6996a438adc0919ebbe70561efbb600#file-verdant-contributor-license-agreement-md"
           path-to-signatures: "signatures/version1/cla.json"
 
-          remote-organization-name: "jamespilgrim"
+          remote-organization-name: "PiTracLM"
           remote-repository-name: "PitracCLASignatures"
 
           branch: "main"

@@ -17,4 +17,4 @@ Note that a beginning of a sketch for an x-shaped leveling support base has been
 Note also that the "shank shield" is not designed for 3D printing.  The hope is that the .dxf file can be used to laser cut or mill that part out of acrylic or (better) polycarbonite.
 **Assembly Notes:**
 
-See the [main assembly instructions](https://github.com/jamespilgrim/PiTrac/blob/main/Documentation/PiTrac%20Version%202%20Assembly.md).
+See the [main assembly instructions](https://github.com/pitraclm/pitrac/blob/main/Documentation/PiTrac%20Version%202%20Assembly.md).
@@ -12,5 +12,5 @@ You'll want to paint on supports and support-exclusions so that the only places
 
 **Assembly Notes:**
 
-See the [main assembly instructions](https://github.com/jamespilgrim/PiTrac/blob/main/Documentation/PiTrac%20Version%202%20Assembly.md).
+See the [main assembly instructions](https://github.com/pitraclm/pitrac/blob/main/Documentation/PiTrac%20Version%202%20Assembly.md).
 Ultimately, the two parts will be glued together with something like thick, slower-drying super-glue such as Starbond Gap Filler Thick High Performance Super Glue.
@@ -20,7 +20,7 @@ Recommended print settings: 2 perimeter layers, 15% infill, grid or rectilinear
 
 Please note that the default version is setup to accept 4 M2.5 and 4 M3 inner-diameter screw-in (or melt-in) inserts in which to screw the Pi and the V2 Connector Board.  If you want to instead simply use self-threading screws, change the values in the Monitor Chassis Parameters spreadsheet in rows 104 (GsPi5MountingHoleDiameter) and 110 (GSConnectorBoardMountingHoleDiameter).
 
-See the [main assembly instructions](https://jamespilgrim.github.io/PiTrac/hardware/assembly-guide.html).
+See the [main assembly instructions](https://pitraclm.github.io/PiTrac/hardware/assembly-guide.html).
 Ultimately, the four parts will be glued together with something like thick, slower-drying super-glue such as Starbond Gap Filler Thick High Performance Super Glue and then screwed together with 
 12 M2 x 6 self-tapping screws for additional strength in the lap joint (if desired).
 
@@ -17,7 +17,7 @@ Recommended print settings: 2 perimeter layers, 15% infill, grid or rectilinear
 
 **Assembly Notes:**
 
-See the [main assembly instructions](https://github.com/jamespilgrim/PiTrac/blob/main/Documentation/PiTrac%20Version%202%20Assembly.md).
+See the [main assembly instructions](https://github.com/pitraclm/pitrac/blob/main/Documentation/PiTrac%20Version%202%20Assembly.md).
 Ultimately, the four parts will be glued together with something like thick, slower-drying super-glue such as Starbond Gap Filler Thick High Performance Super Glue and then screwed together with 
 12 M2 x 6 self-tapping screws.
 
@@ -13,23 +13,23 @@ Introducing [PiTrac](https://hackaday.io/project/195042-pitrac-the-diy-golf-laun
 
 PiTrac uses low-cost Raspberry Pi(\*) computers and cameras to determine golf ball launch speed, angles and spin in three dimensions.  PiTrac interfaces with both GSPro and E6/TruGolf simulators, and its output is also accessible on a stand-alone web-based app.  \[We’ve reached out to 2k/TopGolf, but no response yet.\]
 
-PiTrac uses off-the-shelf hardware, and includes a [parts list](https://jamespilgrim.github.io/PiTrac/hardware/parts-list.html) with links to potential suppliers.  The only custom part is a small printed circuit board.  The fabrication instructions for that PCB are included in the open-source distribution and it can be manufactured for a few dollars.  The two Pi computers and cameras are the most expensive parts, and cost around $250 in total.
+PiTrac uses off-the-shelf hardware, and includes a [parts list](https://pitraclm.github.io/PiTrac/hardware/parts-list.html) with links to potential suppliers.  The only custom part is a small printed circuit board.  The fabrication instructions for that PCB are included in the open-source distribution and it can be manufactured for a few dollars.  The two Pi computers and cameras are the most expensive parts, and cost around $250 in total.
 
 PiTrac is not a commercial product for sale–the full design is being released as open source on GitHub for folks to build themselves.  It’s not easy, but if you’re handy with a soldering iron, can figure out how to 3D print the parts, and are willing to burrow into the Linux operating system to compile and install software, you should be able to create your own PiTrac\!  
 
 We are hoping that we can inspire a community of developers to help test and continue PiTrac’s development.  This is a really immature project right now.  The basic features usually work reliably, but the current release is a bit dodgy.  We’re looking for folks to try building their own PiTracs and help us improve the documentation and design to make it easier for other people to do the same.
 
 ## Project Page
-Please visit our [project page](https://hackaday.io/project/195042-pitrac-the-diy-golf-launch-monitor) and also our YouTube channel [here](https://www.youtube.com/@PiTrac) for more details and videos.  The [GitHub repository](https://github.com/jamespilgrim/PiTrac) is in the works and already has the 3D printed part designs, the hardware design and initial software documentation.  If you’re interested in more of the details and some of PiTrac’s development history, please look through the [project logs](https://hackaday.io/project/195042-pitrac-the-diy-golf-launch-monitor#menu-logs).  
+Please visit our [project page](https://hackaday.io/project/195042-pitrac-the-diy-golf-launch-monitor) and also our YouTube channel [here](https://www.youtube.com/@PiTrac) for more details and videos.  The [GitHub repository](https://github.com/pitraclm/PiTrac) is in the works and already has the 3D printed part designs, the hardware design and initial software documentation.  If you’re interested in more of the details and some of PiTrac’s development history, please look through the [project logs](https://hackaday.io/project/195042-pitrac-the-diy-golf-launch-monitor#menu-logs).  
 
 Finally, any help at our [support page](https://ko-fi.com/Pitrac) would be appreciated to continue this work and complete the release process.
 
 (\*) Raspberry Pi is a trademark of Raspberry Pi Ltd.  The PiTrac project is not endorsed, sponsored by or associated with Raspberry Pi or Raspberry Pi products or services.
 
-## [Getting Started](https://jamespilgrim.github.io/PiTrac/getting-started/getting-started.html)
+## [Getting Started](https://pitraclm.github.io/PiTrac/getting-started/getting-started.html)
 The process of building your own PiTrac DIY Launch Monitor is described here at a high level. There are several more-detailed instruction documents elsewhere in the PiTrac repository that are referred to below for various sub-assemblies and tasks like compiling the code and preparing the build environment.
 
-## [Setup and Configuration](https://jamespilgrim.github.io/PiTrac/software/pi-setup.html)
+## [Setup and Configuration](https://pitraclm.github.io/PiTrac/software/pi-setup.html)
 The instructions which are targeted toward getting setup on a step-by-step basis. These instructions start with a Raspberry Pi with nothing on it, and are meant to describe all the steps to get from that point to a working, compiled version of PiTrac.  PiTrac currently requires two Raspberry Pi’s, so the majority of these instructions will have to be repeated twice.  Because the ‘smaller’ Pi system that connects to Camera 2 is the only Pi that handles the Tomcat/Tomee web-based GUI for the system, there are a few more steps for that system.
 
 ## [Join the Discord](https://discord.gg/gMQcBBQYHT)

@@ -493,7 +493,7 @@ https://github.com/digdeeproots/provable-refactorings
 #### Build Failures
 - Make many small and reversible changes
 - Test on a clean environment regularly
-- Aim to improve the [pipeline](https://github.com/jamespilgrim/PiTrac/blob/a3b3f1baad0ded3066b0c9585ce4879ef6314d18/.github/workflows/camera-tests.yml) test coverage
+- Aim to improve the [pipeline](https://github.com/pitraclm/pitrac/blob/a3b3f1baad0ded3066b0c9585ce4879ef6314d18/.github/workflows/camera-tests.yml) test coverage
 - Maintain a working baseline with frequent small pull requests and short lived branches
 
 #### Integration Issues  

@@ -221,7 +221,7 @@ TEST(OpenCVAnalyzerTest, DetectsTeedBall) {
 
 ### Related Documentation
 - **Camera Bounded Context**: 
-[Pull Request](https://github.com/jamespilgrim/PiTrac/pull/87) Provides camera abstractions and calibration data.
+[Pull Request](https://github.com/pitraclm/pitrac/pull/87) Provides camera abstractions and calibration data.
 
 ## Camera Bounded Context Integration
 

@@ -9,7 +9,7 @@ source "${SCRIPT_DIR}/common.sh"
 load_defaults "pitrac-build" "$@"
 
 # Configuration from defaults
-PITRAC_REPO="${PITRAC_REPO:-https://github.com/jamespilgrim/PiTrac.git}"
+PITRAC_REPO="${PITRAC_REPO:-https://github.com/pitraclm/pitrac.git}"
 PITRAC_BRANCH="${PITRAC_BRANCH:-main}"
 PITRAC_PR="${PITRAC_PR:-0}"
 BUILD_DIR="${BUILD_DIR:-$HOME/Dev}"

@@ -1,5 +1,5 @@
 # PiTrac Build Configuration
-pitrac-repo: https://github.com/jamespilgrim/PiTrac.git
+pitrac-repo: https://github.com/pitraclm/pitrac.git
 # Branch to checkout (main, develop, feature/xxx, etc)
 pitrac-branch: main
 # Pull request number to checkout (overrides branch if set)
@@ -15,4 +15,5 @@ configure-shell: 0
 build-cores: 0
 # Set to 1 to clean build directory before building
 clean-build: 0
-# Note: Camera types and paths are read from environment variables set by pitrac-environment
+
+# Note: Camera types and paths are read from environment variables set by pitrac-environment
@@ -627,7 +627,7 @@ print_help_footer() {
     echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
     echo
     echo "For more information:"
-    echo "  - PiTrac Documentation: https://jamespilgrim.github.io/PiTrac/"
+    echo "  - PiTrac Documentation: https://pitraclm.github.io/PiTrac/"
     echo "  - Discord Community: https://discord.gg/j9YWCMFVHN"
 }
 

@@ -2,14 +2,14 @@ title: PiTrac - DIY Golf Launch Monitor
 description: Complete documentation for PiTrac, the open-source DIY golf launch monitor built with Raspberry Pi. Get ball speed, launch angles, spin rates, and golf simulator integration.
 theme: just-the-docs
 
-url: https://jamespilgrim.github.io
+url: https://pitraclm.github.io
 baseurl: /PiTrac
 
 # Logo
 logo: "/assets/images/logos/PiTrac.svg"
 
 aux_links:
-  Edit Me: https://github.com/jamespilgrim/PiTrac/tree/main/docs
+  Edit Me: https://github.com/pitraclm/pitrac/tree/main/docs
 
 search_enabled: true
 

@@ -35,7 +35,7 @@ Finally, the current calibration rig assumes that the tee-off camera that watche
 
 First thing to do is to get your calibration rig printed.  The rig provides an easy way to precisely position two golf balls in front of the launch monitor.  Of course, you could make your own rig – you would just need to make measurements of where the ball(s) are relative to the cameras and inform PiTrac of that through the configuration file. 
 
-1. Print the rig using the [files here](https://github.com/jamespilgrim/PiTrac/tree/main/3D%20Printed%20Parts/Enclosure%20Version%202/Calibration%20Rig) in the github repo.  The rig is in the version 2 enclosure file area, but can be used with either version of the enclosure.  The main difference in using the rig for the Version 1 and 2 enclosures is just the measurement values that describe the distances from where the cameras are to the golf balls positioned on the rig.  The rig looks like the following on the print bed:
+1. Print the rig using the [files here](https://github.com/pitraclm/pitrac/tree/main/3D%20Printed%20Parts/Enclosure%20Version%202/Calibration%20Rig) in the github repo.  The rig is in the version 2 enclosure file area, but can be used with either version of the enclosure.  The main difference in using the rig for the Version 1 and 2 enclosures is just the measurement values that describe the distances from where the cameras are to the golf balls positioned on the rig.  The rig looks like the following on the print bed:
 
    ![Picture 1_0 - AutoCalibration Instuctions](https://github.com/user-attachments/assets/5d97b701-f18b-42c8-89fc-3654e0de1781)
 (Picture 1\_0)

@@ -186,7 +186,7 @@ CMake files exist in the project but have different structure than shown. Multip
 #### Initial Setup
 
 ```bash
-git clone https://github.com/jamespilgrim/PiTrac.git
+git clone https://github.com/pitraclm/pitrac.git
 cd PiTrac/packaging
 
 # Get pre-built artifacts

@@ -82,7 +82,7 @@ The following documentation pages are available:
 
 1. **Clone the repository:**
    ```bash
-   git clone --recursive https://github.com/jamespilgrim/PiTrac.git
+   git clone --recursive https://github.com/pitraclm/pitrac.git
    cd PiTrac
    ```
 
@@ -120,7 +120,7 @@ The following documentation pages are available:
   ```
 - Add upstream remote:
   ```bash
-  git remote add upstream https://github.com/jamespilgrim/PiTrac.git
+  git remote add upstream https://github.com/pitraclm/pitrac.git
   ```
 
 ### 2. Development
@@ -177,7 +177,7 @@ PiTrac/
 
 ## Getting Help
 
-- **GitHub Issues**: https://github.com/jamespilgrim/PiTrac/issues
+- **GitHub Issues**: https://github.com/pitraclm/pitrac/issues
 - **Discord Community**: https://discord.gg/j9YWCMFVHN
 - **Documentation**: This guide and source code
 

@@ -49,7 +49,7 @@ We are also thankful for individual contributors who—even if we haven't used t
 11. The many supportive folks on the Hackaday site, including @Ometry and @melaby
 12. Phillip Mayhew
 13. Mark Harman (@Speci on Discord)
-14. @[broschb](https://github.com/jamespilgrim/PiTrac/commits?author=broschb) and others on GitHub
+14. @[broschb](https://github.com/pitraclm/pitrac/commits?author=broschb) and others on GitHub
 15. Merrygrin, Scuzzy On Discord
 16. Ron Heywood
 17. Connor Gallopo (@gallapagos on Discord)

@@ -19,7 +19,7 @@ PiTrac is not a commercial product for sale–the full design is being released
 
 We are hoping that we can inspire a community of developers to help test and continue PiTrac's development.  This is a really immature project right now.  The basic features usually work reliably, but the current release is a bit dodgy.  We're looking for folks to try building their own PiTracs and help us improve the documentation and design to make it easier for other people to do the same.
 
-Please visit our [project page](https://hackaday.io/project/195042-pitrac-the-diy-golf-launch-monitor) and also our YouTube channel [here](https://www.youtube.com/@PiTrac) for more details and videos.  The [GitHub repository](https://github.com/jamespilgrim/PiTrac) is in the works and includes the 3D printed part designs, software and hardware designs and code and some initial software documentation.  If you're interested in more of the details and some of PiTrac's development history, please look through the [project logs](https://hackaday.io/project/195042-pitrac-the-diy-golf-launch-monitor#menu-logs).
+Please visit our [project page](https://hackaday.io/project/195042-pitrac-the-diy-golf-launch-monitor) and also our YouTube channel [here](https://www.youtube.com/@PiTrac) for more details and videos.  The [GitHub repository](https://github.com/pitraclm/pitrac) is in the works and includes the 3D printed part designs, software and hardware designs and code and some initial software documentation.  If you're interested in more of the details and some of PiTrac's development history, please look through the [project logs](https://hackaday.io/project/195042-pitrac-the-diy-golf-launch-monitor#menu-logs).
 
 Finally, any help at our [support page](https://ko-fi.com/Pitrac) or our project [wish list](https://www.amazon.com/registries/gl/guest-view/11PSDIVICY8UX) would be appreciated to continue this work and complete the release process.
 

@@ -43,7 +43,7 @@ But here too, there's a decision to make.  The Version 2 enclosure will someday
 
 But the Version 2 enclosure can also support builds using *OTS parts* instead of the Compute Board.  As such, part of the decision of which road to take right now is whether to wait for the above-pictured vision of PiTrac to emerge, or instead use the Version 2 enclosure with the currently-available off-the-shelf system.  Most folks are opting for that option now.
 
-This second Version 2 option typically houses the large LED driver in the base of the system, with several AC power adapters kept externally with wires running to the tower.  To go that way, you'll need an enclosure "tower" variant that is fitted for the separate Pi 5 SBCs.  See [here](https://github.com/jamespilgrim/PiTrac/tree/main/3D%20Printed%20Parts/Enclosure%20Version%202/Tower-Connector-Board-Variant).
+This second Version 2 option typically houses the large LED driver in the base of the system, with several AC power adapters kept externally with wires running to the tower.  To go that way, you'll need an enclosure "tower" variant that is fitted for the separate Pi 5 SBCs.  See [here](https://github.com/pitraclm/pitrac/tree/main/3D%20Printed%20Parts/Enclosure%20Version%202/Tower-Connector-Board-Variant).
 
 ![Tower Variant](https://github.com/user-attachments/assets/d040da0a-5363-475d-8114-5715e5935a62)
 

@@ -15,7 +15,7 @@ All 3D printable parts can be found in the main PiTrac GitHub repository under:
 - `3D Printed Parts/` directory
 
 {: .highlight }
-📥 **[Download 3D Parts](https://github.com/jamespilgrim/PiTrac/tree/main/3D%20Printed%20Parts)** - Access all STL files and 3D models on GitHub
+📥 **[Download 3D Parts](https://github.com/pitraclm/pitrac/tree/main/3D%20Printed%20Parts)** - Access all STL files and 3D models on GitHub
 
 ## Printing Requirements
 

@@ -207,11 +207,11 @@ The Middle Layer has two wall halves and two floors on the Pi side: lower floor
 
 ### 1. Build Strobe Assembly
 
-See [LED Strobe Mount instructions](https://github.com/jamespilgrim/PiTrac/tree/main/3D%20Printed%20Parts/Enclosure%20Models/LED-Array-Strobe-Light-Mount).
+See [LED Strobe Mount instructions](https://github.com/pitraclm/pitrac/tree/main/3D%20Printed%20Parts/Enclosure%20Models/LED-Array-Strobe-Light-Mount).
 
 ### 2. Build Connector Board
 
-See [Connector Board instructions](https://github.com/jamespilgrim/PiTrac/tree/main/Hardware/Connector%20Board).
+See [Connector Board instructions](https://github.com/pitraclm/pitrac/tree/main/Hardware/Connector%20Board).
 
 {: .important }
 **Critical:** Attach 12V IN/OUT wiring pairs and 4-wire harness to Connector Board screw terminals *before* mounting the floor. Access becomes difficult after upper floor installation.

@@ -23,7 +23,7 @@ This guide will walk you through getting PiTrac up and running on your Raspberry
 First, clone the PiTrac repository to your Raspberry Pi:
 
 ```bash
-git clone https://github.com/jamespilgrim/PiTrac.git
+git clone https://github.com/pitraclm/pitrac.git
 cd PiTrac
 ```
 

@@ -7,7 +7,7 @@ nav_order: 1.1
 
 ### About this Document
 
-To contribute to this documentation, please visit [Github Pitrac](https://github.com/jamespilgrim/PiTrac)
+To contribute to this documentation, please visit [Github Pitrac](https://github.com/pitraclm/pitrac)
 
 To quickly test your documentation locally, please take the following steps: 
 

@@ -557,7 +557,7 @@ Follow semantic versioning:
 
 ```bash
 # Clone with submodules
-git clone --recursive https://github.com/jamespilgrim/PiTrac
+git clone --recursive https://github.com/pitraclm/pitrac
 cd PiTrac/packaging
 
 # Install development tools
@@ -584,7 +584,7 @@ sudo usermod -aG docker $USER
 ## Support
 
 For packaging-specific issues:
-- GitHub Issues: https://github.com/jamespilgrim/PiTrac/issues
+- GitHub Issues: https://github.com/pitraclm/pitrac/issues
 - Discord: #packaging channel
 - Documentation: docs/development/packaging.md