November Update #3

Accomplished this past week:
Sam - Working on Report, Redesigned power circuit for new IC. Passing BOM to Matt to order.

Ian - Tested parallel code with shared resource using a mutex, wrote section of report.

Ogi - Picked out a camera model and working on report. Dr.Bao proposed buying another model (Canon SX710) and seeing if that one works.

Matt- Finished Poster, working on final report, parts order waiting on Sam

Goals for this week:
Sam - Focus on documenting power circuit design, provide analysis for final report and revise material from midterm report. Get report material finished ASAP. Get Bill of Materials finished ASAP.

Ian - Focus on pseudocode for project, document and analyze software needs (streaming, libraries, everything needed to prove that software needs are analyzed and addressed.) Document this as part of the Final Report ASAP.

Ogi - Focus on more background research -
- Get prototyping parts from work
- Check with work to see if they can/will 3D print our case once we design it
1) Selecting and using an embedded camera (example model)(2nd link)
2) How the technologies of the project are used in a relevant sense (see old reports for examples of what to talk about).
Document these as part of the Final Report ASAP.

Matt - Place parts order when available, write BLE material for final report ASAP.

Meeting activity:
- All members present, all worked on writing and compiling the report. Anticipated deadline following Monday (along with poster submission).

Upcoming Deadlines:
- Design Poster (Monday, 16 November)
- Final Report (Monday, 16 November)

Notifications:
- Everybody must start writing documentation/report material for their work and use Word format, submit to Google Drive folder "FINAL REPORT". All material is PAST DUE. Submit ASAP.

Notes:
- Write Word doc updates on each of your weekly tasks and use them to compile your section of the Final Report.
- Use Word docs for compiling your final report material
- Check your email and this blog frequently

- Here's what we need to develop for the Final Report:


1) A complete parts list for the project must be formed

2) The project circuits/schematics must be captured/simulated to prove design

3) The errors/weak spots of the midterm report must be addressed

4) More background must be researched/provided

5) Review design specs - All design choices must be supported with analysis

6) Provide Analysis of complete design - All design choices must be supported with analysis

7) Schematics include pin-out level, RefDes #s

8) Software flowcharts/pseudocode, algorithms simulated, libraries tested, OS formed

9) processors documented and required software identified, communications described


Breakdown:
Sam - 1, 2, 3,      5, 6, 7
Ian -           3,      5, 6,     8, 9
Ogi -           3, 4, 5
Matt - 1, 2, 3,      5, 6, 7