• If you want to get your assignment 4 and/or final test grades when I have them graded, you must send me an e-mail requesting that I send it to you (it is a violation of school policy for me to send them to you without a formal request).
• Assignment 2 is due Monday 2/13/06.
• Final will be 1:30 - 4:15PM Friday, May 12.
• Midterm will be Wednesday 3/08.

1. Shared memory programming with OpenMP,
2. Shared memory programming with pthreads,
3. Distributed memory programming with MPI.

• CS 5513 Computer Architecture
• CS 5633 Analysis of Algorithms

The only required book is:
• Introduction to Parallel Computing by Grama, Gupta, Karypis & Kumar. (second edition).

• Parallel Programming in OpenMP by Chandra, Dagum, et al.

• 40-60% From 2-3 major exams.
• 40-60% from various projects.
• 0-5% class participation/quizzes.

For a more complete description, consult the syllabus.

Students with disabilities:
If you have a physical, psychological, medical or learning disability that may impact on your ability to carry out assigned course work, I would urge that you contact University Disability Services (DS), Multidisciplinary Studies Building, Room 2.03.18, 210-458-4157 (Voice), 210-458-4981 (TTY), 210-458-4980 (Fax), homepage: http://www.utsa.edu/disability/. Please bring a letter to me from the DS indicating your need for academic accommodations within the first week of class. The syllabus and other class materials can be made available in alternative format upon request.

Academic Integrity:
Remember that the goal of programming or written assignments is to enhance your programming skills and understanding of the topics under discussion. Thus indulging in academic dishonesty results in poor understanding of the material as well as being unfair to other students. In case you have any questions about whether an act of collaboration may be construed as academic dishonesty, please clarify the issue with the instructor before you collaborate. Academic dishonesty can result in a grade of 'F'.

• It is understandable that discussing a problem with other people may lead to more insight into the issues involved. Thus discussing a problem in assignments/homeworks in a general way with other people is fine. However, discussing the solutions to the problem or showing/examining actual code is NOT acceptable.
• Every student must write his/her own code and homework. Showing your code or homework to members of other teams, giving it to them, or making it accessible to them (e.g., by making the files world-readable) is academic dishonesty.
• You are responsible for ensuring that your code/documentation/results are adequately protected and not accessible to other teams. Change permissions of your working directory to 0700 ('chmod 0700 <directory>).
• Consulting code from a textbook, or from the Internet, in order to understand specific aspects of your assignment is fine. However, copying entire code or large parts of such code will be considered academic dishonesty. If you borrow small parts of code from these sources, you must acknowledge this in your submission and additionally you must clearly understand and be able to explain how the code works. If you cannot explain your own code in detail, it will be graded as zero.