DevLog Week12 Meeting Minutes 2025 06 16

Project Meeting Minutes

Meeting Date: June 16, 2025
Duration: Approximately 50 minutes
Attendees: Cathal, Shane, Junjie, Dave
Absent: Oleksandr, Oskar

1. Academic Requirements

1. Project Report and Logbook

   • Reference document: "CS and DSA Guide for Student Placement" (available on Canvas, page 12).
   • Logbook: Weekly entries instead of daily, as per mentor’s advice to simplify requirements.
   • Report format: Follow guidelines for margins, headings, etc. One team member to create a shared template.
   • Report sections:
     • Title Page: Standard format.
     • Summary: ~1 page, aligned with presentation content.
     • Project Description: Outline project goals, objectives, and motivations.
     • Placement Description (6-8 pages): Focus on individual contributions, supplemented with screenshots (code, UI, database schema), photos (printer parts, prints), and diagrams. ~3 pages of text, rest visual.
     • Placement Appraisal: Feedback on project experience (e.g., learning about 3D printing technologies).
     • Self-Appraisal (Appendix 4): Include as a scored checklist, potentially as a photo at report’s end.
   • Significance: Klaas indicated flexible submission requirements, emphasizing project contributions over strict guideline adherence.

2. Report Artifacts

   • Include screenshots (GitHub, Tinkercad, Cura, data collection), photos (successful/failed prints, e.g., stringing, support issues), and diagrams (e.g., database schema).
   • Significance: Visuals enhance documentation and demonstrate project scope.

2. Presentation Development

1. Structure (20-30 minutes, target 20 minutes)

   • Based on UCD Impact Canvas (searchable online).
   • Sections:
     • Problem Statement & Audience (2 min): Describe issue and beneficiaries (e.g., CS students using ML for manufacturing). Visual: Printer video with text overlay (e.g., “Support ML in CSET”).
     • Solution Benefits (2 min): Highlight comprehensive data capture (HDF5, simulator for ML). ~100 words/min.
     • Solution Overview (2 min): Show data collection process, codebase (Python, libraries), cross-platform UI, challenges (e.g., Z-axis, connectivity). Visuals: GitHub screenshots, UI, transitions.
     • Evidence of Impact (2 min): Focus on data (STL, G-code, sampling rate, imagery), error cases (e.g., Benchy, adhesion issues). Visuals: Data samples, error photos.
     • System Demo (10 min): Video-driven, covering Tinkercad (design rotation), Cura (G-code export), print setup, and HDF5 browsing. Allow pauses for explanations.
   • Significance: Concise, visual presentation engages academic and industry audiences.

2. Visual Elements

   • Use videos (printer, data collection), images (sensors, HDF5 structure), and animations (text transitions).
   • Storyboard slides for timing (e.g., 2-min printer video for problem statement).
   • Include overarching process diagram and error examples (e.g., cold bed, filament issues).
   • Significance: Visuals ensure clarity and engagement.

3. Practice Runs

   • Multiple rehearsals, starting with timing, then refining for natural delivery (3-4 runs).
   • Dry run scheduled for Thursday, June 18, 2025, using big screen for first 6 minutes.
   • Significance: Ensures polished delivery for industry visits or academic evaluation.

3. Task Priorities

1. Report Completion

   • Draft report this week, including contributions (design, implementation, testing, GitHub setup) and visuals (screenshots, print photos).
   • Mentor to send email summarizing report points.
   • Significance: Completing report during project mode avoids holiday disruptions.

2. Presentation Preparation

   • Draft first three sections (problem, benefits, solution) by June 17 for review.
   • Record videos (printer, UI, Tinkercad, Cura, HDF5) on June 17-18.
   • Significance: Timely preparation ensures readiness for potential visits.

3. Data Collection and Demo

   • Conduct print run (e.g., cold bed) to capture data and record demo (printer view, endoscope feed, UI, HDF5).
   • Include successful/failed prints (e.g., supports, stringing) for visuals.
   • Significance: Demonstrates functionality and challenges overcome.

4. Project Deployment

   • Deploy project to a computer if time allows, prioritizing report and presentation.
   • Significance: Deployment enhances project accessibility for future use.

4. Industry Engagement Plan

1. Logitech Visit

   • Tentative for week of June 16, 2025, pending development team availability (due to sensitive prototypes). Team discussion concluded September 2025 as the visit date.
   • Format: 20-min team presentation, 20-min Logitech presentation, 20-min makerspace tour.
   • Significance: Industry feedback and networking opportunities.

2. Stryker Visit

   • Confirmed interest for presentation and tour of advanced 3D printing facility (e.g., titanium printers).
   • Significance: Exposure to industrial applications informs future work.

3. Timing Decision

   • Decision by June 16 on June vs. September visits if Logitech cannot confirm next week. Team discussion concluded September 2025 for visits.
   • If delayed to September, reconvene via Teams for practice beforehand.
   • Significance: Aligns with team and industry schedules.

5. Project Timeline

1. Final Week Activities (Week of June 16)

   • Complete report draft, presentation sections, and video recordings.
   • Conduct print run and capture visuals (UI, printer, Tinkercad, Cura).
   • Practice presentation on Thursday, June 18, but team discussion concluded September 2025 for final presentation.
   • Significance: Meets project deadlines and prepares for evaluations.

2. Industry Visit Scheduling

   • Monitor emails for Logitech confirmation. Decision by June 16 on June vs. September visits, with team confirming September 2025.
   • Significance: Ensures timely coordination.

6. Meeting Summary

The meeting focused on finalizing the 3D printing data capture project for academic submission and industry engagement. The team reviewed report requirements (weekly logbook, 6-8 page placement description, visuals) and planned a 20-minute presentation (problem, benefits, solution, evidence, demo) with heavy visual emphasis (videos, screenshots, print photos). Priorities include drafting the report and presentation, recording demo videos, and capturing print data. Logitech and Stryker visits are planned for September 2025, as decided by June 16. The project is in its final week, with a dry run on June 18 critical for refining the presentation. The team’s work was noted for its foundational role in makerspace data infrastructure, enabling future ML/AI applications.

7. Action Items

Action Item	Responsible	Deadline
Create and share report template	One team member	June 17, 2025
Draft report (contributions, visuals)	All team members	June 16, 2025
Draft presentation (first three sections)	Team	June 17, 2025
Record videos (printer, UI, Tinkercad, Cura, HDF5)	Team	June 17-18, 2025
Conduct print run for data and visuals	Team	June 17-18, 2025
Schedule presentation dry run	Team	June 18, 2025
Monitor emails for Logitech/Stryker updates	All	Ongoing
Send report points email	Mentor	June 17, 2025
Capture print photos (success/failure)	Team	June 16, 2025

8. Next Steps

• June 17: Review draft presentation sections; start video recording.
• June 18: Dry run presentation; finalize videos and print run.
• September (confirmed delay): Reconvene via Teams for practice before visits.