Contact No office hours, but is checked multiple times daily. - Specific questions/issues, particularly conceptual

Transcription

1 CS III: Lab Hi

2 Contact - jadamek2@kent.edu - No office hours, but is checked multiple times daily. - Specific questions/issues, particularly conceptual ones. - Only exception: really odd errors that are truly stumping you. - Do not wait until the last minute; the sooner you contact me, the sooner I can reply.

3 Attendance - Mandatory! - Sign-in sheet. - If you are not on the sheet, you lose 2 points for that week s lab. - *Always* feel free to me if I missed you somehow, but make sure you do so within a week. - Any excuses need documentation; no, traffic is bad, and - You may leave anytime after the lecture is finished, but are encouraged to stay, so that you may ask questions if you get stuck, etc.

4 Plagiarism - Don t do it.. - Never send someone your code by . You cannot stop them from turning it in as theirs, and you both get punished. - If I notice copying, I inform Dr. Nesterenko, then he decides your fate. - Do not try to be clever Swapping interchangeable blocks of code will fool no one: we all have a coding style, I will know yours.

5 Grading - Grades are located on the SVN in a text file called grades in EVAL - Labs are worth 10 pts: you get 5 minimum for turning *ANYTHING* in. - Any points deducted have a reason written. - Generally speaking: code that does compile is NOT a zero, or even a 5. I will read it to see the damage. Please turn stuff in... - (-2 Did not attend relevant lab) will appear at the bottom of an assignment you missed lab for.

6 Assignments - Weekly: basic gist described in lab each week. - All labs are viewable at: - Due every Friday 11:59 PM (for both labs) - Breaks and other special circumstances will be planned ahead of time. - Late assignments will not be graded.

7 Assignments : Submitting - Assignments *must* compile and run on department servers (hornet/wasp). - Submit by uploading to your SVN repository, located at: - Use a browser to make absolutely sure the correct/most up-to-date submission is there.

8 Assignments and SVN : Done Right - Student creates a project Lab1, then writes some code to solve their first lab using their favorite editor. - They test their code in their editor, and are sure it works and solves the lab. Their complete source files are Lab1.cpp and Diff.h - Student opens up SSH: terminal in Mac, Putty, SSH Client, etc. and heads to hornet.cs.kent.edu using their Flashline login info. - Student goes to their homework folder on the server using some cd commands. - They enter the command: svn co cs3lab - The console asks them a few silly questions, including their password. The student enters their Flashline password. - Student enters: ls - a folder called cs3lab is now in their homework folder. - Student enters: mkdir Lab1, creating a new folder. - They open up the SFTP client, and copies their code and two sample text files into the Lab1 folder. - They enter: g++ Lab1.cpp -std=c++0x -o diff : an executable diff appears in the folder. - They run the executable with./diff sample1.txt sample2.txt : it runs just as it should and things are working excellently! - Student goes back into their command prompt and enters: rm diff, deleting the now unnecessary executable. - They next enter: cd.. returning to the cs3lab folder, and then enter: svn add cs3lab - The console returns a message like: - A Lab1 for the folder and all files. - The student now enters: svn commit -m Finished Lab1. Cool cool cool. - The console returns a few messages, the last of which reads like Revision The student opens up Chrome, and heads over to their svn URL. They Proceed Anyway and enter their Flashline info. They see a folder Lab1, and click it. In that folder, they see Lab1.cpp, Diff.h, sample1.txt and sample2.txt. They open each file, and are satisfied it contains their latest code. - They go do other things with their time.

9 Lab Time