Difference between revisions of "EGR 103/Fall 2022"

From PrattWiki
Jump to navigation Jump to search
(→‎Labs)
(→‎Labs)
 
(One intermediate revision by the same user not shown)
Line 82: Line 82:
 
** Lab handout references: [[Numerical Differentiation]]
 
** Lab handout references: [[Numerical Differentiation]]
 
* Lab 13
 
* Lab 13
−
** [[EGR 103/Spring 2022/Lab 12 | Lab 12 Main Pundit Page]]
+
** [[EGR 103/Fall 2022/Lab 13 | Lab 13 Main Pundit Page]]
 +
* Lab 14
 +
** [[EGR 103/Fall 2022/Lab 14 | Lab 14 Main Pundit Page]]
 +
** [[Python:Ordinary_Differential_Equations]]
 +
** [[Python:Ordinary_Differential_Equations/Examples]]
 +
** [[Python:Ordinary_Differential_Equations/Templates]]
  
 
<!--
 
<!--
Line 100: Line 105:
  
  
−
* Lab 13
+
 
−
** [[EGR 103/Fall 2021/Lab 13 | Lab 13 Main Pundit Page]]
 
−
** [[Python:Ordinary_Differential_Equations]]
 
−
** [[Python:Ordinary_Differential_Equations/Examples]]
 
−
** [[Python:Ordinary_Differential_Equations/Templates]]
 
 
-->
 
-->
  

Latest revision as of 13:17, 6 December 2022

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 2022

Concept List

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

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.

  • Lecture 01:
    • Main web page: [1]

Labs

Lab support pages. Generally, you will want to start by going through the steps at EGR 103/Fall 2022/Beginning of Lab. Also, note that assignments will be at the Assignments page at the classes site.



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.

Grand Challenges

EGR 103 will also be looking at the 14 Grand Challenges for Engineering chosen by the National Academy of Engineering. One of the Challenges, "Engineer the tools of scientific discovery," is a large part of what this course is all about. Computational methods can be used to collect, analyze, and present data from various experiments in order to get a better sense of how the universe works. The inclusion of data acquisition techniques in this class allows us to use a wide array of sensors for gathering that data rather than being limited to "cooked" data sets of unknown origin.

Another of the Grand Challenges, the quest to "Advance personalized learning," relates to looking at the different ways people can learn information for themselves. While there will be several opportunities for students to be taught as a group, we will be providing different resources for individual students to expand the breadth and depth of learning on their own. This includes making sure all class assignments are posted on the web, providing a discussion forum for students and class staff to talk about different aspects of the course, and creating a wiki-based interactive knowledge database. Also, we will present and explore different approaches to solving various problems in the knowledge that different students perceive computational methods in different ways.

For the remaining 12 Grand Challenges, we will link specific assignments to the relevant field or fields that may support it. For example, a problem on optimizing the dimensions of a water channel will relate to both the challenge to "Provide access to clean water" as well as the challenge to "Restore and improve urban infrastructure." Laboratory assignments introducing students to sensors and sensor technology relate to the challenge to "Prevent nuclear terror," in that accurate, rapid, and long-distance detection of fissile material is a key element of such prevention.

Note also that the Pratt School of Engineering is host to the NAE Grand Challenge Scholars Program at Duke. The program description, found on the web site, is:

The Duke NAE Grand Challenge Scholars Program educates engineering undergraduates to have the technical expertise, breadth of knowledge, and the social, ethical, and environmental awareness to successfully pursue leadership positions in addressing the NAE Grand Challenges for Engineering...this will be accomplished by requiring each GC Scholar to propose and complete a five-component GC portfolio, and by completing a GC senior thesis.


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
September 18, 2022

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

References

Retrieved from "https://pundit.pratt.duke.edu/piki/index.php?title=EGR_103/Fall_2022&oldid=29183"