 |
Welcome to EE202A, a course on
Embedded and Real-time Systems in the EE Embedded Computing
Systems field.
|
2001/12/6 |
|
Take-home final exam is available
here. It is due by Monday 5PM. |
|
2001/11/1 |
|
Homework # 2 is our - see
Homeworks page. Due on Thursday,
November 15 @ 5PM. |
|
2001/10/30 |
|
Paper Review # 3 is out - see
Paper Reviews page. Due on Tuesday,
November 13 @ 10AM. |
|
2001/10/09: |
|
Initial list of the first 8 of 16 Student
Presentations is available here. |
|
2001/10/09: |
|
Paper Review # 2 is out - see
Paper Reviews page. Due on Monday,
October 15 @ 10AM. |
|
2001/09/25: |
|
If you are taking this course, please subscribe to the class mailing
list
ee202a@ee.ucla.edu by
filling this questionnaire
(preferred), or sending an email to me at
mbs@ee.ucla.edu. |
This course web site is designed to complement the course lectures. Resources available
here include lecture viewgraphs, handouts, solutions, and pointers to relevant resources on the web. Some material may have access
restricted to UCLA students.
EE202A is a part of the
Embedded Computing Systems graduate major field
program in the EE Department. This flyer gives
an overview of what will be covered in the course this year.
Course Staff Information
Please visit this web site frequently during the course for various announcements, and
to download lecture viewgraphs (placed by the morning of the lecture) and to get
information on papers assigned for reading. Also, explore the various links on the button
panel to the left of this page for useful information relating to the course.
Time & Place
| Lectures |
TuTh 6:00PM-7:50AM,
5436 BH |
| Office Hours |
Th 3:00PM-5:00PM, 7702-B Boelter Hall |
Prerequisites
 | No prerequisite graduate courses
|
| Knowledge
of the following at advanced undergraduate level
 | digital
hardware design |
| computer
architecture |
| system
software |
| algorithms
and data structures |
|
| Following
will be useful too…
| digital
signal processing |
| VLSI
CAD tools |
| compilers
and programming languages |
|
| Basically, I will assume that you know EVERYTHING
that a student in UCLA's EE/CE B.S. program is supposed to know. |
Grading
|
One examination: 20%
|
9th or 10th week … most likely a take-home during
the weekend between Weeks 9 & 10 |
|
|
Several home works: 17.5% total
|
analysis, simulation, programming, library/web
research |
|
|
Several paper reviews: 5%
|
Typically due Monday morning of the following
week |
|
Critique … not summarize |
|
Around 0.5 page / paper |
|
|
Presentation: 12.5%
|
20-25 min paper review or area survey
(topic/paper specified by me) |
|
groups of two students (form them by end of W2,
otherwise I’d assign) |
|
slides prepared jointly, speaker selected by me
at the presentation time |
|
this material is fair game for homework and
exams! |
|
|
One project: 25% results, 10% report, 5%
presentation = 40% total
|
software/hardware design, tools, analysis,
simulation |
|
groups of up to two students (need not be the
same as for presentation) |
|
30 minute presentation during finals week |
|
like a conference paper + talk |
|
|
Class participation: 5%
|
E.g. questions that you ask during lectures and
student presentations |
|
E.g. how much you interact
with me regarding the project |
|
Reader & Textbooks
This being a course in a rapidly evolving area, the lectures will be
substantially based on papers from literature. An evolving web based
course reader will provide links to on-line papers, and identify their availability as
INSPEC images in Melvyl. There is no paper reader. I will handout those papers that are
unavailable on-line. It is your responsibility to print and read the on-line papers
before the lectures.
Lecture material will also be drawn from various books
and other resources. See the
resources page for names of
some books. There is no particular need to buy these
books, although they are good books to have if you are doing research in the area.
On-line submission
In this course I rely solely on on-line submission of
home works, paper reviews, and even the examination. At the same time, I do
not want my mailbox to be bombarded my huge mail attachments. So, what you
will need to submit is a URL by the deadline. Now, to avoid the problem of
you sending me a URL but changing the underlying contents after the
deadline, I would run a script that would automatically fetch the files soon
after the deadline. For this to work, I need to know the URL in advance.
So, this is how the on-line submission will work.
- At the beginning of the course, you need to give me
a top-level URL for all your course submissions, e.g.
http://www.ee.ucla.edu/~student/ee202a.
- Your submissions for a specific assignment should
be a single zip (preferred) or tgz (tar + gnu zip) file, say hw1.zip or
hw1.tgz, inside which can be the multiple files for, say, the different
problems. The files inside the zip or tgz archives could be in any of the
following formats: html, pdf, ps, word, framemaker, jpeg, GIF.
- I would specify the prefix name that you should use
for the zip/tgz file, e.g. hw1.
Example: I might say that for homework 1, the root
name for the submission file is hw1. Moreover, let us say that the top-level
URL you have given me is U. Then my script will simply attempt to fetch
U/hw1.zip and U/hw1.tgz. I would use the program wget that is available
under Unix (Linux). So, in essence, my script would do 'wget U/hw1.zip' and
'wget U/hw1.tgz'.
YOU ARE RESPONSIBLE FOR MAKING SURE THAT YOUR
SUBMISSION IS AT THE RIGHT URL.
Late submissions
Unless I give an extension, late submissions for any
assignment would carry a 50% (of whatever you score) penalty after the
scheduled deadline, and a 100% penalty after 24 hours past the deadline.
Policy on Cheating and Plagiarism
|
My apologies if you are one of the vast majority of
students who don’t resort to academic dishonesty
|
but unfortunate incidents in my previous grad and
undergrad courses |
|
|
What is cheating & plagiarism?
|
Acting dishonestly, practicing fraud |
|
Stealing or using (without my permission) other
people’s writings or ideas |
|
E.g. from other students, other sources such as web
sites, solutions from previous offerings of this course etc. |
|
Note that it doesn’t have to be literal copying –
stealing ideas but presenting in a different style is still cheating and
plagiarism. |
|
|
You are also guilty if you aid in cheating &
plagiarism |
|
My policy: zero tolerance
|
HWs, paper presentation: zero score + one level
reduction in course grade |
|
Exam, project: “F” grade for the course + report to
Dean |
|
More than 1 incident: : “F” grade for the course +
report to Dean |
|
|
Moreover, please remember that you may have to face
me in other exams (e.g. M.S. comprehensive, Ph.D. prelims, Ph.D.
qualifiers) and professionally! |
|
|
