Instructor | Master Billy Oxford - william.oxford@nmt.edu |
Lecture |
Tues/Thurs 1:00-1:50pm Workman 101 |
Labs |
Section 01 Tue 2:00-4:30pm Speare 16 |
Grading |
50% Labs 40% Final Project 10% Attendance |
Attendance | You're a grown-up now...come to class if you feel like it. If you want to be successful, however, you should attend as many scheduled sessions as possible. Oh, did I mention attendance is 10% of your grade? You can drop a full letter grade by not showing up so definitely keep that in mind. |
Final Project |
Each student will choose a problem from a compiled list or use a problem of their own. An abstract describing the nature of your problem will be due Thursday, March 8th by 5pm. One point will be subtracted from your final average for every day your abstract is late (up to 10 points). The final project is due May 6th by midnight. Late submissions will not be accepted and a grade of zero will be assigned. Your final project will consist of a professionally formatted write-up (2-5 pages), plots and/or data tables, and code in the appendix. A sample project and list of topics will be available within the next few weeks. You are strongly encouraged to ask professors in your department for problems in your field that are solvable by someone at your level. If you are required to complete a project for another course you are welcome to “double dip” and submit that project in this class, as well...just be sure to incorporate the appropriate amount of coding in your write-up. If you are unsure if the amount of code is acceptable, please visit with me to determine whether your project meets the minimum requirements (this should also be addressed in your mid-semester abstract submission). |
book: | Matlab - A Practical Introduction to Programming and Problem Solving - 3rd Edition - Stormy Attaway |
or |
42% - Freshman29% - Sophomore13% - Junior16% - Senior |
15% - Super difficult70% - Everybody else15% - Super easy |
Good job finding a built-in function to accomplish a specific task...but do you know how it works? We want to learn how to write our own functions.
No, we will not get into OOP. No, we will not get into theory.
Sorry, but you have to take this course (some of you anyway)
Your needs are likely a bit different than others when it comes to programming. We are going to try and focus on the skills you need to solve problems in your chosen field.
I'm not joking.
"When you have the facts on your side, argue the facts. When you have the
law on your side, argue the law. When you have neither, holler."
You should be capable of solving most algorithmic problems you encounter.
There is a common foundation among most languages: logic, variables, loops, conditionals, etc
Out of ~71k undergraduates surveyed:
...animals, people, even well-designed machines will naturally choose the path of least resistance or "effort".
"In simple terms, the Principle of Least Effort means, for example, that a person in solving his immediate problems will view these against the background
of his future problems, as estimated by himself. Moreover, he will strive to solve his problems in such a way as to minimize the total work that he must expend
in solving both his immediate problems and his probable future problems. That in turn means that the person will strive to minimize the probable average rate of his
work-expenditure (over time). And in so doing he will be minimizing his effort...Least effort, therefore, is a variant of least work."
(George Kingsley Zipf, Human Behavior and the Principle of Least Effort: An Introduction to Human Ecology. Addison-Wesley Press, 1949)
or |
or |
or |