Advertisement
Guest User

Untitled

a guest
May 5th, 2019
190
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 18.17 KB | None | 0 0
  1. CS 1332 Spring 2019
  2. Jump to Today
  3. CS1332 Data Structures & Algorithms Spring 2019
  4. Professor
  5. Dr. Mary Hudachek-Buswell
  6. Email: hudachek@cc.gatech.edu
  7. Office: CCB 137
  8. Office Hours: Fridays 11:30 - 1:00, other times by appointment. (I do not hold office hours the first or last week of the semester.)
  9. Spring2019Piazza (Links to an external site.)Links to an external site.
  10.  
  11. Teaching Assistants
  12. Office hours are listed on the "TA Info / Help" page.
  13.  
  14. Timothy J. Aveni – Head TA: tja@gatech.edu
  15. Alok Tripathy – Senior TA: atripathy8@gatech.edu
  16. Andrew Suh – Senior TA: asuh9@gatech.edu
  17. Adrianna Brown – Senior TA: adrianna.brown@gatech.edu
  18.  
  19. Alexander McQuilkin, alexmcq99@gatech.edu
  20. Billy Vaughn, wvaughn9@gatech.edu
  21. Brandon Vu, bvu32@gatech.edu
  22. Caroline Kish, ckish3@gatech.edu
  23. Destini Deinde-Smith, dds7@gatech.edu
  24. Elena May, elena.may@gatech.edu
  25. Garrett Monroe, gmonroe8@gatech.edu
  26. Ila Vienneau, ivienneau3@gatech.edu
  27. Jacob Allen, jallen317@gatech.edu
  28. Joey Jackson, ejackson61@gatech.edu
  29. Mahima Chander, mchander6@gatech.edu
  30. Maya Pogrebinsky, mpogrebinsky@gatech.edu
  31. Miguel de los Reyes, mbclr3@gatech.edu
  32. Neha Deshpande, neha.n.deshpande@gatech.edu
  33. Nicholas Worthington, nworthington3@gatech.edu
  34. Paige Ryan, aryan34@gatech.edu
  35. Reece Gao, rgao@gatech.edu
  36. Robert Turko, rturko3@gatech.edu
  37. Rodrigo Pontes, rpontes3@gatech.edu
  38. Sanjana Tewathia, stewathia3@gatech.edu
  39. Siddu Dussa, adussa3@gatech.edu
  40. Stephanie Baione, stephaniebaione@gatech.edu
  41. Walker Powell, wpowell9@gatech.edu
  42. Will Crawford, will.crawford@gatech.edu
  43. Yotam Kanny, ykanny3@gatech.edu
  44. Younmin Bae, ybae35@gatech.edu
  45.  
  46.  
  47. Where to Find your TA:
  48. - Help Desk or TA Office Hours will be held in the College of Computing – CCB 104A.
  49. - Schedule of Help Desk hours will be posted on Canvas. You may see ANY CS1332 TA for help.
  50.  
  51. Course Information
  52. Lectures and Final Exams:
  53. Section A lecture is Monday/Wednesday/Friday in Clough 152 from 9:05 AM – 9:55 AM
  54. Section A FE is Wednesday, May 1st, 8:00 AM – 10:50 AM
  55.  
  56. Section B lecture is Monday/Wednesday/Friday in Clough 152 from 10:10 AM – 11:00 AM
  57. Section B FE is Friday, April 26th, 8:00 AM – 10:50 AM
  58.  
  59. Section C lecture is Monday/Wednesday/Friday in Howey L3 from 1:55 PM – 2:45 PM
  60. Section C FE is Monday, April 29th, 2:40 PM – 5:30 PM
  61.  
  62. Prerequisite:
  63. You must have a C or better in CS1331 to remain in this course. If you do not have this prerequisite you will be dropped.
  64.  
  65. Recommended Textbook:
  66. Data Structures and Algorithms in Java. 6/edition by Goodrich, Tamassia, and Goldwasser 2014 ISBN: 9781118771334 (Kindle edition is fine. The 5th edition is probably also fine.)
  67.  
  68. Course Website/Resources/Communication:
  69.  
  70. Canvas is the course management tool for the semester, http://canvas.gatech.edu/ (Links to an external site.)Links to an external site..
  71. Gatech email is the official communication tool between professors and students for this course. You must check for messages on a regular basis. All communication with your professor should be through the Canvas Email.
  72. Here is the Piazza link to CS1332 Spring 2019, Sp19Piazza (Links to an external site.)Links to an external site.
  73. Students are responsible for any and all announcements made during lecture or on Canvas.
  74. Java 8, Checkstyle 8.12, JUnit 4.12
  75. IDE is your choice, the TAs officially endorse IntelliJ as an IDE
  76. Party AVL
  77.  
  78.  
  79.  
  80. Course Objectives:
  81. Develop more skills in individual Java programming
  82. Work with common data structures used in software development by coding their low-level implementation
  83. Arrays, ArrayLists,
  84. LinkedLists (Singular, Doubly, Circular)
  85. Stacks, Queues, Deques, Priority Queues
  86. Various Trees: Binary, Binary Search, AVL, Splay, Heaps, 2-4 Trees, etc…
  87. Hash Maps/Tables; External Chaining and Probing
  88. Graphs and their algorithms
  89. Become familiar with common algorithms on these data structures
  90. Sorting Algorithms: Bubble, Insertion, Selection, Cocktail Shaker, Merge, Quick, Radix etc...
  91. Pattern Matching Algorithms: Brute force, Boyer-Moore, KMP, Rabin-Karp
  92. Graph Algorithms: Dijkstra’s Shortest Path and multiple MSTs
  93. Dynamic Programming Algorithms
  94. Work with Big-O notation, allowing good choices about the appropriate data structure and algorithm to use for a particular programming problem
  95. Improve one's ability to test and debug programs
  96. Lecture Attendance is required, Recitation Attendance is highly encouraged, and it is assumed you are attending. You are responsible for any and all announcements made during lecture whether you are present or not.
  97.  
  98. All students are required to attend the lecture that they are registered in for the duration of the semester. No switching sections will be allowed.
  99.  
  100. “Sitting in" is against GT Policy, and is explicitly not allowed. We do not violate Institute policy. You are not allowed to attend without being registered. Problems with this will be turned over to the Dean of Students and/or GT Police.
  101. Conduct Policy:
  102. It is expected that everyone will follow the Student-Faculty Expectations document, and the Student Code of Conduct. The professor expects a positive, respectful, and engaged academic environment inside the classroom, outside the classroom, in all electronic communications, on all file submissions, and on any document submitted throughout the duration of the course. No inappropriate language is to be used, and any assignment, deemed by the professor, to contain inappropriate or offensive language will get a zero. You are to use professionalism in your work. Violations of this conduct policy will be turned over to the Office of Student Integrity for misconduct.
  103. Assessments and Grade Thresholds:
  104. There will be homeworks every week and exams are roughly 4 weeks apart. Expect for a homework to be due during the last full week of class of the semester.
  105. There are NO “dropped” exams or homeworks.
  106. There is NO curve in this course. Letter grade cutoffs use a straight scale.
  107. The final exam is mandatory.
  108. In addition to having a passing average, you must have a passing exam average (all exams and the final are averaged together, unweighted) to pass this class. Passing is hereby defined as 70% or higher.
  109. There is a Participation grade for this course. Students will have "Reality Checks" on topics every week that will be turned in during lecture. Feedback will be given to students who complete the work.
  110. Type Assessment Points Grade Scale Percentage
  111. Participation 4% A 90.0%
  112. Homework/Programming 16% B 80.0%
  113. Exams (3) 60% C 70.0%
  114. Final Exam 20% D 60.0%
  115. Total 100% F less than 60.0%
  116. Party AVL
  117.  
  118.  
  119.  
  120. No – Makeups/Exceptions:
  121. There are no makeups for missed exams or homeworks or reality checks. Institute approved absences are rare and do qualify for an exception.
  122. Please minimize absences to attend the Georgia Tech All Majors Career Fair. Exam 1 will still take place on February 6 because there is no conflict with any of the career fairs.. Additionally, for any absences due to interviews, you must provide documentation from the employer on letterhead with the exact interview/travel dates. In order to be excused for attendance at a career fair, you must send an email to the professor prior to the event with the exact day and time. An excuse for career fair attendance will only cover Reality Checks, not homework.
  123. If you are absent due to official Georgia Tech business, please forward the electronic official documentation to the professor in an email stating the dates you will be absent. It will be noted in the gradebook.
  124. Events such as vacations, weddings, graduations, errands, work conflicts, sleeping through your alarm, alarm malfunction, forgetting to submit, forgetting the date or time of an exam, not being aware of the assignment are all not valid excuses.
  125. If you miss any assignment without a valid excuse, then you receive a 0.
  126. If you will be observing religious holidays during the semester, then inform your professor the first week of the semester in writing, especially of any conflicts with exam dates.
  127. Any request for exceptions to the no-makeup policy must be made in advance of the assessment unless that is impossible.
  128. Documented incapacitating illness, death in the family, judicial procedures, military service, or official school functions are considered valid excuses. Be aware that documentation must be provided on letterhead with the signature of a physician, supervisor, or other appropriate official. Additionally, the excuse must be encompass the date(s) of any assignment for which you are requesting an exception. All situations will be referred to the Dean of Students Office for verification. Therefore, contact the Dean of Students with your documentation, and they will inform you of the proper procedures.https://studentlife.gatech.edu/ (Links to an external site.)Links to an external site. The Dean of Students Office, then contacts your professor directly with any accommodations to be provided.
  129. The final decision regarding any exception is made solely at the discretion of your professor.
  130. We will only offer a single makeup day for each exam. We write a brand new exam for makeups so that the integrity of the exams remains intact. The exam makeup day takes place one week later on a Thursday (when classes are in session) from 11 to noon in the TA helpdesk lab. If you have an excused absence, then you may take the makeup exam at this time. If you miss the makeup day, then you must have another institute approved absence in order for us to consider alternative dates. If you miss the makeup day without a valid excuse, then you receive a 0.
  131. Grade Disputes/Regrades:
  132. We will be using Gradescope this term, which allows us to provide fast and accurate feedback on your work. Exam grades will be returned through Gradescope. Your Gradescope login is your university email, and your password can be changed here (Links to an external site.)Links to an external site.. When the first assignment is released, you will receive an email to set your password for the first time. As soon as grades are posted, you will be notified immediately so that you can log in and see your feedback.
  133. If you feel that a regrade request is justified, visit the Help Desk with your laptop and discuss the dispute with any TA. The TA will give you instructions on how to submit your regrade request.
  134. Grade disputes are rare, but if you find yourself not clear about why points were lost, we have a strict policy and procedure to follow. Disputes of grading on assignments, exams, etc. must be discussed within 7 days of the assignment being returned. Any exceptions to this timeline will be announced before grades are released. All regrade requests go through the Head TA. Should you find yourself having an issue with a grade, contact the Head TA. No regrade requests submitted after the deadline or without approval from a TA will be considered.
  135. If the Head TA is unable to resolve the issue, contact your instructor.
  136. Every regrade request must have a detailed reason why a regrade is needed. “I'd like to get more points" is not a valid reason and will result in the request being promptly declined. Furthermore, any regrade request that is not respectful and professional will be declined. Be aware that any regrade request may result in your entire exam or homework being regraded. Your grade may go up or down.
  137. It is your responsibility to ensure that all the grades in Canvas are correct before finals week. After that, the only grade discussion will be about the grading of your final exam. Any discussion of your grades after the final exam must be done in person, and cannot occur until the 3rd week of the next semester you are in school. Final exams are not released or returned to students. They remain on file for the college.
  138. Academic Honesty:
  139. Every Student is expected to read, understand and abide by the Georgia Tech Academic Honor Code. http://www.honor.gatech.edu/ (Links to an external site.)Links to an external site.
  140. File sharing is expressly forbidden. Do not give your code to another student, nor take code from another student. Both activities are academic misconduct and forms of cheating.
  141. Proper collaboration means talking through problems, assisting each other with de-bugging, explaining a concept, etc… Diagramming and high-level discussions are acceptable forms of collaboration.
  142. You may only use pseudocode provided in the course materials. This means, you are NOT allowed to use pseudocode or code from your peers or the internet, including Github, Gitlab, or Bitbucket.
  143. You are not allowed to simply exchange code or write code for others. This still applies even if you make trivial changes such as variable names, comments, styling, etc...
  144. The only code you are allowed to share is JUnits on a pinned post on Piazza. Use JUnits from other students at your own risk. We will not be endorsing them. See assignments for more details. If you share JUnits, they must be shared on a site that we specify and not in random locations like Facebook, your GitHub account, etc...
  145. Violators of the collaboration policy for this course will be turned into the Office of Student Integrity.
  146. Homework Submission & Responsibility:
  147. All course information and resources can be found in Canvas http://canvas.gatech.edu/ (Links to an external site.)Links to an external site. to include: Syllabus, Assignments, Submissions, Announcements, Grades & Feedback, Resources, ….
  148. All homework for all sections will have a single due date. Homework due dates may differ depending on the length of the assignment. Homework is always due at 11:55:00 pm for full credit consideration. There is a grace period until 2:00:00 am the following day, but your submission will be marked as late by Canvas, and you will be penalized 25 percentage points for the assignment. Do not ask for an exception to the late policy unless you have a valid excuse accompanied by documentation that has been submitted to the Dean of Students office.
  149. Homework turn-in is via Canvas. Turning in homework properly on Canvas is solely your responsibility. That last statement bears repeating.
  150. Canvas is NOT forgiving about due dates and times. Imagine a train taking off whether or not you are fully onboard. It has no love.
  151. Turning in homework properly on Canvas is solely your responsibility.
  152. Canvas submissions:
  153. It is completely within your power to make sure your homework is submitted properly. If you are not conscientious about your submission, then there is a high likelihood you will trip up and not turn in one or more assignments correctly.
  154. You are to upload the .java files and any other files required by the assignment. .class files will not be graded and will be given a 0. To receive credit, the file(s) must compile in Java 8 using only JUnit 4.12 and the Java standard libraries.
  155. After submitting your file(s) for a HW, reload Canvas going to the Assignments link within the CS1332 tab. Look at the assignment in question. You should now see that it says it has been submitted with the date and time.
  156. Download a fresh copy of the files from Canvas, saving to a new folder, and then recompile and run that code. Following steps 1, and 2 is truly the only way to confirm what you have turned in.
  157. Failure to upload the proper file(s) for a homework will result in a zero for the assignment. Programs that do not compile or run also receive no credit.
  158. Party AVL
  159.  
  160.  
  161.  
  162. Exam Instructions:
  163. If you arrive to an exam more than 15 minutes late, we will refuse entry. You must bring your GTID to every exam so it can be scanned. You are to attend your section’s exam, not another one. If you attend a different section’s exam, then you will receive an automatic zero on the exam.
  164. Signing and/or taking the exam signifies you are aware of and in accordance with the Academic Honor Code of Georgia Tech and the Georgia Tech Code of Conduct.
  165. Special seating assignments may be required at the start of the exam.
  166. Notes, books, calculators, phones, laptops, smart watches, headphones, etc. are NOT allowed.
  167. Under NO circumstances are you allowed to leave the exam room until you have turned in the exam.
  168. Extra paper is NOT allowed. If you have exhausted all space on this test, talk with your professor.
  169. Pens/pencils and erasers are allowed. Do not share.
  170. All code must be in Java.
  171. Efficiency matters. For example, if you code something that uses O(n) time or worse when there is an obvious way to do it in O(1) time, your solution may lose credit. If your code traverses the data 5 times when once would be sufficient, then this also is considered poor efficiency even though both are O(n).
  172. Style standards such as (but not limited to) use of good variable names and proper indentation is always required. (Don’t fret too much if your paper gets messy, use arrows or whatever it takes to make your answer clear when necessary.)
  173. Comments are not required unless a question explicitly asks for them.
  174. Final Exam Instructions (in addition to all the above instructions):
  175. According to Institute rules, three exams in one day constitutes a Class Two conflict. Per those guidelines, http://www.catalog.gatech.edu/rules/12/ (Links to an external site.)Links to an external site. , you are expected to notify your instructor and make alternative arrangements two weeks before the beginning of exam week, before April 8th. This notification window is essential, because faculty members have a very busy time during finals week, and alternate exam periods are not always easy to arrange at the last minute. Additionally, per the posted regulations, when there is a Class Two conflict, it is always the middle exam period that is deemed to be in conflict, and the instructor of that course should be contacted with regard to alternative arrangements.
  176.  
  177. Important Dates (all dates are tentative and subject to change):
  178. First Lecture Day January 7, 2019
  179. First Recitation Day January 15, 2019
  180. Holiday (No class) January 21, 2019
  181. Exam 1 February 6, 2019
  182. Exam 2 March 6, 2019
  183. Withdraw Deadline March 13, 2019 (4pm)
  184. Spring Break (No Class) March 18-22, 2019
  185. Exam 3 April 10, 2019
  186. Last Lecture Day April 22, 2019
  187. Last Recitation Day April 23, 2019
  188. Final Section A May 1, 2019, 8:00am - 10:50am*
  189. Final Section B April 26, 2019, 8:00am - 10:50am*
  190. Final Section C April 29, 2019, 2018, 2:40pm - 5:30pm
  191. *Since Section A & B are at 8:00 am there will be no rescheduling. Contact your other Professors of the second exam for rescheduling.
  192.  
  193.  
  194. Party AVLs
  195.  
  196.  
  197.  
  198. Created by Adrianna Brown
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement