-
Notifications
You must be signed in to change notification settings - Fork 0
Davis Alexander
dangerdave10 edited this page Dec 4, 2014
·
20 revisions
- Program spits out "after.csv" to create second visual for after the greedy algo is implemented.
- Prep for presentation on Saturday, December 6th.
- Finals week (Dec 8th - Dec 13)
- Simulator up and running.
- Program spits out "before.csv" to create visual for 100 clients, 10 servers, 7 groups.
- Next Step: Create basic algorithm to minimize communication between servers + test.
- Next Step: Spit out "after.csv" to show effect of running algorithm.
- Simulator is up and running.
- Create Visualization in progress -- need to make "writer program" to output to CSV file.
- Next Steps: Take first shot at algorithm to minimize communication between servers.
- Next Steps: Create visualization step for "after runnning algo"
- Next steps: Prep for demo scheduled Dec 6.
- Simulator spawns x servers, and spawns y clients ( x and y are user inputs).
- Currently, we have a group restriction - clients are spawned with a random Group ID (value between 1 and 5)
- George continues to work on the Functional Requirements ( we call it the 'PAPER' now)
- We have yet to start working on the visual as Dr. Vidal suggested last meeting, that is currently our focus now -- figuring out the organization of the file that needs to be output and creating it.
- Met today with the group.
- Talked about restructuring the organization of our modules to include an overseer, a simulator and then the algorithm module.
- Scheduled to meet again on Sunday (11-14-2014) at 4 pm to hack at coding the ideas we discussed.
- Team meeting with Graham and Paul in attendance.
- Discussed how client allocation on server should be randomized.
- Tried to figure out cost function -- what needs to be spit out by the simulator.
- George has taken over work on Functional Requirements documentation.
- We need to find some time together to hack at the simulator and implement proposed changes.
- Had Skype meeting with client and rest of the team.
- Figured out Makefile config with Graham.
- Need to build Functional Requirements doc.
- Created "Specific Description of Problem" in Wiki
- Added visual aid to the page
- Met with team to discuss how to proceed with simulator.
- Looked at Getting Started with Erlang guide to some concurrency implementations.
- Ran a ping pong message transaction in Erlang
- Ping sends message to pong, waits to receive.
- Pong receives msg.... sends msg to Ping... waits to receive.
- Discussed mathematical model with Prof Vidal and the rest of the team.
- We will focus on our primary issue - that is minimizing the overall communication between servers.
- At this time - load-balancing is NOT a priority.
- Next steps
- 👍 Look at creating an algorithm
- 👍 Creating a simulator to test algorithm
- 💯 "The main deliverable for this team will be a simulation, in Erlang." ~ Vidal's notes.
- Talked to my Math professor to get a better understanding of the mathematical perspective of the problem.
- Need to discuss this with the team -- see what they think.
- Need to figure out with the client as to what takes precedence:
- do we minimize overall communication between the servers
- do we focus on distributing load over the servers
- Contacted Drew (our client) for a better understanding of the project goals and deliverables.
- Drew compiled our Project Description page on the wiki with what he'd like to achieve.
- Research on hold - midterms this week (Sept 22-26)
- First meeting with client (also our mentor) took place
- Discussed scope of project and more immediate to do's
- Added client to git repo
- Decided meeting time with Dr. Vidal -- Wednesdays @ 8 am starting Sept 24th.
- Put Resources and Links page together (Research in progress)
- First meeting with client scheduled for Sept 16, 2014
- Git repo setup
- Milestones setup per course website
- Personal log begun
- First meeting took place
- Decided on meeting place and time, communication mode, team name, roles, etc.