AY2017/8 Semester 2
Continual Assessment - Labs

Preamble

Labs form the practical element of CS1010. We attach great importance to developing good programming skills in you, and hence we need your cooperation and committment to view lab assignments seriously.

We will be closely monitoring your progress, and your discussion leader is entasked to help you. They will run through your graded lab assignments with you, give comments on your programs, and point out areas for improvement.

You are reminded that all submissions must be from your own effort. This is the only way real learning can take place. (Please see About Plagiarism below.)

For take-home lab assignments, there is no fixed lab session. You are to do your lab assignments and your own practice on your own, either at home or in school. Locations of the programming labs are given in the following floor plans:

• All
• COM1 basement (where it houses PL1 - PL5.)
• COM1 level 1 (where it houses PL6.)

You may use the computers as long as there are no classes going on. For the locations of all teaching labs and their accessibility and opening hours, please refer to Teaching Laboratories.

The card readers at the labs are usually activated from week 3 onwards. If your matriculation card has problem with accessing the labs, please send an email with your matriculation number to smartcardop@comp.nus.edu.sg to inform them of your problem.

Please also visit Resources - Online page for links to other resources, such as C resources, style guides, information for Mac users, vim help sheet, etc.

Intro Workshop

• Intro Workshop: Getting Started with UNIX and CodeCrunch
  A posting will be made on IVLE forum in week 1 to instruct you how to sign up for this workshop.
• UNIX Workshop 2014 slides (Conducted by FOW on 5 August 2013)
• Videos on vim:
  • Lesson 1
  • Lesson 2
  • Lesson 3
  • Lesson 4

CodeCrunch

You will use a system called CodeCrunch to submit your lab assignments. We will introduce CodeCrunch to you at the Intro Workshop in week 2. (You will be granted access to CodeCrunch later, so for the moment you are unable to access it.)

• CodeCrunch website
• Introduction to CodeCrunch (Powerpoint)
  
  

About Plagiarism

Plagiarism, in general, is an act of academic dishonesty. In the context of a programming module, it refers, but is not limited, to cases of a student copying others' work and passing it off as his own, or a student who allows his own work to be copied by another.

We would thus advise you against collaborating on lab questions, or discussing the solution among yourselves or openly on the IVLE forum. However, you may raise your doubt about the task statements on the IVLE forum.

We encourage discussion among the students, but you need to draw a line between discussion and copying. Two students who get together to discuss a problem and derive the algorithm, and then leave to write the code on their own is fine. But most often than not, during the discussion the students tend to produce the code, a partial code, or a skeleton of the code together, and their end products will look quite identical. You need to be aware of this and to avoid getting into such situation.

For take-home lab assignments, we understand that sometimes you may discuss the problems with your friends as part of your learning experience. However, try to refrain from copying the programs from others without putting in your own real effort. If we encounter such cases, we will not award the attempt-mark to the students.

For more details on plagiarism, please refer to the page on NUS Plagiarism Notice.