Alan Kaminsky Department of Computer Science Rochester Institute of Technology 4486 + 2220 = 6706
Home Page
Parallel Computing II 4005-736-70 Spring Quarter 2012
Course Page

4005-736-70 Parallel Computing II
Course Grading and Policies

Prof. Alan Kaminsky -- Spring Quarter 2012
Rochester Institute of Technology -- Department of Computer Science

Grading
Grade Notification
Required Reading
Extensions
Email Rules
Plagiarism


Grading

I will not be running this as a traditional classroom course with lectures, homework, exams, etc. Instead, I will be running this as an individualized research course. Each student will undertake a research investigation, the outcome of which will be a paper ready to be published in a research conference and a conference presentation to go with the paper. During class sessions, as well as outside of class as necessary, I will be coaching you on your literature searching, software design and measurement, research paper writing, and presentation delivery. Your final course grade will be based on my assessment of your research investigation progress, paper, and presentation according to the standards of scientific research conferences. For detailed information about the research investigation requirements and grading, see Research Investigation.

I may encourage you to submit your papers for publication in appropriate conferences. However, acceptance of your paper for publication is not a requirement for this course.

The specific graded items are:

5%   Initial web site
40%   Weekly status (8 weeks × 5%)
10%   Draft report
15%   Final report
15%   Source code archive
15%   Final presentation

I will not hand out letter grades during the course, just points. Your final grade will be determined by the total points you earn, weighted as shown above, and converted to a letter using this scale:

92%  ≤  A  ≤  100%
84%  ≤  B  <  92%
76%  ≤  C  <  84%
68%  ≤  D  <  76%
0%  ≤  F  <  68%

For the actual formulas used to calculate grades, see the Grade Calculator.

Frequently Asked Questions

  1. Q: Will you curve the grading scales based on class performance?
    A: No.
  2. Q: If my final score comes in a fraction of a point below the cutoff, will you give me the higher grade?
    A: No.
  3. Q: Can I do extra work to increase my grade?
    A: No.
  4. Q: I will lose my scholarship if I don't get a grade of ___. Won't you give me a grade of ___?
    A: No.
  5. Q: I will lose my visa and have to leave the country if I don't get a grade of ___. Won't you give me a grade of ___?
    A: No.
  6. Q: I will go on academic probation or suspension if I don't get a grade of ___. Won't you give me a grade of ___?
    A: No.
  7. Q: I will not be able to graduate when I planned if I don't get a grade of ___. Won't you give me a grade of ___?
    A: No.
  8. Q: My GPA will be too low for me to find a good co-op if I don't get a grade of ___. Won't you give me a grade of ___?
    A: No.


Grade Notification

I will record your grades for the programming project, as well as your final letter grade, in a grade file. Each student will have his or her own grade file. Each grade file will be encrypted with a different secret key for each student. The encrypted grade files will be posted on the course web site. Since no one can decrypt the grade file without the secret key, your personal grade information remains confidential despite being posted on the web site.

To decrypt your grade file, you will have to obtain the secret key from me, in person. Come to my office, show me your student ID, and I will give you your secret key. It is your responsibility to safeguard your secret key. If anyone else discovers what your secret key is, they will be able to decrypt and examine your grade file. Treat your secret key as you would your student ID, driver's license, or credit card. If you lose your secret key or suspect someone else has discovered it, see me, in person, to get a new secret key.

When I have finished grading each assignment, I will post an announcement on the What's New page that the grades are available.

For further information, see Encrypted Grades.

Discussing your grades: If you have questions about or want to discuss your grades, you must come see me in person. Either visit me during office hours or make an appointment. I will not answer questions about or discuss your grades via email.


Required Reading

You are responsible for knowing the material in Parts I, II, and III of the Building Parallel Programs textbook. I covered this material in the Parallel Computing I course. If you did not take Parallel Computing I with me, you will need to pick up this material on your own.

You are responsible for learning the material in Part IV of the Building Parallel Programs textbook. I will be covering this material in class lectures. The material in Part V is not required but may prove useful in your research investigation.

To help you learn the material, solutions to Selected Exercises are posted on the course web site. I strongly recommend you do the problems before looking at the solutions, then check your work afterwards.

Accessing the solutions on the course web site requires authentication with a specific username and password. (This is not the same as your Computer Science Department account, and this is not the same as the secret key for decrypting your grade file.) The username and password will be announced in class and will also be listed in your grade file. Please observe the following restrictions:

If these restrictions are not obeyed, I will not be able to continue posting solutions.


Extensions

