Assignment Submission Rules

To receive full credit for your assignments the following rules have to be followed. Violation can cost up to 100% of your Assignment credit. Please read the information on the page carefully, you are responsible for the knowledge of the material put up here. If anything in this page is ambiguous, please clarify with the TA's immediately. No excuses will be entertained. 

• • Please put your full name, student ID, section, and Gator ID on every assignment. This is only way for us to know that its your work. Insert this information as a commented part before the beginning of your code.

            The format is:

                        Name : XXXXXXX

                        UF ID: XXXXXXX

                        Discussion section # : %%%%%%%%%%%

           If this information is missing you get 0 credit for the assignment. 

• • Late HWs: The HWs will be posted every Monday before class and will be due the following Monday before class unless stated otherwise. Remember, it has to be submitted before class through the online course management system Sakai. Any HW submitted after the class is over, or during the class will be considered late and will receive an automatic zero. Late  HWs are strongly discouraged due to the fast pace of the course.

    • However, we will give you 5 grace days throughout the whole semester. Use it for whatever reason you like. There will be no penalty for submitting late till the time your 5 grace 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 3 days late, then you will only have 2 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. The .cpp file (say, ProgramName.cpp) must compile successfully.

      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.

      3. To create a tar file:

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

      4. To extract the contents of a tar file:

• • • • 1.   tar xvf (tar file name)

• • • 5. 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:

• • • • 1.   tar cvf MyAssigment.tar ProgramName.cpp readme.txt

        2. 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.

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

• • No copying of assignments is allowed. Please look at the Academic Dishonesty policy. We will run MOSS on your assignment, and view cases of cheating seriously.