waterloop / waterloop-website-old

Official website of Waterloop

General Information - How Everything Is Connected.

Current architechture.

• TODO: Every technical repository should be mapped onto the overall architechture.

Repository Overview Table For Waterloop:

Repository	Pod/Server/Dashboard?	Is it Archived?
goose-communication	YES	YES
goose-dashboard	YES	??
goose-sensors-wio	YES	??
goose-sensors	YES	YES
goose2-embedded	YES	YES
goose2-communication	YES	YES
goose2-dashboard	YES	YES
goose2-sensors	YES	YES
goose2-data-processing	YES	YES
goose3-sensors-old	YES	YES
goose3-testing-tools	YES	YES
waterloop-legacy	??	YES
wqt	YES	YES
wcomms	YES	??
wstream	??	??
wpool	??	??
wcosa	YES	??
cosa-canbus-wio	YES	??
cosa-roboteq-sdc21xx	YES	??
cosa-servo	YES	??
cosa-i2c-register	??	??
mpu6050	??	??
doc	NO	??
team-manager-front	NO	??
waterloop-website	NO	??
wcosa-test	NO	YES
team-manager-back	NO	??
wiki	NO	??
s18-software-challenge	NO	YES
waterloop	NO	NO

waterloop-website-old's Issues

TWEB-3 Learning creating 3js render of the pod

We want to have a 3js render of the pod that can explode into pieces and implode back together. Similar to how this video works http://delfthyperloop.nl/#intro
For details about pod's internal parts contact @Ruslan, but for now maybe just play around

BCK-5 Writing a sample server in GO

• Implemented UDP, TCP and QUIC
• Testing needed to determine fastest protocol

Write server in GO

TWEB#46 Building main team website

For team-website issues, use TWEB-<# of your issue>

TWEB#45 Design the wireframe for the website

BCK-1 Checksums of packets

Ability to validate the completeness of arriving packets

BCK-2 Blackbox data logging

Make sure we are logging all of the data that is being passed through the server into some sort of non-volatile memory

EMB-3 Message protocol between devices and back-end

Vertical alignment on landing page breaks on mobile

The current solution works on desktop and breaks on mobile.
Alternatives tested:

• materialize's vertical align class: same error
• br tags before h1: same error

For team-internal issues, use TMAN-<# of your issues>

Switching to UDP

UDP Problems:

• minimizing packet loss
• being able to recover lost packets
• according to most questions asked about reliability, it would be easier and faster to just use TCP which is already optimized
• simple solution would be to number each packet being sent, if the receiver misses a number, resend that packet
• Alternative:
  • QUIC
  • https://en.wikipedia.org/wiki/QUIC
  • not much support yet but has lower latency than TCP and also provides reliability
  • built on top of UDP by Google

BCK-3 Server Heartbeat

Be able to tell from the front end if the server is live and functioning well

TMAN-1 Internal website

Tyler started working on it. I think best way to collaborate would probably be creating a bunch of github issues and sort of resolving those one by one

BCK-6 Receive and send packets in I2C in GO

The idea is that we have a bunch of Arduinos that are talking to all of the sensors and we are going to define a binary data structure that we will use to send packets between backend (likely Linux) computer and Arduinos. We were planning on using I^2C for packet transfer between the Arduinos and Backend, so we have to find a way to read binary input that is sent through i^2c

BCK-1 Testing Node.JS Performance vs Go (with multiple network protocols) on a Raspberry Pi

BCK-4 Watchdogs

If case the server restarts or arduino loses power, must be able to restart and reconnect automatically

TWEB-1 Design the wireframe for the website

For team-manager issues, use TMAN-<# of your issue>

For Backend issues, use BCK-<# of your issue>

EMB-1 Memory friendly String Classes

┆Attachments: teamwaterloop/wlib: Issue #1

http://www.techbitar.com/how-to-network-many-arduinos-with-sensors-using-i2c.html

EMB-3 Message protocol between devices and back-end

┆Attachments: #3 EMB-3 Message protocol between devices and back-end

For team-website issues, use TWEB-<# of your issue>

EMB-1 Memory friendly String Classes

Main objectives:

1. Static String
2. Dynamic String to use our own memory model

┆Attachments: #1 EMB-1 Memory friendly String Classes

EMB-6 STL Integration

EMB-4 Memory management solution

EMB-4 Memory management solution

┆Attachments: #4 EMB-4 Memory management solution | memory_management

For Backend issues, use BCK-<# of your issue>

Parallax doesn't work on mobile

TWEB-2 Building main team website

Blockchains

• potentially use blockchain to store data?
• doesn't seem particularly viable / useful over normal methods

Mobile navbar is broken

• sidenav doesn't show
• overlay works
• hamburger icon doesn't show (instead displays white "menu")

For VR issues, use VR-<# of your issue>

If you create a card, make sure you add an issue key to it. just like described above ^^^. If you create a branch on GitHub, make sure you name it based on the following convention: "<issue code>-<# of your issue> short summary". An example would be: "EMB-

font size on front page does not change on mobile/page resize

Materialize is unable to handle this for some odd reason

For embedded issues, use EMB-<# of your issue>

EMB-6 STL Integration

┆Attachments: #6 STL Integration

For embedded issues, use EMB-<# of your issue>

EMB-9 USART implementation

If you create a card, make sure you add an issue key to it. just like described above ^^^. If you create a branch on GitHub, make sure you name it based on the following convention: "<issue code>-<# of your issue> short summary". An example would be: "EMB-

Wlib Code style consistency

┆Attachments: #8 update wlib code style

Create a communication standard (using bits)

Define a structure to send messages from embedded to backend

┆Attachments: #3 communication packets standard

TWEB#47 Learning creating 3js render of the pod

EMB-6 STL Integration

┆Attachments: #6 EMB-6 STL Integration

EMB-9 USART implementation

┆Attachments: #9 EMB-9 USART implementation

If you create a card, make sure you add an issue key to it. just like described above ^^^. If you create a branch on GitHub, make sure you name it based on the following convention: "<issue code>-<# of your issue> short summary". An example would be: "EMB-

EMB-3 Message protocol between devices and back-end

┆Attachments: #3 communication packets standard

EMB-9 USART implementation

┆Attachments: #9 EMB-9 USART implementation

EMB-4 Memory management solution

┆Attachments: #4 memory management solution | memory_management