MEEN 357

Engineering Analysis for Mechanical Engineers

Fall 2020
Section 502 • Class: TTh 11:30am - 12:45pm online

1. General Information
Instructor: Prof. Pilwon Hur, Ph.D.
Phone: (979)862-4461
Email: [email protected]
Office: MEOB 222
Office Hours: TTh 11:00 – 11:30 am, 12:45 – 1:15 pm (via Zoom) or by appointment
Lecture: Synchronous via Zoom (check eCampus for the link)
TA:
1) HW2-4: Alaba Bamido ([email protected])
2) HW5-7: Sandipan Paul ([email protected])
3) HW8-10: Sencheng Yu ([email protected])
Python Help Desk:
1) Mazen Ali ([email protected]) Schedule with Zoom link (TBA)
2) Tray Ramirez ([email protected]) Schedule with Zoom link (TBA)
3) Maria Parison ([email protected]) Schedule with Zoom link (TBA)
4) Samuel Ortiz ([email protected]) Schedule with Zoom link (TBA)
5) Jiafei Wang ([email protected]) Schedule with Zoom link (TBA)
Textbook: J. Kiusalaas, Numerical Methods in Engineering with Python 3, Cambridge University
Press, Cambridge, 2013.
Other References:
1) R. M. Bowen, Lectures on Applied Mathematics, Part 1: Linear Algebra, available for
download on eCampus.
2) R. M. Bowen, Lectures on Applied Mathematics, Part 2: Numerical Analysis, Written
for Matlab and available for download on eCampus.
3) Python tutorials can be found at https://docs.python.org/3/tutorial/ and documentation
for Spyder at https://pythonhosted.org/spyder/.
4) Codecademy may also be useful: https://www.codecademy.com/.
5) Insightful and informative tutorials on linear algebra can be found at
https://m.youtube.com/playlist?list=PLZHQObOWTQDPD3MizzM2xVFitgF8hE_ab
published by 3Blue1Brown.
Requirements:
1) A laptop (preferably), a desktop, or a like device that is network-enabled, webcam.
2) Install Python 3 and an IDE (integrated development environment) on your computer.
If you run Windows, install the Anaconda distribution of Python. You can download
and install it from https://anaconda.org/anaconda/python-editor. Anaconda comes with
Spyder, https://www.anaconda.com/products/individual, the IDE that we will use in
this class. Make sure that when you install Anaconda (or alternative) it is for version 3
of Python, not version 2.
Course Credits: Three (3-0)
Prerequisites: MATH 308 and ENGR 112; pre- or co-requisite: MEEN 210
MEEN 357 Syllabus Aug 19, 2020
Mid-Term Exam: Oct 13, 2020, 11:30am - 12:45pm via Zoom
Final Exam: Dec 1, 2020, 11:00am - 1:30pm via Zoom

2. Course Description
This course provides a practical foundation for the use of numerical methods to solve engineering
problems. The topics studied in this course are: solving systems of linear equations, curve fitting
and root finding, numerical integration and differentiation, initial value and two-point boundary
value problems, plus eigenvalues and optimization methods. We will study these techniques
mathematically, develop numerical approximations for them, and apply them to solve engineering
problems. Personal computers are used extensively in this course. Students are required to program
these numerical analysis techniques, which will be programmed from scratch, even if there exists
the implementation of these techniques in the extensive Python standard library,
https://docs.python.org/3/library/index.html or in the numerous third-party libraries, for example,
https://wiki.python.org/moin/UsefulModules.
Python is the programming language that we will use in this class. It is the fastest growing
programming language in the World today, and as of this year, is being taught in freshman
engineering. Spyder is the recommended IDE, and it is installed on the computers in the MEEN
Computer Lab. No previous knowledge of programming, in general, or of Python, in particular, is
required. Nevertheless, students are expected to become proficient in the use of this tool by the
end of the semester. This typically requires a great deal of self-learning on the student's part, which
is why self-help tutorials are so important.

