Location=
: CCB
17
Time: Tu/Th 12:05 – 1:25pm
Instructor: Calton Pu (calton@cc=
.gatech.edu)
Office: 3334 KACB
Office hrs.: by appointment.
TA: Younggyun Koh (young@cc)
Office:
Office hrs.: HOURS or by appointment.
TA: TBD
This is a preliminary page. For detailed
information on the last offering, see the
CS4220 (Embedded Systems) and CS6235 (Real-Time Systems) are co-listed t= his term. This course covers the principles of real-time and embedded sys= tems inherent in many hardware platforms and applications being developed for engineering and science as well as for ubiquitous systems, including roboti= cs and manufacturing, interactive and multimedia, immersive and omnipresent applications. As part of this course, students will learn about real-time a= nd 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. Platfo= rms 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 must summarize the main points of the paper. Abstracts should not be simple cut = and paste from the papers -- they should display some understanding of the mate= rial 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 summar= ize. Each abstract will be graded by 0 (not submitted), 1 (average), and 2 (good). Abstracts should be submitted through T-Square.
NOTES:
The paper links are hosted on T-Square.
Grading
Policy
Sample abstracts from
another class
(use user_id cs4803 and password carmen)
Sample S=
tandard
Project Reports
&middo= t; Benchmarking Real-Time Linux Alternatives
Class projects will use the Unix Solaris and Linux ope= rating 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 hand= held devices and portable PCs (Linux-based PCs and PalmOS/Linux-based handhelds and/or wearables), including camera a= nd 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 applications available to students include multimedia codes (video and audio), distributed games, sensor processing codes, image processing co= des, location identification (if there is class interest) and possibly, distribu= ted virtual environments (again, given class interest).
The deadline is the Friday of the last week of classes (12/4).
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 platfor=
m,
supporting material should include some information that helps me understand
the project better, for instance, a description of a custom board or a spec=
ific
(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. T=
he
supporting material may be separate files or appendices to the report. The
deliverables should be uploaded to T-Square, or they may be sent through
physical media (e.g., CD or DVD). 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
The plan below has not been updated for Fall 2009.
-------------------------------------------------------------------<= /p>
Weeks 3 - 5: QoS and Feedback
Week 6: Scheduling Algorithms
Week 7: Specialization
Week 8:
Week 9:
Week 10: Security
Week 11:
Week 12:
Week 13:
This class is taught every year, by combining the 4= 220 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. T= he 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 topi= c 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 consist= s of three paragraphs (not too long, since quality is more important than quantity). The first paragraph should summarize the main ideas and the stro= ng points of the paper. The second paragraph should outline the limitati= ons 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
B=
oston
University: CS835 Reading List
=
Computer
Science Research Paper Search Engine
Real-Time Resources
Ubiquit=
ous
Computing Links
Postscript(R) to PDF
Converter