DevLog Week11 Meeting Minutes 2025 06 11

Project Meeting Minutes

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

1. This Week’s Progress

1. Windows Application Fix

   • “The Windows application issue was resolved by setting PyInstaller to bundle the application into a single file, ensuring the internals folder is included.”
   • Significance: Enables the software to run on both Windows and another operating system, enhancing cross-platform compatibility.

2. Invenio Integration Challenges

   • “Efforts to set up an Invenio instance faced issues with permissions and library compatibility on Windows, particularly with PyCairo and Invenio RDM. Vanilla Invenio is being considered for better deployment flexibility.”
   • Significance: Resolving these challenges is critical for data sharing, but a pragmatic approach will prioritize whichever solution (RDM or vanilla) yields results.

3. GitHub Repository Ownership

   • “Proposal to transfer the project repository to the UCC organization’s GitHub account, pending confirmation of permissions.”
   • Significance: Transferring ownership ensures long-term accessibility and aligns with university infrastructure.

2. Task Priorities

1. Presentation Development

   • “Develop a presentation for potential visits to Logitech and Stryker, including a process diagram, problem description, solution overview, challenges (e.g., Z-coordinate, Windows compatibility), and a video demo.”
   • Significance: A polished presentation is critical for showcasing the project to industry partners and academic evaluators.

2. Code and Repository Finalization

   • “Polish the codebase and finalize the GitHub repository, potentially transferring ownership to the UCC account.”
   • Significance: Ensures the code is production-ready and accessible for future contributors.

3. Data Collection and Video Demo

   • “Conduct a print run (e.g., cold bed print) to collect data and record a video demo showing the printer, interface, and HDF5 file structure.”
   • Significance: Visual evidence of the software’s functionality enhances presentations and project documentation.

4. Invenio Deployment

   • “Resolve Invenio setup issues, focusing on the vanilla version for flexibility, to enable data set sharing.”
   • Significance: Data sharing via Invenio supports academic research and project deliverables.

3. Industry Engagement Plan

1. Logitech Visit

   • “Negotiations are underway to schedule a visit to Logitech’s makerspace for a presentation and tour, tentatively proposed for the week after next (week of June 16, 2025). Scheduling depends on Logitech’s development team availability due to project deadlines and prototype confidentiality.”
   • Significance: The visit offers networking opportunities and feedback from industry professionals, with interest in the project’s data collection for prototype production.

2. Stryker Visit

   • “Stryker has agreed to host a tour of their advanced additive manufacturing facility, featuring Renishaw printers for titanium parts and a HIPP treatment plant.”
   • Significance: Exposure to industrial 3D printing processes can inform future project enhancements and provide networking opportunities.

3. Timing Decision

   • “The team must decide whether to schedule visits in June (post-project) or September (start of semester), depending on availability and summer plans.”
   • Significance: Aligns visit timing with team availability and industry schedules.

4. Presentation Plan

1. Structure

   • “The presentation will include: team introductions (2-3 minutes), problem description (3 minutes), solution overview with a process diagram (5 minutes), challenges overcome (e.g., Z-coordinate, Windows compatibility, 5 minutes), and a video demo of the printer and interface.”
   • Significance: A clear, concise presentation will effectively communicate the project’s value to Logitech, Stryker, and academic evaluators.

2. Practice Runs

   • “Plan multiple practice runs, potentially with Laura and Chris, to refine timing and content. Record a practice session for reference, especially if visits are delayed to September.”
   • Significance: Rehearsals ensure a polished delivery, and recordings aid consistency.

3. Video Demo

   • “Record a video showing the printer in action, interface setup, data collection, and HDF5 file structure, using simple tools like PowerPoint or Keynote for editing.”
   • Significance: A pre-recorded demo avoids live demo risks and enhances presentation impact.

5. Academic Requirements

1. Report Submission

   • “Clarification needed from Klaus on report requirements (e.g., weekly reports or a single summary). Existing bullet points and GitHub repository will form the basis of the report.”
   • Significance: Ensures compliance with academic grading criteria.

2. Project Artifacts

   • “The GitHub repository, runnable code, and demo video serve as tangible artifacts to demonstrate the project’s success.”
   • Significance: Provides concrete evidence of the team’s work for evaluation.

6. Project Timeline

1. Final Week Activities

   • “The project is in its final week (week 12). Planned tasks include conducting a print run, video recording, presentation development, and practice runs with Laura and Chris within this week.”
   • Significance: Critical to meeting project deadlines and preparing for potential industry visits.

2. Industry Visit Scheduling

   • “Awaiting confirmation from Logitech on availability for the week of June 16. The team will decide by June 13 whether to pursue June or September visits if the proposed week is unavailable.”
   • Significance: Ensures alignment with industry and team schedules.

7. Meeting Summary

The meeting focused on finalizing the 3D printing software project and preparing for industry engagement. Key progress includes resolving the Windows application issue using PyInstaller, addressing Invenio setup challenges (favoring vanilla Invenio), and proposing to transfer the GitHub repository to the UCC account. The team established priorities: developing a presentation for Logitech and Stryker visits, finalizing the codebase, recording a demo video, and resolving Invenio issues for data sharing. Visits to Logitech and Stryker are being planned, with Logitech’s visit tentatively set for the week of June 16, pending their development team’s availability. The team must decide by June 13 whether to pursue June or September visits if the proposed week is unavailable. For academic requirements, clarification on report formats will be sought from Klaus, with the GitHub repository and demo video serving as key artifacts. The project is in its final week, with print runs, video recording, and presentation practice scheduled within this week. The team’s work was praised for its quality, with the project exceeding expectations in 12 weeks.

8. Action Items

1. Print Run and Video Demo: Conduct a cold bed print run within this week to collect data and record a video demo showing the printer, interface, and HDF5 file structure.
2. Presentation Development: Start building the presentation within this week, including a process diagram, problem description, solution overview, challenges, and video demo. Schedule practice runs with Laura and Chris.
3. Code and Repository Finalization: Polish the codebase and confirm with Klaus about transferring the GitHub repository to the UCC account.
4. Invenio Deployment: Focus on setting up vanilla Invenio for data sharing, addressing Windows compatibility issues.
5. Industry Visit Decision: Discuss and decide by June 13 whether to pursue June or September visits if the week of June 16 is unavailable for Logitech.
6. Academic Requirements: Follow up with Klaus on report requirements and compile existing bullet points into a report format.