| CS21003 Algorithms I
CS29003 Algorithms Laboratory
|Autumn 2012, L-T-P: 3-1-0
Points to Consider
All submissions must be made in the submission server. Any e-mail submission to the teachers and/or the TAs will be ignored. If submission fails because of a server problem, please let me know immediately. However, failure because of expiry of deadline cannot be entertained. It is your duty to submit before the deadline. Note that you may submit as many times as you want. Only the last submission is retained. You should take into account the fact that the clock in the submission server may be slightly erroneous, and act accordingly. If the error is more than ten minutes, let me know. If submission fails because of network problems in your hostel, I am not responsible for that.
Do not forget to give attendance in the submission server. Attendance can be given only between 1:30pm and 4:30pm on Wednesdays.
These assignments may involve designing the algorithms yourself. This lab is not about coding well-specified algorithms. Efficient codes would deserve more credit than inefficient codes. Please handle your C/C++ syntax or runtime errors (including segmentation faults) yourself. This lab is not meant for teaching C (or any other programming language). If you are not fully comfortable with C syntax, look at this site, or bring with you any textbook on C/C++. Note that we accept only C and C++ programs.
We want each line of your code be written by you only. Any case of copying among students will call for no credit. We will not make any distinction between who copied a program and from whom it is copied. Partial copying is also treated the same as copying entire programs. We will not entertain claims like stealing of codes. It is entirely your responsibility to protect your codes from others.
If you copy parts of your code from the Internet, you must mention that clearly in your code. Failure to do that will lead to your entire submission being invalid. Of course, you will not get any credit for the parts you copied, but you get due credits for the parts you coded yourself.
Repeated instances of copying attached to the same name(s) would call for severe punishments including deregistration.
Comments and Indentation
We want your programs to follow a proper indentation style. Also, we encourage you to add comments to your code. In order to know our rcommended indentation and commenting styles, please visit this site.