3. Learning Outcomes
1) Gain programming confidence. Computers are the most widely used tool in engineering.
a) Basic programming (data structures, conditionals, loops, input checks)
b) Reporting (generating plots, tables)
c) Use of integrated development environments (IDE) like Spyder and advanced libraries
d) Overcome threshold of Python’s learning curve (preparation for future courses)
2) Develop a foundational understanding and experience in numerical analysis
a) Solving linear algebraic systems of equations
b) Curve fitting and roots of equations
c) Integration and differentiation
d) First- and second-order differential equations
e) Eigenvalues and optimization
3) Design programs and select appropriate method(s) to solve a given physical or engineering
problems while considering:
a) Finite precision (numerical error)
b) Finite memory (accuracy, convergence)
c) Finite processing speed (number of operations)
4) Practice proper programming techniques. You will seldom if ever be a ‘Lone-Ranger’ (sole-
developer, sole-user). To work in this collaborative arena, you will need to become
knowledgeable in the areas of:
a) Design of programs, algorithms and their interfaces
b) Construction of structures (data, subroutines, functions, testing routines)
c) Commenting, useful variable naming

MEEN 357 Syllabus Aug 19, 2020

5) Gain experience applying numerical techniques to solve engineering design problems.
Ultimately, our motivation for this entire course is to help you solve engineering problems by
using numerical techniques, and thereby enable you to design engineered systems more
efficiently and more effectively.
a) Learn to relate physical situations, mathematical models, and numerical solution
techniques
b) Learn to solve/approximate calculus-based problems using algebraic techniques
c) Learn the tools necessary to formulate and solve design-refinement problems using, e.g.,
optimization techniques

Lecture: All lectures will be synchronous via Zoom. Please attend the lectures at the
designated time via Zoom. All lectures will be recorded and posted on eCampus.

Assessments: Your progress toward achieving the learning outcomes will be assessed in the
following ways. These pertain to ABET objectives (see below):
• Regular homework assignments (approximately one per each week) involving hand
calculations, programming and running code, and writing reports. Individual efforts.
• A mid-term exam assessing your grasp of the fundamentals of the methods taught.
Individual effort, closed book, but with a one-sided cheat sheet and a calculator. The
exam will be made available on eCampus. It will be done during the regular class hour
(11:30am-12:45pm). The exam will be proctored via a two-way system: you are
required to prepare a Zoom-enabled computer (with webcam) and a smartphone so that
the proctor can monitor you during the exam. You are required to prepare your own
blank papers for your solution. Once done, you need to scan (or take photos of) the
solution and post them on eCampus.
• Comprehensive final examination for the course, aimed primarily at assessing the
student’s understanding of the fundamentals. Individual effort, closed book, but with a
double-sided cheat sheet and a calculator. The exam will be made available on
eCampus. It will be done during the University-approved final exam date. The exam
will be proctored via a two-way system: you are required to prepare a Zoom-enabled
computer (with webcam) and a smartphone so that the proctor can monitor you during
the exam. You are required to prepare your own blank papers for your solution. Once
done, you need to scan (or take photos of) the solution and post them on eCampus.

4. General Expectations
What you can expect from us:
• To make sure that the homework and exams will be graded within two weeks
• To come prepared to class
• To treat you with respect
• To begin and end the class on time
• To admit to not knowing something, but to search for an answer promptly
• To make myself available to you for both course and career advice
• To maintain confidentiality concerning your performance
• To assign a grade that will reflect the quality of your work and nothing else
• To be honest with you
• To enforce the Aggie Honor Code
MEEN 357 Syllabus Aug 19, 2020
What we expect from you:
• To be willing to learn both numerical methods and their implementation into Python
code
• To treat everyone in the class with respect
• To do your work on time
• To accept that previous academic preparation (e.g., mathematics, lower engineering
courses) will affect your performance in this course
• To realize your perception of effort is not enough to justify a good grade
• To understand that a program which does not function properly is wrong, no matter
how small a mistake that causes the problem, even if it is only one keystroke
• To comply with the Aggie Honor Code

5. Topics Covered
The following is a tentative lecture schedule. The actual schedule may deviate from this posting
depending on class dynamics and how instruction progresses throughout the semester.

