Skip to content

Meeting notes

Konrad Bryłowski edited this page Jul 24, 2024 · 21 revisions

Space for meeting notes - decisions, tasks etc.

Introduction

Edit this page and add notes from a meeting at the end. Put meeting date on first level header (#) and in the next line the main topic of the meeting.

11.03.2024

Topics:

  • web app or mobile app
  • research - existing apps/projects, how they work etc
  • team organization

Decisions:

Tasks:

  • research existing solutions

13.03.2024

First meeting with the supervisor - general ideas, background of the project, organizational advices

  • idea: photo before and after a game, output: all elements are present or some are missing
  • game is only an example, may change topic
  • first iteration: some elements from different classes with known quantity
  • second thread of the project: how to add new topics, games etc.
  • thesis:
    1. Introduction
    2. Analysis
    3. 3/4 pages about roles, tasks descriptions and who did what
    4. Methodics and team work
    5. Technologies (eg pytorch - what it is, why is it used here)
    6. Final product
    7. Conclusion
  • deadline: 10/12/2024
  • should have programming done by the end of October, November - thesis
  • maybe PWA, search for what web can do
  • next meeting 27.03.2024 19:30

18.03.2024

First iteration plan.

  • we need research about PWA
  • architecture: model and database, UI communicates with backend via API
  • saving results for some time (cache for example) referenced via for example hash

27.03.2024

ML research - meeting with supervisor

  • two team members will research two approaches to ML aspect - single shot and multiple shots learning
  • next meeting - 10/04/2024 19:30
  • found a book on the topic "Hands-On One-shot Learning with Python" (available on O'Reilly)

10.04.2024

ML research, one team member sick

08.05.2024

ML resarch results - YOLO v8

  • next meeting - 29/05/2024 20:30
  • TODO: further experiments: add some constraints (eg white background) to have working app and then work on removing them, if the whole team is not needed work on UI and communication interface

05.06.2024

first tries with model, UI and backend with upload and basic (mocked) response

  • next meeting - 19.06.2024
  • TODO: database (begin with sqlite), user results history, improve the model

19.06.2024

Project progress - user authentication, bounding boxes in UI, model

  • next meeting - 17/07/2024 20:30 24/07/2024 19:00
  • confirm one week before
  • next main goal: integrate UI, backend and the model

21.07.2024

Program flow:

  1. User sends an image
  2. User picks at least one point for the background and sends them to the server
    • selection types: positive/negative
    • sent in form of tuples, px
    • can be done meanwhile the client is sending the input image
  3. Server responds with a selected background
    • format: mask that's the same size as the image, 0 false, 1 true
  4. User can optionally make changes in their selection (goes back to step 2., the server responds with a new background)
  5. User confirms their selection with the server
  6. Server responds with a result
    • first without classes

24.07.2024

Project progress

TODO:

  • consider non-relational db for data storage
  • UX
  • experiments with real life datasets
  • finish work on user accounts
  • consider possibility of counting sum of several photos

Next meeting: 21/08/2024 19:00 - confirm one week before

Clone this wiki locally