Location:
Environmental Science and Engineering (L1205)
Time: Tu/Th 3:05 – 4:25pm
Instructor: Calton Pu (calton@cc.gatech.edu)
Office: 3334 KACB
Office hours: Mon/Thu 9-10am.
TA: Ling Liu (liuling@cc)
Office:
Office hrs.: Fri 10am-12noon.
TA: Qingyang Wang (bbqywang@gatech.edu)
Office: 3201 KACB
Office hrs.: TBD.
Newsgroup: git.cc.class.cs6235 (Server name: news.gatech.edu). Check this regularly since it is the main place that the announcements will go. Please also post common questions to this place so that other students can benefit from the answer.
This is a preliminary page. For detailed information on the last offering,
see the Fall 2006 course.
Project Presentation Schedule
CS4220 (Embedded Systems) and CS6235 (Real-Time Systems) are co-listed this term. This course covers the principles of real-time and embedded systems inherent in many hardware platforms and applications being developed for engineering and science as well as for ubiquitous systems, including robotics and manufacturing, interactive and multimedia, immersive and omnipresent applications. As part of this course, students will learn about real-time and quality of service system principles, understand real-time operating systems and the resource management and quality of service issues that arise, and construct sample applications on representative platforms. Platforms range from handheld and mobile computers to media and real-time server systems. Platforms may also include specialized systems used in application-specific contexts, such as autonomous robotics, smart sensors, and others.
All students must submit written abstracts for at least 75% of the papers studied in class, before each paper's presentation. These abstracts should explain the main points of the paper. Abstracts should not be simple cut and paste from the papers -- they should display some understanding of the material and criticism of the work (both pros and cons). Only one abstract is due for each class, and unless indicated, students may choose which paper to summarize. Each abstract will be graded by 0 (not submitted), 1 (average), and 2 (good). Abstracts must be emailed to the TA by class time. The title of email should be a form of [CS6235] (your last name) (the last name of the first author of the paper you have chosen) or similar (for example: Jason Parekh summarizing Weiser's paper would be: "[CS6235] Parekh Weiser")
NOTES:
Grading Policy
Sample abstracts from another
class
(use user_id cs4803 and password
carmen)
Sample Standard
Project Reports
· Benchmarking Real-Time Linux Alternatives
· A Performance Study of Real-Time Operation System using RTLinux
Class projects will use the Unix Solaris and Linux operating systems, both of which offer some facilities for construction and control of real-time systems. Class members have access to selected real-time devices and ubiquitous systems, including smart sensors (skiff boards running Linux), possibly including Lego robots (if there is class interest), including handheld devices and portable PCs (Linux-based PCs and PalmOS/Linux-based handhelds and/or wearables), including camera and other video-based sensors on PCs running Windows or Linux, and they can have access to the commercially most prevalent real-time operating system kernel, called Vxworks, running on Pentium and Sparc machines.
Sample pplications available to students include multimedia codes (video and audio), distributed games, sensor processing codes, image processing codes, location identification (if there is class interest) and possibly, distributed virtual environments (again, given class interest).
Qingyang The deadline is the Friday of the last week of classes (12/7).
The deliverables of the project consists of all material on the project for
which you want to get credit. This typically consists of code written by the
team, presentation materials, a final report, and supporting material. The
supporting material may contain very useful information such as design documents
(for well organized teams) and user instructions (for polished projects) to run
a demo. In addition, if you have used some unusual platform, supporting material
should include some information that helps me understand the project better, for
instance, a description of a custom board or a specific (not generally
available) virtual machine monitor. The report is the "root" of the deliverables
tree. Instead of reading through the entire code, for instance, I will read the
report first to understand what you are doing, and then browse through the
materials to appreciate your work. The supporting material may be separate files
or appendices to the report. The deliverables may be sent through physical media
(e.g., CD or DVD) or a download. If the files are small enough, they can be sent
as a zipped email attachment (limit of 2MB).
Weeks 1 - 2: Basic Concepts and Research Techniques
Weeks 3 - 4: QoS and Feedback
Week 5: Scheduling Algorithms
Week 6: Specialization
Week 9: QoS semantics
For future papers, please check T-Square. This web page will be updated occasionally.
This class is taught every year, by combining the 4220 and 6235 course numbers. It is suitable for both CoC and non-CoC majors, in part because grades are based on project work, which is defined jointly by the instructor and students. The intent is to ensure some basic skills on the part of each student and also to match both student interests/background and course objectives.
Each student (or team) will present one course topic in class and also complete the class projects. Maximum team size is 3 students. In addition, as part of class homework, all students must submit written commentaries for at least 75% of the papers studied in class, before each paper's presentation. These commentaries should consists of three paragraphs (not too long, since quality is more important than quantity). The first paragraph should summarize the main ideas and the strong points of the paper. The second paragraph should outline the limitations or weaknesses of the paper. The third paragraph contains your own comments. Each commentary will be graded by 0 (not submitted), 1 (average), and 2 (good).
Real-time Systems Reading List
Boston
University: CS835 Reading List
Computer Science Research Paper Search Engine
Real-Time Resources
Ubiquitous
Computing Links
Postscript(R) to PDF
Converter