Project Update 14.4.

Work begins on finalizing parts of the project into one cohesive product. Work continues on the website which will be the part that is the most visible to potential customers, and how the project could be marketed better. Our sensor team has successfully sent data from the sensor to our server, and our database has been set up. We still need to figure out how to display the data on the website and how to incorporate our machine learning predictions into the displayed data.

Project update 6.4.

Work continues on the project, we got some new usable data from the city of Turku to train our machine learning algorithms. That data has been pruned and sorted into a usable format. The data was given to us in an Excel sheet, from that we needed to pick out the needed values and then turn it into a json in and sort the measurements by the timestamp.

Flask for the server is in a deployable format and is pretty much ready to go. Work still continues on the visualization of the data in a website format, and machine learning algorithm is getting training from the newly acquired data.

As for sensor deployment, in the current situation we are probably going to deploy the sensor at one of the group members' home to get some usable data from our own sensor, as we can't deploy them to the school.

Project update - 24.03.

Current situation

Because of the current situation with COVID-19, we have been working remotely on the project. Our sensor is nearly deployment ready, the secure connection and integrity token are being worked on. On the server side we are working on our database and receiving the data from the server, and then processing it. We have successfully sent data in a home network from the sensor to a flask receiver, and we are working on deploying that with the IoT connection.

Next steps

Our next part of the project that needs to get started is the visualization of our data, through a web page on our server. We need to decide on who starts working on the web page as it is a vital part for sales purposes. A potential customer isn't really interested in the back end code side, but the front end visual side of the results is important. That's why we need to start working on it as fast as possible to get a good front end to sell.

ICT-Showroom Report

How did it go?

It went well, we had quite a lot of people that were interested in our project and asked a lot of questions about it.

How did we manage? What was good and what was not so good?

We managed to do well in our opinion. The position of our stand was ok but not ideal, when people were visiting the other stands before us, they kind of blocked the way to our stand so that might have limited some people from coming to our stand

What did you learn out of organising & participating in the Showroom?

Overall organization and planning in short amount of time. Most of the group have never really done any stands before so it was something new to set it up and answering different people's questions about our project.

What did you learn out of the other projects?

Other projects had interesting ways on approaching their tasks compared for instance how we would have done it. Overall stand presentations especially for some of the game projects were awesome. Also, generally more information regarding what and how the projects are going.

What would you do differently next event?

Stand setup could be overall little bit better and more interesting, for instance with more graphical showcase say with PowerPoint on how our project is meant to look like in the end.

Sprint review/planning

We had our sprint review and planning on Friday 14.2. Below are the main pointers. Overall, we feel like the project advanced nicely this sprint, and we got some important work done.

Tasks we got done in the last sprint:

• Poster done
• NB-IoT connection working
• Raspberry code almost done
• Machine learning code close to done
• Started working on the server

Tasks we need to work on the next sprint:

• Pi to server connection needs to be done
• MongoDB needs to be established on the server
• Some test results from the sensors to test machine learning
• Attend ICT-Showroom

Jan will continue as our scrum master for this sprint.

Our Trello board

Week Report – Week 7 – Server connection

Tuesday 11.2:

On Tuesday we didn’t have much to do as a group, since we were waiting to get a response from Tommi regarding some questions we had about the server. Because of this we thought it would be best for us to have the sprint review/planning on Friday, when we know more about the server and what we need to do next.

Friday 14.2:

On Friday we finally had the answers we needed regarding the server, and we could get on with working on the connection and database. We also had the sprint planning/review, which we will be covering in another blog post. Ife and Anastasiaa showed the group the poster they made for ICT Showroom, which is pretty much ready to go. Finally, we updated our Trello board to match the sprint planning/review.

Happy holidays!

Week Report – Week 6 – Posters!

Tuesday 4.2.

On Tuesday we started with a lecture on posters, since we need to make a poster for ICT ShowRoom. Anastasiia and Ife also went to the poster workshop after the lecture to get our poster started. While most of were attending the lecture, Matti and Jan were meeting with Tommi about the server details. When we met after the lecture, they briefed us on the meeting, and shared some tasks which we need to do next to get the server connection up and running. These tasks included for example registering a free domain, getting an SSL certificate and proxy, and deciding on the database we are going to use on the server.

Friday 7.2.

On Friday we mostly researched the tasks we were given on Tuesday. Ife got us a domain and we decided that we will use NGINX for our SSL proxy and MongoDB for our database. The implementation of these will require some more research and we need to get answers to a few more questions from Tommi, but the process seems to be moving along nicely!