Aro: It was a good sprint for us because we made good progress toward our project. My primary objective was to tackle the software side: setting up the Fitbit developer environment and establishing a working connection between our code and the AxiDraw plotter. This sprint was a success because we achieved the deliverables set out in the plan by establishing the core infrastructure for data extraction and machine control. As we did in the first sprint, we divided the tasks and remained available to help each other. We look at each other's progress and help one another when we get stuck. 

• GitHub Repository and VS Code Setup: I successfully set up the initial code, got the project running in VS Code, and established a functional GitHub repository. The repository, https://github.com/Arohasina/patina-engraver, now includes a detailed README with installation instructions, setting the foundation for collaboration and version control.

• Fitbit Data Integration: I worked on extracting step data from the downloaded Fitbit data file and successfully set up initial code scripts and a virtual environment. The running of the load_steps.py script successfully demonstrated the ability to access and display step count data on the terminal.1

• Programmatic AxiDraw Control: establishing direct control over the AxiDraw using a Python script, moving away from manual designs in Inkscape. By running the draw_triangle.py script, we successfully got the AxiDraw to draw a triangle, achieving basic line drawing for initial data visualization.

Challenges: My initial challenge was tackling the software requirements, specifically understanding the Fitbit authentication process and connecting to the tracker data. But after looking at the blog I linked in our DDS, I realized we can just manually connect the Fitbit to our Google account in the Fitbit app, then download the data in CSV format directly from there to use. In the next sprints, I plan to automate this process. The other challenge was connecting to the axidraw machine and getting it to work with a Python script, but after reading the documentation at this link, I was able to figure it out. 

- 

Galina:

In our second sprint, Aro and I focused on expanding our physical prototype to include a pouch container for the tracker itself and working on system integration, specifically setting up the Fitbit API. Aro primarily worked on the technical side by setting up the Fitbit developer environment and getting the code running in VS Code, while I focused on refining the physical prototype.

My main contribution was improving the wristband by designing and attaching the pouch container and updating the magnet system. I made the magnets smaller and more flexible and added two levels to better fit different wrist sizes. I also sewed the pouch onto the band and reinforced the structure with silicone glue, making the prototype more refined.

A key achievement this sprint was successfully setting up the Fitbit API and getting a working codebase, which is an important step toward connecting data to our physical output. Compared to the last sprint, we had fewer major blockers and were able to make more consistent progress. Overall, we worked well by dividing responsibilities and will move forward by focusing on connecting the Fitbit data to the AxiDraw so we can begin actual data visualization.