Logbook

Starting this week, we got to know each other, had our first team building meetings and were presentated the possible choices of the upcoming project.
On the weekly meeting on Thursday, the proposals were explained more detailed to give us an overview of what was necessary to do and achieve for the different projects.
After discussing the various opportunities within our group we made a list of preferences and sent it to Benedita.
A few hours later we knew that the project we'd work on for the next 4 months was a relatively large aquaponics system and mainly the controlling and monitoring referring this system.
This should be achieved by creating a mobile device function to give an instant overview of data like temperature, pH-value, conductivity.

Things get started.
This week didn't only bring us summerly weather but also the first steps to work on our project.
Before having the first Thursday-conference, we had to be clear about the uncertainities and questions we had left regarding the aquaponics system and the objective of our project.
In order to work together in the most efficient way, we created a facebook group as well as a Google Drive folder, so we could simultaneously edit and upload files for the project.
Moreover everyone could have a direct overview what needs to be done and what already has been worked out.
Additionaly, we nominated Arick as the group leader to bring a solid structure into the organizational part of the team work.
On Thursday we could discuss all our prepared questions with our supervisors. This helped us to finally get started to work on different, more specific tasks.
The first step here was to get an overview of the upcoming work and with these informations start to create a Gantt Chart.

After last week's tast definition and allocation everyone had to start working on their specific fields of work.
Doing this, we made an approach on the introductions of the several chapters of the report. Furthermore the website, programming, component research and studies on the circuit and electrics were worked on.
Concerning the marketing part of the report, we furthermore started analysing the external environment as well as the competitive situation.

Main objectives in this week were finishing the components list to meet the deadline and to work out the marketing plan until the positioning could be defined further.

Easter Break
The interims presentation was begun and worked out.

Break was over and we all met again to discuss the interims presentation as well as the content and specific task allocation.
We spent Wednesday practicing the final version of the interims presentation and held it on Thursday.
Further project management tools and methods were introduced and started including R&R Matrix, extension of WBS and Gantt and Risk Register.

After the interim presentation we got feedback from the teachers. We used this feedback to make improvements in our Wiki report. Such as the following chapters: Marketing Plan, State of the Art, Ethical and Deontology, Eco-efficiency Measures for Sustainability and Project Management.

Further on, the industrial design student in our team made a new 3D design of the feeder. This was before we were told that we are going to buy one instead of building one.

And as it should be, our Web app had some improvements as well. The login credentials were reconfigured for the ISEP database account and the code structure was also updated. Then we started to work on the access terminal through SSH via Python commands, using a personal Raspberry Pi because we don't have access yet to the one we put in the components list.

We continued with the improvement of our Wiki: Marketing Plan, State of the Art, Ethical and Deontology, Eco-efficiency Measures for Sustainability and Project Management. We also finished the component and the budget list. The calculations for the heater are still in progress. Further we started to work on the stakeholders register and the design of the website.

Project Management chapter was mainly finished, also Eco-Efficiency and Ethics got the final touch. We started to take footage and pictures for the video and figured BiBtex out. Also the coding was continued to be developed since we received our first materials.

We got final feedback on the marketing section, worked on improvements regarding motivation section as well as parts of the project management. Arick started to do the user manual and Jan continued to code. Francisco managed to finish the chapters about ethics and sustainability.
Furthermore we worked on report details such as glossary and BiBtex was introduced to all members of the team. Viorel worked out a 3D model of our future box including the electronics parts and ports.

The almost completed report was reviewed and checked. Feedback from communications class was taken into account.
Since the components arrived entirely we were able to start building the blackbox which will contain all components to control our system. Furthermore the work on the video continued and chapter 5 and 6 needed more detailed improvements. Coding gets into its final phase, so testing and functionalities can start soon.

1. Presentation
2. Modus operandi
3. Project proposals
4. Electronic Logbook

The several proposals were presented and explained by the teachers, then discussed within the teams.

1. Discuss any further uncertainties and other questions the team has in order to start working on the project.
   
2. What happens if you exceed your budget?
   
3. Do we have access to a functional aquaponic system? If so, where and when?
   
4. If we make a phone app, do we have to make it for Android, Windows and Apple?
   
5. What functionalities will the app have?
   Do we need a phone app or can the controls be web based?
   
6. Are the controls specified in the proposals all that we will need?
   
7. Does the system need an independent or back up power system?
   
8. Who will determine the fish and plants?
   
9. What exactly will we need to present on the 9th of April?
   
10. Is the material list definitely final?
    
11. What happens in case we need more/stuff breaks?
    
12. Do we only do the shopping list or “shop” ourselves on- and offline?
    
13. Is the use of ONLY freeware mandatory?
    
14. Is there any equipment left from last year which could be used for our system?
    
15. Could we use material to lend for another people?
    
16. Could we include in the program a sensor to determine when we would have to change a component?

Each member of the team came up with their questions, regarding the execution of the project. These questions were then sufficiently answered by our supervisors.
The requirements of our task and the milestones were reviewed more detailed.

1. Leave out flow-sensor
2. Gantt-Chart
3. Blackbox-diagram
4. Website

Throughout the meeting we discussed several points. The blackbox-diagram of the first circuit design was presented. Furthermore we talked about the necessity of a flow sensor or eventually other sensors to measure the water level.
Concluding, we reviewed the process of our wiki page and the report.

1. Components
2. Diagram
3. Functionalities

components_budget_excel.xlsx
schematic_v3.pdf

The components list was the main topic of this meeting. We were also advised to pay attention to the correct use of units in our list. Another point was the accurate maintenance of the wiki-page.

