The following policies apply to the CS 23001 lab.
Students are required to attend lab meetings.
Assignments will not be accepted from those who don't participate in the lab. This included attendance.
Attendance is mandatory.
A version control system will be used to turn in assignments (programs and any other required files).
All assignments must be put in the version control system's repository.
Students are responsible for making sure that their work is in the repository.
Work not in the repository will not be accepted.
Code that is not committed cannot be counted. There is no way for the instructor to see code that is not committed.
Grading for the lab will come in two components:
Lab Participation -
A score of 0 - 10 will be given for each lab.
Lab scores are based on lab attendance, the assignment, and an occasional quiz.
Before you leave the lab you must show the lab instructor you have completed or made significant progress on the assignment..
If you do not finish the assignment, show your lab instructor what you have done before you leave.
Scoring on lab participation:
Assignment done and correct
Assignment almost complete or small error
Assignment half complete or major error
Some assignment work done or many errors
Assignment started or nothing correct
Present, no work on assignment
Not present
The lab quiz grades will be graded separately, but are worth ~20% of the overall lab grade.
Project Scores -
Projects are broken into sub-parts.
Each sub-part is worth a specified number of points, as specified in the project assignment document.
Each sub-part is graded and scored.
Grading System -
Grades for your project parts will be submitted to the EVAL folder in your version control.
Check your EVAL folders regularly.
We will leave comments after we've graded your assignments, giving you an idea of why you recieved the score we gave you.
Project parts are due by the time specified on the project assignment pages.
Regrades must be requested via Discord post ONLY in the #regrade-requests channel.
To be eligible for a regrade, a reasonable attempt on the milestone must have been made and committed to subversion by the due date.
There is only one regrade request per milestone.
After initial milestone grade, there is a one week period to request a regrade.
Regrades incur a flat 10% off. This means the highest possible score from a regrade is 90%. (10% off of 100%)
If a request was made and the code is not noticeably better, you will lose 5% off your current grade.
All programs must compile on the CS Department's machines WASP or HORNET.
When a lab instructor is grading the labs, the instructor will not spend time fixing programs that do not compile.
There will be a large point deduction for programs that do not compile, and they will not otherwise be graded. Depending on deadlines you may get some points back if you file your program (see regrade section).
If you have compiling problems, talk to your lab instructor.
It is your responsibility to make sure your code in the repository compiles. When in doubt - recompile.
It is easy to make a mistake in a small change and cause your program to not compile.
Don't hesitate to contact your lab instructor if you have any problems or questions.
Plagiarism of any type will not be tolerated and will be dealt with in accordance to Kent State University's policy on cheating and plagiarism described in the student handbook.
See your lecture instructor's syllabus for plagiarism details.
Students may discuss programming assignments with each other - however, each student must write their own program.
It is not permitted to copy, in any manner, assignment related material (except material provided by the instructor).
You should understand and be able to explain any and every part of any assignment you turn in.