Lectures 01 (08/20) and 02 (08/25) Course overview: Introduction and Error analysis
Lectures 03 (08/27) and 04 (09/01) Programming basics: Spyder and Python (Chp. 1); HW 1 is
due
Lectures 05 (09/03) and 06 (09/08) Simultaneous linear algebraic equations: review of linear
algebra and Gauss elimination (Chp. 2); HW 2 is due
Lectures 07 (09/10) and 08 (09/15) Simultaneous linear algebraic equations, continued: LU and
Choleski matrix decomposition, pivoting and matrix
inversion (Chp. 2); HW 3 is due
Lectures 09 (09/17) and 10 (09/22) Curve fitting: interpolation, splines and regression (Chp. 3);
HW 4 is due
Lectures 11 (09/24) and 12 (09/29) Root finding: bisection, Ridder and Newton-Raphson
methods (Chp. 4); team adjustments; HW 5 is due
Lectures 13 (10/01) and 14 (10/06) Numerical differentiation: finite-difference methods,
Richardson extrapolation and derivatives of analytic
functions (Chp. 5 and handouts); HW 6 is due
No Class (10/08) Mid-term Exam
Mid-Term Exam (10/13)
Lectures 15 (10/15) and 16 (10/20) Numerical Integration: Newton-Cotes methods, Romberg,
Gaussian and Gauss-Kronrod integration methods (Chp. 6);
mid-term exam
Lectures 17 (10/22) and 18 (10/27) Numerical ODEs: Euler’s methods, Heun’s method, PECE
methods and Runge-Kutta methods (Chp. 7)
Lectures 19 (10/29) and 20 (11/03) Numerical ODEs, continued: error, stability and stiffness in
ODEs, and DIRK & IRKS implicit methods (Chp. 7); HW 7
is due
Lectures 21 (11/05) and 22 (11/10) Higher-Order ODEs: Methods of Newmark and Freed that
solve M!!x + C!x + Kx = f (t)
Boundary-Value Problems: the shooting method (handouts,
Chp. 8); HW 8 is due

MEEN 357 Syllabus Aug 19, 2020

 Lectures 23 (11/12) and 24 (11/17) Boundary-Value Problems: Finite Difference Method
Eigenvalues: Jacobi’s method; Optimization: linear method
(Chps. 8 and 9); HW 9 is due
Lectures 25 (11/19) and 24 (11/24) Optimization: Linear method (Chp. 10); review; HW 10 is
due
Final Exam (12/01) Final Exam

6. Course Grading Policy

Grade Allocation
Homework 500 points Programming assignments to be coded in Python, except for HW 1
which is a get-to-know-you assignment. A grading script will be
used to run programs you will write for these homework
assignments. Each assignment will be worth 50 points
Midterm 200 points There will be one midterm exam scheduled on July 01, 2020,
Exam covering Lectures 1 through 14, including programming.
Final 250 points Comprehensive closed book exam.
Exam
Attendance 50 points There are total 25 lectures. Attendance for each lecture is worth
3pts. Attendance score will max out at 50pts.
Total 1000 points Subject to change if the above constituents change

Final Grade Calculation

Two final grades will be calculated for each student. You will receive the higher of these two
grades as your overall course grade.
1. The first grade will come from percentage point:
A >= 90%, 80% <= B < 90%, 70% <= C < 80%, 60% <= D < 70% and F<60%.
Fractional parts will be rounded up, e.g., 699.33 would be rounded up to 700 points;
however, 699 will not be rounded up.
2. The second grade will come from a curve where grades will be assigned by your rank-
order with your peers:
A’s for the top 30% of the class, B’s for the next 40% of the class, C’s for the next
25% of the class, D’s and F’s for the bottom 5% of the class. Q drops are taken out
of the F’s in this grading scheme.
The percentage point grade is all about the points you earned. The curve grade is all about
your rank in class.

Grading on Programming Tasks

In programming, small mistakes matter a great deal. Something as seemingly innocuous as a
misspelling or a forgotten punctuation mark can cause your code not to execute properly.
Debugging is a part of proper programming practice, and it is expected that you debug your code
fully prior to submission. Because you can run your program and observe whether it is correct
prior to making your submission, there is no excuse for submitting buggy code.
Naming conventions for your script file, including the functions they import and export, are all
strictly enforced in each homework assignment.

MEEN 357 Syllabus Aug 19, 2020

