EGR 103/Fall 2023

EGR 103 is a course for students planning to earn a Bachelor of Science in Engineering Degree at Duke University and who have limited previous computational experience. Students with AP credit for Computer Science A or significant programming experience may choose to take CS 201 instead.

This page is meant to provide answers to general questions about the course, not necessarily specific questions about content. There is also a Category:EGR 103 that will list all pages relevant to EGR 103. Note at the bottom of this page that it is a member of that category. Finally, there is an EGR 103 Startup page in progress, meant as a kind of "Guide to your first 100 hours taking an EGR class."

Support Pages for Fall 2023

Concept List

The list of concepts covered in each lecture will be available at EGR 103/Concept List/F23

Working on your computer

There is now a page on Working on your computer which includes the software you will need to install and the processes you will need to follow to do work for this class.

Python Common Mistakes

There is now a page on Python:Common Mistakes with a list of common pitfalls in Python. If you are experiencing bugs in your scripts, it can be useful to check this page for common errors and fixes.

Lectures

Any resources useful in support of particular lectures will be posted here.

Labs

For Lab 0 (first week of class) you need to do the following:

• Read Box and follow the instructions to get Box Drive installed on your computer and create a folder inside your Box folder for EGR103F23
• Read Installing_Anaconda_and_Spyder and follow the instructions to install the Anaconda distribution of Python on your computer if you do not already have it or make sure you have Anaconda and Spyder 5.4.3 if you have previously installed Anaconda
• Deliverable: Have Box Drive and Anaconda installed and working on your computer and have a folder called EGR103F23 in your Box Drive.

For Lab 1 and beyond, you will want to start by going through the steps at EGR 103/Fall_2023/Beginning of Lab. Also, note that assignments will be at the Assignments page at the classes site.

• Lab 1:
  • Lab 1 Main Pundit page
  • Lab 1 will be submitted as a PDF, see the EGR 103/Uploading Solutions page for details.
• Lab 2
  • Lab 2 Main Pundit page
  • Lab handout references: Python, Python:Script, Python:Plotting, EGR 103/Uploading Solutions
  • Also note that there is a Connect assignment for this week!
• Lab 3
  • Lab 3 Main Pundit Page
  • Lab handout references: Python:Script, Python:Plotting
  • Also note that there is a group Gradescope assignment and an individual Connect assignment
• Lab 4
  • Lab 4 Main Pundit Page
  • Lab handout references: Python:Script, Python:Plotting
  • Also note that there is a group Gradescope assignment and an individual Gradescope assignment

Introduction and Information about Laboratory Work

Purpose

The primary goal of the laboratory assignments is to give students practical, hands-on exposure to some of the most common computational methods used by engineers. In accomplishing this, we employ short- and medium-scale problems from the major fields of engineering that Duke has to offer in the hopes that students will be able to better choose which engineering discipline(s) to pursue during their undergraduate career. Furthermore, we extend computational methods outside the computer itself using analog and digital inputs and outputs, reinforcing the real-world importance of computers and computational methods with respect to engineering.

Ownership of Work

All the work you do for this class needs to be properly documented and owned. For the reports, this is most easily done with a title block at the top of the assignment. For any graph that you create, you will be including your NetID in the title of the graph as a statement of ownership and adherence to the Community Standard.

For all functions and scripts you create for graded assignments in this course, you must include a title block as well. The format of the title block depends on whether the function or script in question will be turned in on its own or attached to a lab report. Furthermore, the contents of the title block depends on whether the code you have written is original or a modified form of pre-written code.

Standalone Programs

For programs you write yourself that will be turned in on their own, you need to use the following header:

"""
[Function or Script Name]
[Your Name]
[Date Written]

I understand and have adhered to all the tenets of the 
Duke Community Standard in creating this code.  I understand 
that a violation of any part of the Standard on any part of 
this assignment can result in failure of this assignment, 
failure of this course, and/or suspension from Duke University. 
Signed: [Your NetID]
"""

If you are given a piece of code to modify and then turning in the result on its own, the following header must be used:

"""
[Function or Script Name]
[Your Name]
[Date Modified]
Based on: [Original Script or Function]
Written by: [Original Author]

I understand and have adhered to all the tenets of the 
Duke Community Standard in creating this code.  I understand 
that a violation of any part of the Standard on any part of 
this assignment can result in failure of this assignment, 
failure of this course, and/or suspension from Duke University. 
Signed: [Your NetID]
"""

An example header might look like the following:

"""
sample.py
Jane Doe
January 29, 2023

I understand and have adhered to all the tenets of the 
Duke Community Standard in creating this code.  I understand 
that a violation of any part of the Standard on any part of 
this assignment can result in failure of this assignment, 
failure of this course, and/or suspension from Duke University. 
Signed: jjd9
"""

Programs Attached to Lab Reports

For EGR 103, you will generally be submitting codes as appendices to lab reports. Since the "full" text of the Duke Community Standard will be on the cover page of the lab report, you are allowed to use a shortened version on subordinate works. Specifically, for original code you may use:

"""
[Function or Script Name]
[Your Name]
[Date Modified]

I have adhered to all the tenets of the 
Duke Community Standard in creating this code.
Signed: [Your NetID]
"""

and for modified code you may use:

"""
[Function or Script Name]
[Your Name]
[Date Modified]
Based on: [Original Script or Function]
Written by: [Original Author]

I have adhered to all the tenets of the 
Duke Community Standard in creating this code.
Signed: [Your NetID]
"""

F.A.Q.

Do I need to buy Python?

• No - Python is free.

Do I need a Lab Notebook

• Nothing special - whatever you use to take notes in class should be fine for lab.

Questions

Post your questions by editing the discussion page of this article. Edit the page, then scroll to the bottom and add a question by putting in the characters *{{Q}}, followed by your question and finally your signature (with four tildes, i.e. ~~~~). Using the {{Q}} will automatically put the page in the category of pages with questions - other editors hoping to help out can then go to that category page to see where the questions are. See the page for Template:Q for details and examples.

External Links

• http://classes.pratt.duke.edu/EGR103F23 - Main page for EGR 103
• Canvas link - Canvas page for EGR 103
• Ed Link - Ed page for EGR 103