Canvas
(103L site)

• Instructors and Meeting Times:
  • Lectures
    • Monday 10:05am-11:20am, LSRC B101
    • Friday 10:05am-11:20am, French Sciences 2231
  • Labs
    • 5L: Wednesday 11:45am-2:40pm
    • 6L: Wednesday 3:05pm-5:55pm
    • 8L: Thursday 11:45am-2:40pm
    • 9L: Thursday 3:05pm-5:55pm
    • Note: For lab, we will be using Zoom in lab to foster communication between the students, the TAs, and the instructor.
  
  
• Primary Materials :
  • Think Python 2e, Allen B. Downey - free on web page or available to purchase, Creative Commons BY-NC 3.0 Unported license
  • How to Think Like a Computer Scientist: Interactive Edition - free at Runestone Academy
  • Python for Computational Science and Engineering, Hans Fanghor - free on web page
  • Applied Numerical Methods with Python for Engineers and Scientists, 1st Ed., Steven C. Chapra and David E. Clough - access through McGraw-Hill CONNECT; see announcement on Canvas
  • Anaconda - free Python distribution, with Spyder integrated development environment (IDE); we will be using the Python 3.11 version
• References:
  • Guide to LaTeX, Helmut Kopka and Patrick Daly
  • Overleaf Tutorials
• Optional advanced resources:
  • Python Numerical Methods, Kong, Siauw, and Bayen
  • Numerical Methods in Engineering with Python 3, Jaan Kiusalaas, (c) 2013
• Course objectives:
  • Interpret engineering problem statements and solve them using basic programs
  • Model physical systems and optimize parameters using iterative structures
  • Solve engineering design problems using numerical integration, roots of equations, simultaneous equation solving, finite difference methods, matrix analysis, linear programming, dynamic programming, and heuristic solutions
  • Prepare documentation of engineering design solutions using a document preparation system
• Assessment: This course measures students' progress in meeting the above objectives by requiring them to:
  • Design, write, debug, and compile programs in a laboratory environment that solve specific engineering problems (lab assignments)
  • Design, write, and interpret code in closed and open environments (quizzes)
  • Interpret engineering problem statements, design, write, debug, and compile programs to assist in solving the problem, and write a comprehensive solution using a document preparation system (lab reports)
• Accommodated Testing Delivery
  • Note: Quizzes will be taken outside of class, so the Testing Center will likely not be required. The following is in case that somehow changes. The Testing Center will be utilized for providing testing accommodations to undergraduates registered with and approved by the Student Disability Access Office (SDAO) for testing accommodations. The center operates by appointment only and appointments must be made at least one week in advance, but please schedule your appointments as far in advance as possible. You will not be able to make an appointment until you have submitted a Semester Request with the SDAO and it has been approved. So, if you have not done so already, promptly submit a Semester Request to the SDAO in order to make your appointment in time. For instructions on how to register with SDAO, visit their webpage at https://access.duke.edu/requests. For instructions on how to make an appointment at the Testing Center, visit their webpage at https://testingcenter.duke.edu.
• Grading:
  • Final averages will be based on the following breakdown:

    Homework, APT, and Group Gradescope & Connect	20%
    Labs (PDF) & Individual Gradescope & Connect	40%
    Quiz 1 (Skills Quiz)	20%
    Quiz 2 (Applications)	20%

  • Final letter grades will be based on the following chart.

    Grade	(Grade)-	(Grade)	(Grade)+
    A	90-92.99%	93-100%	Exceptional
    B	80-82.99%	83-86.99%	87-89.99%
    C	70-72.99%	73-76.99%	77-79.99%
    D	60-62.99%	63-66.99%	67-69.99%
    F	N/A	<60	N/A

  • Experience has shown that the work done for the labs and homework greatly assists performance on the tests. That is to say, even though the total weight of these assignments is about/exactly half of the grade, the knowledge and skills learned by doing the labs will be helpful in successfully completing all graded exercises.
• Lab Policies
  • Labs are due at the time assigned - turning in the lab means successfully uploading the files of your lab before the deadline. Late labs may be accepted with a penalty - but you must make arrangements in advance (at least 48 hours) with the lab director.
  • If you cannot finish a lab, e-mail the lab director and your lab TA that you are submitting a partial program on time and that you will be submitting the rest late. COMMUNICATION IS YOUR RESPONSIBILITY!
  • If you need to switch lab sessions one week for understandable reasons, send an e-mail to the lab director and your TA before the earlier of the two labs (your regular one or the one you are switching into).
  • Some of the labs are individual assignments. If you get stuck, use the lab TA's office hours and the lab director's office hours (real and virtual). Do not wait until the last minute to work on an assignment - this will invariably put you in a bad situation where ethical behavior tends to fall by the wayside.
  • For individual assignments, under no circumstances are you allowed to copy programs/labs or any part of programs/labs from other people or look at other people's code until after all graded work for that lab has been turned in. If you want to look at someone else's code after you have both received your grade, that is generally a good way to learn different approaches to programming. You must, however, also gain the intuition and experience that comes with writing and fixing code yourself.
• Religious Observances
  • Generally, required items are scheduled as to avoid known religious observances, though this cannot always be arranged. If you would like to discuss having a test rescheduled due to religious practice, please send the instructors an e-mail. The same is true regarding the need to reschedule turning in a lab assignment. There is a Notification of Religious Holiday form to fill out as well.
• Community Standard
  • All work for this course must be done in accordance with the Duke Community Standard, which reads:
    • Duke University is a community dedicated to scholarship, leadership, and service and to the principles of honesty, fairness, respect, and accountability. Citizens of this community commit to reflect upon and uphold these principles in all academic and nonacademic endeavors, and to protect and promote a culture of integrity.
      
      To uphold the Duke Community Standard:
      • I will not lie, cheat, or steal in my academic endeavors;
      • I will conduct myself honorably in all my endeavors; and
      • I will act if the Standard is compromised.
• Short-term Illness Policy
  • Pratt and Trinity have developed a short-term illness policy. Pratt has posted both the description of the policy and the required electronic forms at Pratt's Policies page. If you are going to miss a class or lab because of a short-term illness, please follow the instructions on that page.