Late HWs: The HW due date will be posted on every HW and will be followed. In no circumstances will an extension be given. Late  HWs are not allowed and strongly discouraged due to the fast pace of the course. The HWs have to be submitted BEFORE class via sakai on the due date. Any HW submitted after the class is over, or during the class will be considered late and will receive an automatic zero.

However, we will give you 2 grace class-days throughout the whole semester. By class days it is meant the days on which we have lectures. So, if a HW is due on Wednesday and you have not used any of your grace class-days then you can submit it till the following Monday.

Use your grace class-days for whatever reason you like. There will be no penalty for submitting late till the time your 2 grace class-days are valid. After that if you submit late you will get zero. Remember, not to consume them in the initial assignments itself and have nothing left for you towards the end of the semester when you will be overburdened with exams and submissions from other courses. 

For example, if you submit your first assignment 1 class-day late, then you will only have 1 grace days left for the whole of the remaining assignments. So, use them judiciously!

Graders will test your code with their programs. Mere passing of all the test cases does not ensure full credit. Even if not stated there will be time and space constraints on the implementation of the algorithm. This forms a major part of your assignment grade. Your program should run within acceptable space and time constraints. Often times we will specify these constraints in the HW specs in which case they should be exactly followed.

Note that the TAs will compile and test your program on cise storm machine. So, before submitting you should have compiled and run your program on storm. You need to have a cise account to be able to log into storm.cise.ufl.edu.  

Uncompiled programs or programs with compilation errors or maybe your program compiled correctly on your machine but not on the CISE storm machine, will straight away get zero points with no consideration afterwards. Uncompiled programs waste a lot of time of the TAs and are discouraged.

After each assignment is graded, the policy and the test cases will be available online. You can download these, run them on your code that you submitted and report discrepancies if found.

If the problem specifies the name that you should give your class, you must give your class that name, or it will cost you up to 30% of credit for that question.

Often, you will be asked to extend a class and include a new member function. The signature of the function must be the same as that specified by the problem. The return type, function name and the parameters passed should be the same as that specified in the specs. Violation can cost 100% of the assignment grade.

Each of the following is required, and if not satisfied, will result in a zero for the code portion of an assignment:

1. Makefile, .cpp file, .h file, any other file required in the hw. The .cpp file (say, ProgramName.cpp) must compile successfully. You are required to submit a makefile with every HW. You should not include more than one makefile for a particular HW. The one makefile that you submit should be able to compile all the programs in the HW.

2. The submitted file must be properly tarred. Improper tarring of files again can cost 100% for that assignment. The simplest syntax of the tar command is as follows.

   To create a tar file:

      tar cvf (tar file name) (file 1) (file 2) (file 3)...

   To extract the contents of a tar file:

      tar xvf (tar file name)

   For example, if you have ProgramName.cpp and readme.txt to submit for an assignment, use the following command to tar them properly into a file called MyAssignment.tar:

      tar cvf MyAssigment.tar ProgramName.cpp readme.txt

   Warning: Some platforms have the capability to add other files to a tar archive. Do not use this capability to make your tar files. To be sure, use the 'tar' command described above.

   Note: You can verify that your submission was successful by downloading your submission from Sakai and successfully untarring it.

3. For most cases we will do selective grading. This means that we may not grade all questions for a particular HW. But you will be required to submit solutions to all the questions unless stated otherwise. Whatever question we will choose to grade will be the same for all the students. The HW grade will in most cases rely on only the questions that we choose to grade. We will not declare before the HW due date which questions we have decided to grade. We will also not provide any solutions to the HW. The solutions are not required as the HWs are actually programming projects and we will not ask you to write programs in the exam. However, you should be clear with all the algorithmic details and theoretical details asked in the HWs and as desired in writing conceptual programs, before appearing for the exam. If you need more practice you can look into previous years websites where you may find some solutions. If you find a similar question in the past semesters' HW being given this time you should not look at its solution as this will constitute academic dishonesty.