##Lab Assignments For policies related to labs, please see the syllabus
###Lab Schedule | Lab | Topic | Other Links | Due Date | Submit | | :—————–: | :——————————- | :————————-: | :—————-: | :———-: | | Lab 01 | Setting up your enviornment | | T/W. Sep. 3/4, 2019 @ 11:59PM (PST) | Vocareum |
Remaining labs will be added to the Lab resource folder with due dates specified in the lab document itself
Homeworks
Homeworks are not collected and for your own practice. For information related to homeworks, please see the syllabus
| HW | Topic | Notes | Due Date | Submit |
|---|---|---|---|---|
| HW 01 | Python and git | Submit all answers as 1 PDF | Fri. 9/13/19 | Vocareum |
Grade Disputes
We will work hard to post LAB scores and feedback within 1 week of the lab’s due date. Exams will typically be graded within at most a few days of the exam date.
Any disputes with posted grades must be raised within 7 days of the score posting. (If your schedule does not permit a detailed request within 7 days, you should register a short note that you plan to dispute, and then submit the dispute when you are ready.) Notice that any regrade request will result in us trying to give the fairest possible grade to you, which could be higher or lower than the one you received originally.
To raise an issue with your exam score, you should come to the office hours of the professor teaching your section. If you cannot make posted office hours, schedule one by e-mail. The TAs will not be allowed to grant regrades on exams.
Academic Integrity
The official language on academic integrity is on the syllabus. Here is a little more clarification.
Practically speaking, it is important to be able to seek out helpful information and collaborate, yet it is clearly wrong to pass off work done (even just in part) by others as your own. Navigating these two principles can be tricky. However, notice that only you are responsible for understanding what is allowed, and what is not. Cheating can and does occur which is neither malicious nor intentional. Knowledge is power!
When in doubt whether some behavior you are considering is appropriate, feel free to consult with us (course staff) before engaging in it. As a general guideline, imagine that your professor is looking over your shoulder, but can’t read your mind. Would it look to him like you’re legitimately seeking to understand things, or trying to get a better grade than your own work warrants? That should guide your behavior. Here is a list of some particularly common things, with an explanation:
- Asking other students for hints or discussing high-level ideas. This is clearly OK.
- Having other students look at your code and help you discover mistakes. This is dangerous: if the other student intentionally or accidentally copies from you, there would be negative consequences for both of you.
- Asking course staff (instructor, TAs, CPs) for help, ideas, having them look through code, etc. Clearly no problem; if you are asking for too much help, we will simply not provide that much.
- Copying code or test cases from other students, even if you subsequently edit, improve or change them. Clearly not OK, even if you intend to understand the code or inputs before submitting them as your own. This is most definitely plagiarism! We will run the MOSS software on all submissions in the class to detect instances of copying.
- Sharing your code for other students to “reference” or looking at another student’s code to “get an idea of what is needed”. This is a violation. Not OK. Remember: friends that pressure you for unreasonable help are not really friends. There are plenty of course staff and instructors who are here to help!
- Looking up concepts, syntax, and basic instructions on how to deal with the topics online. This is clearly OK, as you are learning.
- Looking online for solutions or code to reference. This is a violation. Not OK.
- Posting in online forums asking people to solve homework questions (or parts thereof) for you. Clearly cheating - Duh!