If your code does not run according to the assigned specifications, it is wrong! This could be for
something as insidious as a single character typo.
The instructors will provide the students with the grading rubric used for each assignment after the
grades have been issued (ideally one week after the due date). This feedback tool will allow
students to figure out what they did wrong, and to aid them in determining why they received the
points they did.

Partial Credit on Tasks

The following guidelines will be used to assign partial credit to each homework task:
• 100% of value if: the grading script executes, the output is correct, the figures are correctly
labeled, etc., i.e., the output is in accordance to the assignment
• 75% of value if: the grading script executes and the results are correct, but these results are
not displayed, as specified by the assignment
• 50% of value if: the grading script executes, but the output is partially wrong
• 25% of value if: the grading script executes, but the output is completely wrong
• 0% of value if: the grading script does not run (i.e., it crashes) when calling the student’s
functions, etc., as specified by the assignment

Grade Disputes
Under rare circumstances, your professors will make mistakes in the performance of their duties.
We are, after all, human. It is also possible in programming that a very small mistake will cause a
very large error in your results. If you believe that the grade you received is an inaccurate reflection
of the credit you deserve, you may submit your assignment for reevaluation. (Effort does not
equate with grade expectation!) However, you must do this within ONE WEEK of when the
assignments were returned to you. Keep in mind, if the submitted code did not run on the
instructor's machine, you lose 100% of its value—this is not negotiable. The full grade dispute
procedure is outlined below.
Grade Dispute Procedure:
1) Create a cover sheet with the following information: your name, the current date, the
number/name of the homework/exam, the submission due date, the date it was originally
returned to you, your original score, and what you believe your score should have been. Below
this information, provide a concise, well-reasoned explanation for your claim. (We will use the
code you originally submitted for grading, if pertinent.)
2) Return the homework/exam along with this written explanation to the instructor via email. This
must be submitted to your professor within one week of it being returned. Later submissions
will not be accepted.
3) Re-grading: The instructor will re-grade the assignment and return it to you within two weeks.
4) Special note for final exam: Final exams will not be returned to you, obviously. If for some
reason you believe your final exam was graded incorrectly, you must see the instructor (in
person via Zoom) within one month of the exam date. No grade changes will be made after
this point, and the exams will be disposed of at this time.

Missed & Late Assignments

Missed and late assignments count as ZERO in your grade, except in the case of University
approved absences (see below). Any deviation from the general policy will be stated in the handout

MEEN 357 Syllabus Aug 19, 2020

for the affected assignment. The submission policy stated in a handout overrides the general policy
specified in this document. University policies are always in effect.

Class Attendance and Participation

You are required to attend all scheduled lectures. Failing to attend the lectures will reduce your
odds of being successful in this course by a considerable amount. Attendance will be checked by
the participant list in Zoom at the end of each lecture. Therefore, it is important that you remain
online when the class ends. It is also important that your name in the list should be identifiable.
Please use “Last Name, First Name” when you log in the Zoom. The attendance will be 5% of
your point grade.

