This page describes policies for this class, on a range of issues including
cheating, regrade requests, and recordings.
Cheating policy
Each exam and project must be the sole work of the student turning it in. Like the University as a whole and the ECE and CSD departments, we take cheating very seriously. See CMU's policies on academic integrity for more information on the University's policies, which apply fully to this course.The usual penalty for cheating in this class is to be removed from the course with a failing grade. The University also places a record of the incident in the student's permanent record.
No collaboration on exams is allowed. Unless otherwise notified, the following
guidelines dictate what non-exam collaboration is authorized and what is not.
What is Cheating?
- Sharing code or other electronic files: either by copying, retyping, looking at, or supplying a copy of a file from this or a previous semester. Also not allowed is verbal or other description of one person's code to another. Be sure to store your work in protected directories, and log off when you leave an open cluster, to prevent others from copying your work without your explicit assistance. Also, do NOT use any code repository without ensuring that it cannot be accessed by others... for example, using github in a public access mode invites others to copy your code and is not allowed.
- Sharing written assignments or exams: Looking at, copying, or supplying an assignment or exam.
- Using other's code. Using code from this or previous offerings of 746, from other courses at CMU or other institutions, or from any other non-746 source (e.g., software found on the Internet).
- Looking at other's code. Although mentioned above, it bears repeating. Looking at other students' code or allowing others to look at yours is cheating. Also, searching the web for other solutions to the projects (or code similar to a project) is cheating, as is looking at code found and looked at to understand how to complete the project. There is no notion of looking "too much," since no looking is allowed at all.
What is NOT Cheating?
- Clarifying ambiguities or vague points in class handouts or readings.
- Helping others use the computer systems, networks, compilers, debuggers, profilers, or other system facilities.
- Helping others with high-level design issues only. Algorithm implementations and other such details are not "high-level design issues".
- Helping others with high-level (not code-based) debugging.
Be sure to store your work in protected directories, and log off when you leave an open cluster to prevent others from copying your work without your explicit assistance. Do not use publicly accessible code repositories or revision control systems; make sure that only you can access your code. If you are going to host your code on Github, make sure you use a private repository, and be warned that two years after your student status expires, Github will be converting your private repositories to public, so be sure to remove your code. Academic integrity policies extend beyond the duration of your studies.
We understand that the web is a popular tool for everyone (including students)
seeking to better understand and solve problems. Because the line between
cheating and such explorations has been reached by some in the past, we ask all
students to explicitly list websites on which they relied in developing their
solutions. And, we reiterate for enphasis: looking at or relying on
implementations found on the web is considered cheating.
Mobile devices and other distractions
Research on learning shows that unexpected noises and movement automatically
divert and capture people's attention, which means you are affecting everyone's
learning experience if your cell phone, pager, laptop, etc. makes noise or is
visually distracting during class. For this reason, we allow you to take notes
on your laptop, but insist that you turn the sound off so that you do not
disrupt other students' learning. If you are doing anything other than taking
notes on your laptop, please sit in the back row so that other students are not
distracted by your screen.
No recording of class meetings
No student may record or tape any classroom activity without the express written
consent of all instructor(s). If a student believes that he/she is disabled and
needs to record or tape classroom activities, he/she should contact the Office
of Equal Opportunity Services, Disability Resources to request an appropriate
accommodation.
Re-grading policy for exams and assignments
We will make the utmost effort to be fair and consistent in our grading. But, we are human. If you believe that you did not receive appropriate credit for an exam or assignment, you may request a re-grade as follows:
- Submit your request in writing within seven calendar days of when the exam or assignment is returned, explaining in detail why you think that there was a mistake in the grading. Please note that verbal requests will not be processed; requests must be in writing.
- Requests should be submitted to 719-staff@mailman.srv.cs.cmu.edu, whether for an assignment or for an exam. In the case of exams, the exam in question should be hand-delivered to the ECE Coursehub (HH 1112) together with a printed copy of the email request.
- When you submit a request for a re-grade, the entire assignment or exam may be re-graded (not just the parts that you specify). Your grade may go up or down (or stay the same) as a result of the re-grade request. Your request will be processed off-line, and we will respond to your request as quickly as possible (may be delayed, but done before final grades are assigned). This re-grade policy is designed to correct legitimate mistakes in grading, while discouraging frivolous re-grade requests and maximizing our ability to be fair and consistent across the entire class).
Late policy
No late assignments will be accepted, beyond explicitly announced deadline
extensions announced to the entire class. If extreme extenuating circumstances
make it impossible for you to submit your assignment on time, e-mail one of the
course instructors.
Pre-requisites
This course will require solid understanding of computer organization, basic
operating systems, and basic communication. Therefore, the minimum pre-requisite
is a 'B' or better in 15-213 (or 18-213 or 15-513 of 18-600, which are the same
class) or an 'A-' or better in 15-619. Exceptions are rare and only by
permission of the instructor. Our experience indicates that students without the
substantial hands-on systems experience provided by this prereq (or some
equivalently extensive experience) struggle significantly.
Take care of yourself
Do your best to maintain a healthy lifestyle this semester by eating well,
exercising, avoiding drugs and alcohol, getting enough sleep and taking some
time to relax. This will help you achieve your goals and cope with stress.
All of us benefit from support during times of struggle. You are not alone.
There are many helpful resources available on campus and an important part of
the college experience is learning how to ask for help. Asking for support
sooner rather than later is often helpful.
If you or anyone you know experiences any academic stress, difficult life
events, or feelings like anxiety or depression, we strongly encourage you to
seek support. Counseling and Psychological Services (CaPS) is here to help: call
412-268-2922 and visit their website at CaPS website. Consider reaching out to a
friend, faculty or family member you trust for help getting connected to the
support that can help.
Final note
* Everything here is subject to change.Last updated: 2018-03-25 17:44:45 -0400