• Improvement comments on the wiki report
• Bibliography (use this example; add first the bibliographic reference in BibTex to your refnotes.bib file)
• Glossary: How do we link sources for definitions? In the table?
• When will we buy the components? Because some of the components are out of stock now and we keep editing the component list.
• Who can help to find a motor for our feeder and a spindle?
• With who do we have to speak for light leds?

We started this meeting by going over the changes we made in our Wiki report. Then we got some suggestions on the bibliography and on the choice of the Arduino and the Raspberry Pi. We also discussed the purchase of the feeder because building one would be more expensive than buying one. For the light leds the teachers redirected us to the technicians room where there should be leds for our team.

For the next meeting we should try to finish the components list and brainstorm about making the tank more presentable.

• How specific should the work on the codes be described? (a block diagram, flow chart(s) and relevant code snippets)
• What are the poster requirements? (A3)
• What are the video requirements? (5 min in free style)
• What are the paper requirements? (template provided in Moodle)
• When do we get the materials to start working on the product? (in principle, 2.5 weeks after handing in the final list of materials approved by client and direct supervisor)

components_budget_1.xlsx

Video: Focus either on EPS, team work, project and final product experience. Animations, drawings, pictures, video sequences, we can use everything we want.
Paper: Paragraph on development, discussion, sustainability, marketing, each chapter but only the core content referring to our product. 8-10 pages.
Formula: international units (kg).
Feeder: once every 24 hours fish are fed. In case it's not enough, we'd like to control the period of feeding by opening the feeder and access the eletronics. Connect servo motor controlled by Arduino.
Components list: Include tax and delivery.

• Tank modification is neither in budget, requirements nor in time schedule. Do you still want us to think about this issue? (Yes)
• Is there a minimum scope for the report regarding quantity? (You mean number of pages? No. It must report all things you did through the semester to develop your solution and allow a reader to replicate your prototype.)
• Bibliography –> should references in the text be written in [number of bibliographic order] or (author, year, page)? (You can choose)
• Feedback on the report is welcome (Yes, in two weeks.)
• What format do you want the final report in? Is the Wiki “Download as PDF” sufficient? (You should download it as ODT, then edit it, create the front, the tables of contents, figures and tables, make sure that chapter start at odd pages, etc. and. finally, generate the PDF.)

- Tank:we still should think about this issue.
- Report:

1. in developing the report it doesn’t have to have a minimum of pages. It must report all things we did through the semester to develop ours solution and allow a reader to replicate ours prototype.
   
2. Bibliography: We can choose how to write the reference: (number of bibliographic order) or (author, year, page)
   

- Format final report: first we should download it as ODT, then edit it, create the front, the tables of contents, figures and tables, make sure that chapter start at odd page, etc and finally, we generate the PDF.

General feedback of the report. What are our weakest points of the report?

• We need to complete 1.3 Motivation.
  
• Complete in 1.5 Requirements with data about the budget.
  
• Instead of “table” and “figure” use “Table” and “Figure”.
  
• Add a new chapter in State of the Art about our prototype product.
  
• Correction in text about references and in mathematical formulas.
  
• Add Conclusion in chapter 5.
  
• Change i.e. and e.g. in italic style writing.
  
• Add subchapters in chapter 7.1.
  
• Write in chapter 7.4 Functionalities about diagrams, navigation map, flow chart for arduino and raspberry and important code lines.
  

• When will all the components be available?
• The cross-references for maths equations don't work. (Change the MathJax plugin configuration accordingly)
• From Planning: “Hand in a CD with the corrected deliverables (source + PDF)”. What do you mean with source? (A CD containing the sources in Word, PowerPoint, Arduino code, etc. as well as the PDF versions of all deliverables must be handed-in.)

• Wait for the MathJax Plugin to be changed. (supposed to happen today).
• The CD should contain ALL deliverables in editable as well as non-editable files.
• Paulo and Benedita had some suggestions about the connections. (Jan knows)
• Paulo:“Be sure to use some ventilation.”
• Benedita:“In the meanwhile you can test all the code and sort out how to do the layout.”
• Deadline for the 12th includes the entire day until midnight.
• Regarding the Report: Chapter 3-6 you get the feedback from the teachers. The supervisor jury won't discuss these. Chapter 7: Caption for the first figure is missing (“Navigation Map”). “How frequently does the Rasberry Pi write in the database? Do you think it's necessary to check the status every 5 seconds? How frequently is the database updated? Make sure the intervall is discussed with the client.”
• Website: Put update time on the “change” page.
• Benedita's suggestion to think about: It should be Arduino which writes directly in the database. Rasberry is the higher level controller.
• Chapter 7: whitespace between numbers and units. Also units are wrong (kg not Kg) and so on. K for constant needs another variable.
• Proof current is too high from camera, Arduino etc. for USB hub to manage. It's part of the design phase.

• Questions/comments on the marketing deliverable.

Answer: Please address this question to the marketing teacher

• Is it possible to shift chapter 8 to the 25th of June? It might only be possible to draw a final conclusion at the very end.

Answer: No. The very end of the project is the 18th of June. The last week is to improve the deliverables, i.e., include the corrections include corrections provided by teachers and supervisors, and the prototype, i.e., just work on details.

• Do figures included in tables need extra titles/numbering?

Answer: No, if the table is cross-referenced in the text whenever the figures are referred.

• For the report as Word file: is it allowed to snip/screenshot, e.g., tables? Answer: Tables are to be created as tables and not as images.
• Will it be sufficient to copy/paste Bibliography to the Word file?

• We'd like to show the video and ask for feedback/improvements.

Refering to comments in the agenda section.

• Are we allowed to cut the given plastic box that will be installed at the aquaponics system?
• Can we review the poster requirements?
• How does the final evaluation will be handled?
• Feedback on the black box (we bring it).