University-Excused Absences
Work missed due to absences will only be excused for University-approved activities in
accordance with Texas A&M University Student Rules (see http://student-rules.tamu.edu/rule07).
Specific arrangements for make-up work in such instances will be handled on a case-by-case basis.
Please be aware that in this class any “injury or illness that is too severe or contagious for the
student to attend class” will require “a medical confirmation note from his or her medical provider”
even if the absence is for less than 3 days (see 7.1.6.2 Injury or illness less than three days).

7. Course Policy on Collaboration

It is common for students to become stuck on some aspect of an assignment, despite their
understanding of the concepts being implemented. When computer code is involved, one small
detail can make an entire program fail to run. Thus, students will naturally be inclined to share tips
and tricks as they do their assignments.
Rather than trying to stifle this interaction, we want to encourage it. From our perspective, a student
will learn far more if they receive a small tip that enables them to complete an assignment than
they would by leaving the assignment incomplete. Since our primary concern is learning, we see
this type of collaborative interaction as healthy and desirable. Furthermore, it parallels the real
world, where you will collaborate with teams of engineers (not to mention scientists, managers,
marketers, lawyers, etc.).
Naturally, there must be limits to how much you are permitted to help one another. The general
rule of thumb for this course is that the work you submit must be your own, but it is acceptable for
you to receive tips from others on how to complete the work. Examples of permissible
collaboration include:
• Discussing general strategies for solving a problem
• Discussing in any way the methods and techniques presented in lecture, provided you
do not solve a specific assigned problem in the process
• Pointing fellow students to useful websites and other references
• Discussing how to interpret results
Examples of behavior that is not permissible (and possibly to be considered as academic
misconduct):
• Copying code or any part of an electronic document from another student
• Debugging your friend’s code
• Solving a problem together and then submitting two copies of the solution

MEEN 357 Syllabus Aug 19, 2020

If collaboration took place, you must submit a statement listing the students with whom you
collaborated, and what you learned from them or helped them with. This will help avoid confusion
and protect you against incorrect accusations of academic misconduct.
Since this course is an online course, students don’t have chances to meet other students, thus no
opportunities for collaboration. Therefore, students’ name and email addresses will be available
on eCampus. Please keep the size of the collaboration as small as possible (e.g., 2-3). In addition,
discussion forum is available on eCampus for discussion.

8. Course Policy on Academic Misconduct

Academic misconduct WILL NOT BE TOLERATED. According to the Aggie Honor System
Office, academic misconduct (http://aggiehonor.tamu.edu/Student%20Rules/definitions.html)
includes cheating, fabrication, falsification, multiple submissions (same work in multiple classes)
and plagiarism.
Academic misconduct will be dealt with according to University regulations. Any incidence of
academic misconduct will result in a ZERO on corresponding assignment or exam, and your
name will be reported to the Aggie Honor System Office. A second occurrence will result in
your receiving an F in the course and an “Honor Violation Probation”.

Collaboration versus Academic Misconduct

Collaboration involves an exchange of ideas rather than an exchange of work. It is common for
students to become stuck on an assignment despite being able to do most of it. It IS NOT
misconduct to receive tips and help on small portions of an assignment. However, it IS misconduct
to submit someone else’s work as your own.
Aggie Honor Code “An Aggie does not lie, cheat, or steal, or tolerate those who do.” It is the
responsibility of students and instructors to help maintain scholastic integrity at the university by
refusing to participate in or tolerate scholastic dishonesty. Conduct contradicting to this policy will
be punished according to the current rules and regulations. For details, see
http://aggiehonor.tamu.edu.

9. Course Policy Regarding Disabilities

The Americans with Disabilities Act (ADA) is a federal anti-discrimination statute that provides
comprehensive civil rights protection for persons with disabilities. Among other things, this
legislation requires that all students with disabilities be guaranteed a learning environment that
provides for reasonable accommodation of their disabilities. If you believe you have a disability
mandating an accommodation, please contact Disability Services. For additional information visit
http://disability.tamu.edu.

10. ABET Student Outcomes

The program must have documented student outcomes that prepare graduates to attain the program
educational objectives. For 2017 and beyond, those outcomes that pertain to MEEN 357 are:
a.) An ability to select and apply the knowledge, techniques, skills, and modern tools of the
discipline to broadly-defined engineering technology activities;
b.) An ability to select and apply a knowledge of mathematics, science, engineering, and
technology to engineering technology problems that require the application of principles
and applied procedures or methodologies;

MEEN 357 Syllabus Aug 19, 2020

 c.) An ability to conduct standard tests and measurements; to conduct, analyze, and interpret
experiments; and to apply experimental results to improve processes;
d.) An ability to design systems, components, or processes for broadly-defined engineering
technology problems appropriate to program educational objectives;
e.) An ability to function effectively as a member or leader on a technical team;
f.) An ability to identify, analyze, and solve broadly-defined engineering technology problems;
g.) An ability to apply written, oral, and graphical communication in both technical and non-
technical environments; and an ability to identify and use appropriate technical literature;
h.) An understanding of the need for and an ability to engage in self-directed continuing
professional development;
i.) An understanding of and a commitment to address professional and ethical responsibilities
including a respect for diversity;
j.) A knowledge of the impact of engineering technology solutions in a societal and global
context; and
k.) A commitment to quality, timeliness, and continuous improvement.

MEEN 357 Syllabus Aug 19, 2020