Rachel Zhao’s Status Reports for Mar. 18

This week I focused on the Ethics Assignment. After reading the paragraphs that are posted, I gained a new understanding of what ethics in designing a capstone project is and what I can do to make sure my project stays ethical.  We also planned a meeting to further discuss the ethics in our project as a group.

On my own part of work, I am mostly confused when working on my own. Since I have not been working on a web development project since a year ago, much of the knowledge is forgotten and I am struggling to fulfill the demand of the group. I am not sure what I can do about the situation I am facing.

I plan to reach out on stack and see if there are any TA who is experienced in website development, and I will also dig deeper into the ethic of our project by listening to the lectures given next week.

Jasmine Yew’s Status Report for March 18

This week, I created our web app’s registration and login pages and also the class Ethics assignment. In addition, Sydney and I worked together to implement the Bluetooth connection between our device and the web app.

The login page of the website
A temporary page to connect our web app to the device via Bluetooth

With our newly updated schedule, I am currently on schedule and hope to next week be able to send and receive data properly, such that I can complete the feedback page.

Team Status Report for March 18

This week, we primarily worked on the website and getting the Arduino to connect. Since we recently decided to create a web app rather than a mobile app, we’ve had to look at different solutions for connecting our website to the device. One of the biggest risks currently is being able to properly receive large amounts of data sent from the Arduino on the web app. To mitigate these risks, we are looking into solutions where we read data in chunks of bytes. We are currently behind schedule because our parts only arrived this week and due to Rachel’s recent procedure, we have not been able to get as much progress done as planned. However, after shifting some tasks around and changing the amount of time for each, we should still be on time to finish our project by the final presentation.

Our updated schedule

Sydney’s Status Report for March 18

This week I worked on the Ethics assignment, as well as beginning work on the hardware interface. Our boards finally arrived, yay! So far I have managed to get the basic example working, meaning that we can read sensor data from the IMUs. I am still working on getting the on board quartenion processing working. I also worked on configuing the boards bluetooth to work with our web application, which created a potential concern for me. The Arduino web bluetooth library and the DMP library together might occupy all of the on board arduino memory without even including anything extra for our program. So this is something I am going to start investigating next week when I will probably try and combine the two. Worst case scenario, I think we will just offload the quaternion processing to the web app. On the github, you can see the work I have done / played around with under ‘hardware’. Looking at the schedule, while I am currently behind, I think I will be able to catch up next week as configuring the sensors doesn’t appear to be as much of a problem as we originally anticipated.  As I did meet the goal of reading data from the devices this week. Next week it shouldn’t be much of a problem to get the IMU’s placed onto our fabrics.  I will also try to get the MUX working so that I can read data from all of the sensors, not just one.

 

https://github.com/jasCode-s/liftOff

Team Status Report for Mar. 4

This week our team focused on building the design review report and had a few instructing discussions on where we are focusing based on our current resources and capability. Jasmine is on track to work on the website development part of our project, while Sydney is waiting on our parts to arrive.  Rachel had a medical accident that made her hospitalized and unable to catch up on work during spring break. Our team is planning to discuss redesigning the schedule based on the current setback and hardware and human resource limitations. We also look forward to receiving advice from the faculty and course staff. Our plan next week is to reach out to ECE receiving office to check on the arrival of our parts and to order some parts at a faster speed if it is financially allowed.

Zhichun Zhao’s Status Report for Mar. 4

This week I mainly focused on building the design review document. We held multiple team meetings together to discuss further details of the design, and we are becoming more explicit about our design goal.

Due to a personal medical accident, I was hospitalized and could not work during spring break, during which I planned to work on website development. I plan to reach out to the course staff and my group mates to see if we can adjust the schedule so I can catch up on my work. I am also concerned about the parts that we are still waiting on. I reached out to course staff and the receiving office of the ECE department and have not gotten any response yet.

Sydney’s Status Report for March 11

This week I primarily worked on the Design Review Report. This was helpful in forcing me to think even more about our design. I also placed the order for our batteries as well as the fabrics we are going to put the device on this week. Outside of the design report, I wasn’t able to get much done because I am still waiting for the parts to arrive. I am starting to get pretty concerned about this.  I am not sure that we have any back up plans for if the parts take much longer to arrive. Finishing this up at the end of spring break, they are still not in, so we will begin reaching out to the appropriate resources and potentially looking at ordering from a different vendor with rush shipping on Monday. We are falling behind schedule, but this week I will work on connecting the arduinos to the web app as we don’t have the IMU’s yet, which will let us get rid of some interfacing time at the end(hopefully).

Jasmine Yew’s Status Report for March 11

This week, I primarily worked on the design report and also began working on the web app after we made a decision to pivot from making a mobile app and doing a web app instead. So far, I’ve created the base layout for our log and feedback page. However, in order to complete the feedback page, I will need Rachel to finish the tracking page so I have the proper layout. In addition, this week I created the object models and forms necessary for our app to function.

Models we will be using in our implementation

Currently, I am on schedule because I already have most of my implementation of the feedback page done. However, the rest of the feedback page’s implementation does rely on the data read from the sensors and the completion of the rest of the web app. Hopefully, by next week, the sensors will have arrived so I can begin working on my algorithms. By next week, I also hope to have finished the implementation of the feedback page where I match the feedback to the exercise and also compile a list of different feedbacks we can give the user depending on how their set was.

A general layout of our home/log page
A general layout of our feedback page

Zhichun Zhao’s Report for Feb. 25

This week I focused on working on the slides for the design presentation. I also spent time outside of the lecture working on practicing the presentation. Besides, our team came up with a list of components that we want to buy and I submitted the order request for the group. We have already received one of the parts and we are still waiting on the rest to come. On top of that, I tried to find help on mobile app development on the slack channel, but so far I haven’t found any help. I am biasing my work on the knowledge I learned from 17437 web application development. I am planning to learn flutter by watching Youtube videos and find educational websites.

Jasmine Yew’s Status Report for Feb. 25

This week, I set up the team repository and have begun writing the feedback page. I am currently on schedule, however, I am slightly worried about the implementation of the mobile app since I am not the most familiar with Dart. In order to make up for my unfamiliarity with Flutter, I hope to spend most of my time during spring break experimenting with it and finishing my implementation of the app. My goal for next week is to complete the feedback page and the design report.