From 9ff4119bad7a3b6166c1e8de3b34465038e07246 Mon Sep 17 00:00:00 2001 From: logan Date: Tue, 21 Apr 2026 18:47:41 -0700 Subject: [PATCH] Add meeting minutes for April 16, 2026, including agenda items, discussions, and action items --- docs/Mom/MoM_Apr_16_2026.md | 121 ++++++++++++++++++++++++++++++++++++ 1 file changed, 121 insertions(+) create mode 100644 docs/Mom/MoM_Apr_16_2026.md diff --git a/docs/Mom/MoM_Apr_16_2026.md b/docs/Mom/MoM_Apr_16_2026.md new file mode 100644 index 0000000..715d032 --- /dev/null +++ b/docs/Mom/MoM_Apr_16_2026.md @@ -0,0 +1,121 @@ +# Meeting Minutes - April 16, 2026 + +### Meeting Information +- **Date**: April 16, 2026 +- **Time**: 7:57 am - 8:22 am +- **Location**: Zoom +- **Meeting Type**: Weekly project sync +- **Facilitator**: Andrew Nelson +- **Note-taker**: Logan Sutton + +### Attendees +- Logan Sutton +- Gil Rezin +- Collin Rovey +- Andrew Nelson (joined during meeting) +- Dattatray Bhalekar + +### Absentees +- None noted + +### Agenda Items + +#### 1. Amiga Connectivity Status and Debugging Progress +**Discussion**: +- Team reviewed recent deep log analysis on the Amiga issue, including comparisons between a known working day and non-working sessions. +- Collin reported no obvious high-level differences from the primary logs and no clear deeper machine log file currently available. +- Gil identified that in working sessions packets appear to be exchanged, while in failing sessions connection may establish without data flow. +- Team discussed testing an additional GPS/library logging setting (if valid) before the next field attempt. +- Vendor responsiveness remains a concern, with no reply from Bonsai over the prior week. + +**Outcome**: +- Team will perform one more focused debug/test attempt this weekend before declaring the autonomous Amiga path effectively blocked for this cycle. +- Additional logging/config checks will be prepared prior to that session. + +#### 2. Fallback Demonstration Plan (If Amiga Autonomy Fails) +**Discussion**: +- Team discussed worst-case demonstration strategy for capstone and competition deliverables. +- Proposed fallback is to run variable-rate spraying from a prescription map while manually driving (or using available auto-track where feasible), then document autonomous software work and the platform limitation. +- Andrew confirmed this is a valid and defensible approach, especially since the issue appears to be with robot/GPS integration rather than the team's prescription/path logic. + +**Outcome**: +- Team aligned on fallback demo: prove variable-rate execution in the real world, and clearly report autonomous execution limitations caused by Amiga connectivity behavior. + +#### 3. Scheduling: Final Presentation, Sprint Video, and Test Sessions +**Discussion**: +- Team coordinated remaining capstone deliverables: final presentation, sprint video, and possible competition/LinkedIn video. +- A combined recording/demo approach was discussed to satisfy multiple requirements efficiently. +- Initial proposal for next Thursday changed after availability constraints were raised. +- Andrew and Dattatray noted they are unavailable next Thursday. + +**Outcome**: +- Final presentation meeting rescheduled to **Wednesday at 8:00 am** (following week). +- Logan will send/manage calendar invites and keep coordination on email as needed. +- Additional Saturday test session planned for **10:00 am** (target), pending day-of confirmation. + +#### 4. Rate Controller and Integration Readiness +**Discussion**: +- Collin shared that access/unlock for the John Deere rate-controller side is now available. +- Team can now begin validating prescription-map compatibility on monitor/hardware while waiting on remaining parts. +- Hardware arrival was expected around the next day or early next week. + +**Outcome**: +- Team gained a practical path to validate variable-rate control even if full autonomous stack remains unstable. + +#### 5. Deployment/Install Readiness for External Validation +**Discussion**: +- Andrew plans to run the containerized install and evaluate in his environment. +- Logan confirmed recent cleanup fixes were pushed, packages are public, and existing install script should pull latest tags. + +**Outcome**: +- Andrew will attempt installation and send questions/issues by email. +- Team expects smoother install experience compared with earlier states. + +### Action Items +| Task | Owner | Due Date | Status | +|------|-------|----------|--------| +| Run focused Amiga debug/test session and capture outcomes | Gil, Collin | Saturday (next session) | Planned | +| Validate whether additional GPS/library logging setting is real and usable before test session | Gil | Before Saturday test | In progress | +| Follow up with Bonsai again on unresolved Amiga behavior | Collin | ASAP / ongoing | In progress | +| Prepare/validate prescription map for rate-controller testing | Logan, Collin | Before next hardware test window | Planned | +| Send and manage invite for rescheduled final presentation (Wednesday 8:00 am) | Logan | Immediately | Completed | +| Attempt containerized install and report questions/issues | Andrew | Friday / next available morning | Planned | +| Confirm fallback demo narrative and include in sprint/final presentation materials | Logan, Gil | Before presentation/video deadlines | Planned | + +### Decisions Made +1. **Execute one more weekend attempt on Amiga autonomy** before formally pivoting demonstration strategy. +2. **Adopt manual-drive + variable-rate fallback if needed** to still prove real-world prescription execution. +3. **Reschedule final presentation to Wednesday at 8:00 am** due to Thursday conflicts. +4. **Prioritize demonstrable working components** (rate control + mapping pipeline) over waiting for uncertain vendor-side fixes. + +### Key Discussion Points +- Amiga failures appear intermittent at connection/data-flow level and are difficult to diagnose from currently accessible logs. +- Team now has a viable non-autonomous demonstration path that still validates core project value. +- Schedule pressure is high due to converging capstone deliverables and course end-of-term workload. +- Containerized deployment is mature enough for external validation and near-term use. + +### Issues/Risks Identified +- **Vendor dependency risk**: Delayed/no response from Bonsai blocks timely root-cause confirmation. +- **Autonomy demonstration risk**: Amiga may remain unusable for autonomous execution before deadlines. +- **Schedule compression risk**: Multiple end-of-term deliverables reduce slack for additional troubleshooting. +- **Hardware timing risk**: Rate-controller hardware/parts delivery timing may constrain testing windows. + +### Next Steps +- Run Saturday debug session and make a go/no-go call on further Amiga effort. +- In parallel, continue preparing manual-drive variable-rate demonstration assets. +- Complete external install validation and resolve any remaining setup friction. +- Finalize presentation/video plan for Wednesday demo and upcoming submission deadlines. + +### Next Meeting +- **Date**: Wednesday, April 22, 2026 +- **Time**: 8:00 am +- **Location**: Zoom +- **Agenda Preview**: Final presentation review, Amiga debug status, fallback demo readiness, and final deliverable coordination. + +### Additional Notes +- Team aligned on keeping momentum by proving what is reliable now while transparently documenting platform-side blockers. + +--- +*Meeting minutes prepared by: Logan Sutton* +*Date prepared: April 21, 2026* +*Distribution: Logan Sutton, Gil Rezin, Collin Rovey, Andrew Nelson, Dattatray Bhalekar* \ No newline at end of file