DevLog Week9 Meeting Minutes 2025 05 28

Project Meeting Minutes

Meeting Date: May 28, 2025
Duration: Approximately 25 minutes
Attendees: Cathal, Shane, Junjie, Oleksandr, Oskar
Absent: Dave

1. This Week’s Progress

1. Code Refactoring and Modularization

   • "Code refactoring is complete, with the program split into smaller modules, each focused on a single function."
   • Significance: Modularization enhances code maintainability and simplifies future development.

2. Data Collection Issue Resolution

   • "Screenshots are organized and sorted effectively, resolving an issue where photos were only 53 bytes."
   • Significance: Addresses a critical data collection issue, ensuring data integrity.

3. HDF5 File Conversion and UI Development

   • "In development: Converting HDF5 files into a database-like format and developing a visualization interface to display data tables on the homepage."
   • Significance: Data format conversion and UI improvements provide a more intuitive data interaction experience.

4. Simulator Refactoring

   • "In development: Ongoing refactoring of the simulator to improve its structure and organization. A preliminary GitHub Wiki page documenting the simulator’s architecture is complete (see For Contributors: Project Architecture - Simulator). Significant effort has been dedicated to this task, as detailed in Issue #34: Improve the simulator structure with better organisation."
   • Significance: Ongoing refactoring enhances the simulator’s maintainability, with the Wiki providing foundational documentation for contributors.

2. Task Priorities

1. User Experience

   • "The user interface must be visually appealing and easy to use, or people will overlook the effort behind it, especially for non-computer scientists."
   • Significance: Emphasizes the importance of UI/UX for project success and user adoption.

2. Deployment

   • "The primary goal is to ensure the software runs on a PC and is deployed to the G25 lab."
   • Significance: Deployment ensures lab usability.

3. Data Set Sharing

   • "Share HDF5 files via Invenio with metadata."
   • Significance: Data sharing supports academic research.

4. Documentation

   • "Documentation is critical to enable future contributors to continue the project and meet course requirements."
   • Significance: Documentation supports project continuity and academic evaluation.

5. Future Technical Debt: Generalization

   • "Generalization is the fifth priority, as other printers (e.g., Bamboo, Creality) have significant API limitations, and Ultimaker is the most commonly used in research, making it non-urgent for now."
   • Significance: Generalization is considered technical debt, potentially optimizable in the future but currently non-essential.

3. Data Set Plan

1. Diverse Data Set Generation

   • "Using the logo as a sample, print with different configurations: with/without supports, adhesion issues, and stringing due to high nozzle temperature, generating four data sets."
   • Significance: Diverse data sets showcase common 3D printing issues, supporting research.

2. ISO Standard Test Shapes

   • "Plan to print ISO standard test shapes to measure printer geometric accuracy and compare characteristics across different printers."
   • Significance: Standard tests enhance the scientific value of the data sets.

4. Commercialization Potential (TBD)

1. Collaboration with Ultimaker

   • "Consider contacting Ultimaker to license the software as a research tool, enhancing their competitiveness in the university market."
   • Significance: Potential partnership could expand the project’s reach, though plans are TBD.

2. University Entrepreneurship Support

   • "UCC’s Ignite program could provide funding support. Eamonn Curtin is a great contact for discussing commercialization paths."
   • Significance: University resources may facilitate transitioning to a commercial product, pending further exploration (TBD).

3. Open-Source vs. Commercial Model

   • "Consider a model with free basic features and paid extensions, balancing open-source and commercial potential."
   • Significance: Offers a flexible commercialization strategy, to be determined (TBD).

5. Project Timeline and Hardware

1. Project Timeline

   • "The project is in its 9th week, with 3 weeks remaining (until mid-June). Printing tests are scheduled for Tuesday, June 3, as Monday is a bank holiday."
   • Significance: Clarifies the project deadline and testing schedule.

2. Printer Comparison

   • "Ultimaker S5 is ideal for research with its open API, costing approximately €8,000-9,000. Creality K1/K2 is low-cost (£600-700), suitable for personal use."
   • Significance: Hardware choices impact research and commercialization strategies.

6. Meeting Summary

The meeting reviewed the 3D printing software project’s progress, priorities, and plans. Key achievements include:

1. Completing code refactoring, with the program modularized for better maintainability.
2. Resolving data collection issues (e.g., 53-byte photos).
3. Advancing development of HDF5 file conversion to a database-like format and a visualization interface.
4. Continuing simulator refactoring with improved structure and organization, supported by a preliminary GitHub Wiki (see For Contributors: Project Architecture - Simulator) and detailed in Issue #34.

Five task priorities were established:

1. Optimizing the user interface for visual appeal and ease of use, especially for non-technical users.
2. Ensuring software deployment on a Windows PC in the G25 lab.
3. Sharing HDF5 data sets via Invenio with metadata.
4. Documenting code structure and database schema for future contributors.
5. Addressing generalization as future technical debt, non-urgent due to API limitations.

The team plans to generate diverse data sets using the logo and ISO standard test shapes, to be uploaded to Invenio for research purposes. Commercialization potential is TBD, with discussions around licensing to Ultimaker, seeking UCC’s Ignite program support, and exploring an open-source model with paid extensions. The project is in its 9th week, with 3 weeks left until mid-June. Printing tests are scheduled for Tuesday, June 3, due to the Monday bank holiday. Documentation and printer preparation (e.g., cleaning the print bed) are critical next steps.

7. Action Items

1. Printing Tests: Confirm the print bed is clean and schedule tests for Tuesday, June 3.
2. Documentation: Document code structure and database schema for future contributors.
3. Data Set Preparation: Complete logo and ISO test shape printing and upload to Invenio.
4. Commercialization Exploration: Prepare for potential discussions with UCC’s Ignite program and Ultimaker, pending further planning (TBD).