Course project: Networked cameras
Course program and project description
- The dedicated course program for the project is here.
- Background, overview, and requirements are available in the project description. Still refers to old cameras Axis211A. New cameras are named Axis M3006V.
- Lecture 9: Project introduction (including introductory material on sockets). Some additional material on TCP sockets.
More information and download
See the links to the left.
Suggested schedule (per week)
The project description describes the suggested work plan. Below is a short summary of the contents of the document:
- Introductory meeting. Starting on design. Starting preparing design document.
- Make, and document, a high level design showing the required threads for the system and how the threads communicate with each other. Document which thread is responsible for triggering the various events in the system (send image, change between movie and idle, etc). Submitting design document.
- Make sure that you have gotten some part of the system running using the fakecamera API. No scheduled course meeting.
- Run some parts of the system against the real Axis cameras using the cameraproxy API. No scheduled course meeting.
- Test running your systems on the actual cameras using compiled Java via the LJRT compiler. Full system ready. Submission of web site containing software and documentation.
- Prepare presentation and review another groups system until last course meeting. Final meeting.
The examination procedure and contents of hand-ins are described in the project description complemented by information in the email sent to each group. These sources should be used when preparing hand-ins and final presentation.
The introductory lecture and the information below hold a summary of that information as a quick reminder (not to be used as ground truth when preparing the hand-ins and presentation):
- Hand-ins - during week 2 and 6 you are required to handin some material. You will get an email that you will reply to in order to hand in. The week 2 handin should be a pdf. The week 6 handin should be a web link pointing to a homepage for your project (containing report, presentation, run instruction, runnable code, and source code). A short description of what material the report and presentation should contain is available in the project description document.
- Review - after the final handin you will recieve the link to another groups project homepage. You will run their code and perform a code review looking for realtime problems.
- Final meeting - you will present your project, this will be followed by the reviewing group asking questions on your implementation. After all presentations are done, all groups will show their efforts in a demo session. Any remaining realtime problems (as determined by the teaching assistant) should be fixed and handed in one week later.