|
Course Organizer
COP 4530 Data Structures, Algorithms, and Generic Programming
Spring Semester 2014
Root View: Course Components Syllabus The course syllabus establishes course policies on grading, attendance, and exams. The syllabus should be read in detail at beginning semester. Lectures This is the main knowledge resource for the course. Lectures are in the form of a slide show with an accompanying narrative. (Click "Narrative on" to see the narrative. Click "Frames[Windows]" to toggle between displaying the narrative in a separate frame or a separate resizable window.) Please report bugs/corrections in the appropriate Blackboard discussion forum. Note: The lecture notes are undergoing revision during the semester. Calendar The course calendar: coverage, assignments, lecture notes all released here. Assignments Assignments are intended to be total learning experiences, not merely exercises in programming. The assignment documents in particular are used to elaborate on topics and introduce new ones. The content of assignments is of equal importance with the lecture notes. Assignments will be released through the calendar. Note that assignment deadlines will be enforced and that successful completion of most assignments requires starting at least two weeks in advance of the deadline. Assignments will be assessed using the policy described here. We expect polished, thoughtfully prepared work and will assess accordingly. Note that a work log is expected for each programming assignment. Office Schedule, office hours, and contact information for Chris Lacher LIB The course code distribution library LIB = /home/courses/cop4530p/spring14/ Testing Environment Code submitted for assignments will be built and tested on linprog using g++ version 4.7 and the ISO-11 standard library. Code Stds A C++ coding style guide - required for this course.
Extras: Miscellaneous Resources and References COP 3330 The lecture notes from the pre-requisite course SSH The version of ssh software that FSU pays for and recommends. See SSH, The Secure Shell: The Definitive Guide, Second Edition (O'Reilly) for more info on SSH. FAQ Frequently Asked Questions harvested from discussion boards Make1
Make2Two tutorials on the make utility and makefiles Valgrind Valgrind is an instrumentation framework for building dynamic analysis tools. There are Valgrind tools that can automatically detect many memory management and threading bugs, and profile your programs in detail. You can also use Valgrind to build new tools. C++ Ref A resource to look up C and C++ libraries My FSU The FSU/Blackboard Portal, where you will find this course. The course site is the main communication resource for the class. Here you can get help, talk to other students, retrieve your grades, and generally keep up with course news and announcements. Office Hours Instructor office hours and contact information Unix/Emacs Hints Lacher's Unix and Emacs hints to get started Princeton
Stanford
GnuMore Emacs help info - from various sources. Very brief reminders on setting up and checking CS Email. g++ The gnu compiler manual, maintained by gnu itself. MazeBuilder
MazeBuilder2A nifty JavaScript maze accessory. Original by Isaac Olson requires IE 6+. Refactored version by Stephen Brown is compatible with many other browsers, including those running on Linux. TreeDemo
Models of various ordered set implementations using binary search trees.
Unix Script Submission Process:
Most programming assignments will be submitted via a specific Unix script from your CS Majors account logged in to shell.cs.fsu.edu. The submission script for a given assignment will be located in the assignment directory.
Submission via script should generate two email responses:
- When your submission is received, a receipt is sent via email. The date/time stamp of this email is the official submission time.
- After your submission has been unpacked and placed in your portfolio, a second message is sent containing a copy of all files that were unpacked. This is a record of exactly what was received and placed in your portfolio.
After submission, be sure to check your email for these two messages. Normally these would arrive within a few seconds of submission. If you do not get both email responses, a malfunction occurred. When you do receive these confirmation emails, save them. If a problem were to arise with your files, these emails are your proof of submission.
Note that revisions may be submitted any time prior to the deadline and will automatically replace the previous submission.