Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

That one team that's clearly slacking #4

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

That one team that's clearly slacking #4

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d11c8ad
initial push
LFJake Nov 11, 2014
aa57edf
Update README.md
jakecharland Nov 12, 2014
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 27 additions & 18 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,39 +15,48 @@ Project Outline
--> 200 Total

## Team Members
* Person
* Person
* Person
* Person
* Person
* Jake Charland
* Alex Tsankov
* Austin Wood
* Dawson Bradford
* Nikolas Fejes

## GitHub Repo
[As a way to share your project code and handle submissions, please create a GitHub Repo and place the link here so we know where to find your work]
https://github.com/dawsonbotsford/soundvisualizer

## Project Sketch
[Use this section to sketch out the working parts of your project. The project may change as you go, but try your best. Describe how you intend to capture your data, clean it, analyze it, dump it, and vizualize it. How will you set up your hardware? What things are still uncertain and what things do you feel confident about? What will be your process to get each of these things in working order? How would you like your display to be 'triggered' in the installation?]

## Hardware
[This is a preliminary list; it will be finalized in a meeting with Mike (see below)]

1. List
2. of
3. needed
4. Hardware
1. Sound sensor (maybe multiple?)
2. Arduino & Raspberry Pi
3. Web server hosting (DigitalOcean)

## Roles
Given the varying expertise and interests, I'd like you to outline what team member will be responsible for what parts of the project. It's okay if 2 people want to share certain responsibilities. This is mostly for your own organization and, if things get rocky, so Mike knows who to talk to in the group.
Austin, Dawson- Visualization
Alex, Jake- Hardware server data exchange
Nikolas- Hardware/data cleanup

## 4 Milestones
[Please list 4 Project Milestones you'll complete week-to-week to show your progress. You will need to turn in some tangible example to prove you've completed 1 milestone each week. Some combination of code snippets, data, screenshots, picture of the hardware setup, etc. If these milestones need to change slightly, that's OK, as long as you tell Mike and Tom at least 2 days before submission (and as long as you haven't arbitrarily reduced the workload)]

1.
2.
3.
4.

## Propose 3 Meeting Times
[You'll need to meet with Mike sometime during the week of 11/10 to finalize these details. For this your whole team should try to be available for a **30 minute** meeting. Mike is unavailable from 12-1 MWF and 12-2 TTh so don't propose those times.]

SERVER
1. Decide on server stack (express).
2. Show that server is live and can make an api call.
3. get real data from nikolas.
4. Live Demo.
HARDWARE
1. Get hardware from mike and set up that hardware
2. Show that you are retrieving data and format it in a json string for sending over the wire.
3. send real data to jake and alex.
4. Live Demo.
VISUALIZATION
1. Mockup what the visualization will look like.
2. Show visualization on dummy data.
3. show that you can get real data from our server.
4. Live Demo.

AND FINALLY... Remember to have fun! This is going to be a challenging project, and there is going to be some tough hurdles, but it should be a good time if you get into it and get excited about what we're creating. Mike will do his best to be available and around ATLAS so that in the evenings if students need to come in and work or try things, we can set times to do this. Also we'll have a hardware expert [Abhishek Narula] from ATLAS who will help us in the process.