1. Fall 2o12 – August 27, 2012

2. CMPSC 202 First Day Handouts  Syllabus  Student Info  Fill out, include all classes and standard appointments  Return to front before you leave or turn in later this week if your schedule is changing  Autobiography  Do outside of class. Bring back 2 copies W or F.  Index Card: Name Tag  Write first name you want me to call you in big text  Return markers to front

3. Today’s Plan  Introductions  Some highlights of the syllabus  Quick tour of course web site  Lecture on background material  Continues Wednesday

4. Introductions  Instructor: Doug Hogan  TA  Class Roster

5. Out of Class  Office hours (338c IST)  Drop in. First-come, first-served  Email – hogan@cse.psu.eduhogan@cse.psu.edu  Best way to reach me outside of scheduled times  Evening help session  Work on assignments with someone around to help, ask questions  Runs most Wednesdays from 8:15-9:30 in 113 IST  Starts next week, not this week

6. Prereq. & Appropriate Course  Prerequisite: MATH 140  Mainly for mathematical sophistication  Derivatives and integrals  Introductory programming for engineers  200, 201, 202 are similar  121 is for CSE majors  AERSP, C E, E SC, I E, NUC E allow this course

7. Very High Level Plan  13 weeks – how to program, using Fortran as the target language  2 weeks – a taste of Matlab

8. Books  Fortran text – customized  Optional  Everything you need to know is on the web  Book provides more examples, practice, and a second view  You decide how to use it  Matlab text – required  Not needed until after Thanksgiving  Buy it soon, regardless

9. Class Conduct  Be here before class starts, seated and ready to pay attention  Remain seated during lecture and whole-class discussions  If your monitor is on during lecture, only have the same thing on your screen I have on mine  No web surfing, chat, doing assignments, etc.  No cell phones. Keep them away and silent.  Respect the room and your peers and us.

10. Attendance Notes  If you’ll miss a class, email or stop by the office no later than the afternoon before  You’re expected to be here all classes  If you don’t follow the rules above, you’re effectively not here

11. In Class Labs  Where you first get practice with new concepts  An avenue for feedback  Sometimes we mark up all labs, sometimes there’s an early deadline to get individual feedback – if you follow conventions  Nearly always class-wide feedback  Grading  Check, check-minus, or no credit (incomplete, poor effort)

12. In Class Lab Grade  (# of labs with a check) – (# labs with check- minus)/4  Denominator is adjusted by 90%  Everyone gets benefit of the doubt this way  No late work, make-ups if you miss, etc.  Counts 10% of final grade  Lab and attendance percentage must be at least as good as overall grade

13. Formal Assessments  Two options:  Standard assessments – all proctored – for up to B+  Out of class projects and programming exam for extra challenge and eligibility for A or A-  Standard assessments:  Two midterms – 30%  Final – 25%  Graded Programming Assignments in Class – 25%  Quizzes – 10%  (In Class Labs – 10%)

14. Exams  Mix of conceptual ideas and programming problems  Cumulative  8:15 – 10:15 p.m. on 10/11 and 11/14  Conflict exam form on syllabus due two weeks in advance if applicable

15. Graded Programming Assignments  In class, proctored  Five total  A problem designed to be solved in 50 minutes if you’ve been keeping up with the course  Generally every 3 rd Friday  May use notes, but may not discuss with anyone  Grading: ½ on our test of the program, ½ on programming practices

16. Quizzes  Short, about 10-20 minutes  One every week there’s not another major graded event  Lowest is dropped

17. A-level Assessments  Why?  Different goals  Different levels of time and effort you want to put in  Higher-level skills  Midterm take home project  Proctored programming exam –planned for evening of 12/5, starting 6:30 p.m.  Term project  Need at least a B on all three and an A on two to be eligible for A or A-

18. Academic Integrity  Do your own work  All proctored activities are individual  The program output you say the program produced must have been produced by the program  See syllabus for more  It’s okay to discuss practice labs with classmates. It’s not okay to share code.

19. Syllabus and Course Site  Read the whole syllabus carefully. As questions later this week about anything you don’t understand.  Course Web Site:  http://www.personal.psu.edu/djh300/cmpsc202 http://www.personal.psu.edu/djh300/cmpsc202  Don’t use Internet Explorer  Let’s take a quick tour…