The rules for extensions are:

  1. You may request an extension for the following assignments: draft report, final report, and source code archive.

  2. You may request only one extension for each assignment.

  3. The first date on which you may request an extension is three days before the deadline date. You may not request an extension before that.

  4. The last date on which you may request an extension is the deadline date. You may not request an extension after that.

  5. The length of the extension depends solely on when you request the extension, as follows:
     
     If you request an extension:   You will receive an extension of: 
     3 days before the deadline date  3 days 
     2 days before the deadline date  2 days 
     1 day before the deadline date  1 day 
     On the deadline date  1 day 

  6. You do not have to give a reason for requesting an extension.

  7. To request an extension, send me an email message at ark­@­cs.rit.edu. The date on which your email message arrives in my inbox determines the length of the extension as stated in the above table. I will send you an acknowledgment in a reply email message.
     
    When asking for an extension, I would appreciate some basic courtesy. Too many students send me a rude message like "I need an extension." The polite way to ask for an extension is, "May I please have an extension for Project 1?"

The intent of this policy is not to give everyone an automatic 3-day extension for every assignment. The intent of this policy is to accommodate students who plan and work ahead on the assignments but experience an unforeseen last-minute difficulty, and to penalize students who do not plan and work ahead. If you put off working on an assignment and get sick or suffer a computer breakdown at the last minute, I am not going to give you more time than stated above. You should have been working ahead so you would have been finished before the last minute.

If you receive an extension for an assignment and the extended deadline falls after the last day of classes, then at my discretion I may assign you a grade of Incomplete (I) for the course. The Incomplete grade will be changed after you have submitted the assignment and I have evaluated it.


Email Rules

My email address is ark­@­cs.rit.edu. To deter spambots, the email address is obfuscated. If you copy and paste my email address from this web site, it will not work. If you type in my email address by hand, it will work.

I apply spam filtering on incoming email. To get your email past my spam filters and into my inbox:

I reply in a timely manner to all emails that get past my spam filters and into my inbox. Emails blocked by my spam filters go into a separate spam folder. I do not reply in a timely manner to emails in my spam folder.

It is your responsibility to format your emails so that they get past my spam filters. This includes assignment submissions and extension requests as well as general questions. If I have not responded to your email within one business day (i.e. not counting weekends), contact me again.

For further information, see "Contacting Me."


Plagiarism

You may use any resources you wish to do the assignments, including resources discussed in class and resources you find on your own. You may discuss the assignments at a general level with others in the class. However, each assignment you turn in must be entirely your own work. You are not allowed to collaborate with anyone else on any assignment. You are not allowed to use any current student's work, any past student's work, or any other person's work in any way as part of your assignment.

I will not tolerate plagiarism. If in my judgment an assignment is not entirely your own work, you will receive, as a minimum, a grade of zero for the assignment. Plagiarism incidents will result in disciplinary action in accordance with Computer Science Department policy and RIT policy. I expect you to read and abide by the following policies:

These are some examples of plagiarism. These are not the only examples of plagiarism.

  1. Copying a piece of code you found on the Internet into your assignment.

  2. Copying a piece of code you found on the Internet into your assignment, and including a citation to the original source.

  3. Copying a piece of code you found on the Internet into your assignment, with modifications.

  4. Copying a piece of code you found on the Internet into your assignment, with modifications, and including a citation to the original source.

  5. Copying a piece of code written by someone else into your assignment.

  6. Copying a piece of code written by someone else into your assignment, and including a citation to the original source.

  7. Copying a piece of code written by someone else into your assignment, with modifications.

  8. Copying a piece of code written by someone else into your assignment, with modifications, and including a citation to the original source.

  9. A sentence, paragraph, or section of text that is identical to or almost the same as text written somewhere else.

  10. A sentence, paragraph, or section of text that is identical to or almost the same as text written somewhere else, with quotation marks.

  11. A sentence, paragraph, or section of text that is identical to or almost the same as text written somewhere else, with or without quotation marks, and with a citation to the original source. (Yes, I do consider this plagiarism. It also indicates that you do not have a deep understanding of the material, since you are unable to express it in your own words.)

  12. A figure or diagram written somewhere else without a citation to the original source. (It's okay to quote figures and diagrams, if cited. It's not okay to quote text.)

There are only two exceptions to the prohibition on plagiarism:

  1. You may reuse without modification a source file from the Parallel Java Library or the Computer Science Course Library.
     
  2. You may take a source file from the Parallel Java Library or the Computer Science Course Library and add your own modifications, provided you state that you have done so and give credit to the original author.

Parallel Computing II 4005-736-70 Spring Quarter 2012
Course Page
Alan Kaminsky Department of Computer Science Rochester Institute of Technology 4486 + 2220 = 6706
Home Page
Copyright © 2012 Alan Kaminsky. All rights reserved. Last updated 06-Mar-2012. Please send comments to ark­@­cs.rit.edu.