Sie sind auf Seite 1von 8

ENG006 ENGINEERING PROBLEM SOLVING LECTURE: Tu & Th 9 am - 10:20 am 2205 Haring Hall LABS: 1116 Academic Surge and

1044 Academic Surge INSTRUCTORS:

Lecture: 3 hours; Lab:1 hour.

1. Rajeevan Amirtharajah, Professor, Electrical and Computer Engineering Email: ramirtha@ece.ucdavis.edu Office Hour: Monday, 4-5 pm Office Location: 3087 Kemper Hall 2. Brian Kolner, Professor, Electrical and Computer Engineering Email: bhkolner@ucdavis.edu Office Hour: Friday, 10-11 AM Office Location: 3047 Ghausi Hall
COURSE CONTENT: Methodology for solving engineering problems. Engineering computing and visualization based on MATLAB. Engineering examples and applications. COURSE OBJECTIVES: Learn to think logically to solve engineering problems Become comfortable programming in the Matlab language Gain design experience Master the computer skills necessary for modern engineers RECOMMENDED STUDY METHODS: The expectation for a typical 4-unit course is for students to spend approximately 3-4 hours per week on the initial presentation of the course material and an additional 8-12 hours studying, doing homework, writing papers, etc. (Obviously some courses take less time while others take more.) You should therefore plan your time accordingly. In this course your time should be spent reviewing material presented in class, preparing for labs (i.e. studying the assigned material, and completing the prelabs/homework assignments) and working on assigned projects. A very large part of computer programming is practicing writing scripts. Once the fundamentals are mastered, which is the purpose of the labs, increasingly complex problems can be tackled (i.e. why there are two project assignments). PREREQUISITE: Mathematics 16B or 21B (may be taken concurrently with Engineering 6); prior programming experience is not required. TEXTBOOK: i) Matlab Core Techniques (Download from SmartSite) ii) MATLAB: An Introduction with Applications, 4th Edition by Amos Gilat (available in UC Davis Bookstore)

ISBN 978-0-470-76785-6 Wiley REQUIRED MATLAB SOFTWARE: (available in UC Davis Bookstore) MATLAB & Simulink Student Version Release 2010a ISBN-13 978-0-9825838-0-7 Consult www.mathworks.com/support for installation support. COURSE GRADE BREAKDOWN: Homework/Labs: 40% of total grade (lowest grade in lab will be dropped). Project #1: 5% of total grade Project #2: 25% of total grade Final: 30% of total grade GRADING OF HOMEWORK/LABS: The grade for weekly homeworks and labs will be combined into one grade. The homework will count 40% of the total weekly grade, and the lab will count 60% of the total weekly grade. If you do not submit the homework for the week, you will receive a zero for the homework, and the maximum grade that you will be able to achieve is 50% of the total lab grade TEACHING ASSISTANTS: 1. Hsu, Stanley (Lab Sections A01: Tuesday 11-12 & A06: Tuesday 12-1) Email: swhsu@ucdavis.edu Office Hour: Thursday 1-2 pm Office Location: Academic Surge 1116 2. Mamidanna, Manish (Lab Sections A07: Thursday 12-1 & A08: Tuesday 5-6) Email: mmamidanna@ucdavis.edu Office Hour: Wednesday 2-3 pm Office Location: Academic Surge 1044 3. Pham, Binh (Lab Sections A02: Thursday 11-12 & A09: Thursday 5-6) Email: blpham@ucdavis.edu Office Hour: Monday 2-3 pm Office Location: Academic Surge 1116 4. Sereshki, Saeed Bagheri (Lab Sections A03: Tuesday 1-2, A11: Wednesday 5-6, & A10: Wednesday 6-7) Email: sabagheri@ucdavis.edu Office Hour: Tuesday, 6-7 pm Office Location: Academic Surge 1116 5. Ferdousi, Sifat (Lab Sections A04 Wednesday 5-6 & A05: Wednesday 1-2) Email: sferdousi@ucdavis.edu

Office Hour: Friday 1-2 pm Office Location: Academic Surge 1116 HOMEWORK All work must be done individually. On each homework, write your name, lab section number, and problem set number clearly at the top. Homeworks are assigned weekly and the deadline is strictly enforced by Smartsite. They will normally be due 30 minutes before the first lecture of the week, i.e. 8:30 AM on Tuesdays. It is the responsibility of the student to verify work has been correctly uploaded into Smartsite. There are ways things can go wrong, so always verify your submissions. Unfortunately, late homeworks cannot be accepted except for verifiable medical excuses approved by the instructor. Homework sub-problems are normally graded on the following scale: 0 Little attempt made 1 Not fully built 2 All there, but not working 3 Just about correct 4 Totally correct Simple sub-problems will be graded on the following scale: 0 Not a full effort 1 Close but fundamental problem 2 Correct Solutions to Homework problems will be provided ASSESSMENT PORTION OF EACH WEEKLY LAB: Attendance in lab is required Typically, much of each in-lab assessment will cover material from the previous week's two lectures in addition to material covered by the previous homework. You may ONLY use the following material to complete your lab, 1) online help documentation that comes with Matlab, and 2) your own homework solution. You may NOT use any other material including lectures, textbook, and any other online resources. You may NOT communicate with anyone and should not have anything other than the Matlab environment on your screen. During the lab you may NOT access the internet, except to submit the work on SmartSite when you are finished. It is the responsibility of the student to verify work has been correctly uploaded into Smartsite. There are ways things can go wrong, so always verify your submissions. Lab grades will be adjusted so the average grade for each lab section is the same. For several logistical reasons, you may attend only the section in which you are enrolled. In general, you are free to use the lab anytime another course is not using the room according to EACS posted hours. Example lab solutions will be posted after the completion of the final lab section each week. Each lab session has three major components: 1) the programming problem, 2) a brief lecture by the TA, and 3) time for group and individual questions. Lab programming sub-problems are normally graded on the following scale: 0 Little attempt made 1 Not fully built 2 All there, but not working 3 Just about correct 4 Totally correct Simple sub-problems will be graded on the following scale:

0 Not a full effort 1 Close but fundamental problem 2 Correct Solutions to all lab problems will NOT be provided.

FINAL EXAM: The final exam is a mandatory component of this course. It is designed to test a working knowledge and understanding of concepts, not just mechanical procedures. Unfortunately, no early or late exams are possible. If an unavoidable emergency prevents your attendance at the final, you will be required to submit written proof of the emergency and the make-up exam will likely be given as an oral exam with the instructor. The final exam will emphasize the programming concepts of Matlab. The final is closed book. No collaboration, notes, calculators, or aids are permitted for exams. COURSE POLICIES Getting your questions answered: i) Questions to which you need a quick answer: A SmartSite ENG06 chat room has been created for asking questions from your fellow class students. Please use courteous and professional language in online discussions. ii) Technical questions: If you need assistance on topics related to technical aspects of the course: a. You are strongly encouraged to ask as many questions needed during lecture time. b. Post the question on the SmartSite ENG06 forum: The forum will be checked daily. Between 9 am and 5 pm, you can expect a response time of no more than 3 hours. A good faith effort will be made to provide a written answer, however you may be directed to one of the office hours of the teaching assistants. c. Teaching Assistant office hours: There is a teaching assistant office hour on every day. If you have specific questions about what you need to do for the prelab in your section, you are encouraged to seek the assistance from your lab teaching assistant. d. Instructor office hours: If you have exhausted the above mechanisms, finally there is instructor office hour. Even with the regular office hour set, it is a good idea to contact the instructor beforehand to set up a time. In those rare instances the instructor may not be available during the office hour, an alternate time will be scheduled. e. DO NOT E-MAIL TECHNICAL QUESTIONS DIRECTLY TO THE INSTRUCTORS OR TEACHING ASSISTANTS. IT WILL BE MOST LIKELY IGNORED. iii) Other questions: Questions that do not fall under above categories should be directed to head TA Stanley Hsu. He will contact the instructors if the need arises. Personal Identification: You must have your UC ID Card with you during all labs and the final, and must be prepared to show it to either the instructors or teaching assistants. Late Submissions or Failure to Attend Lab: No late work will be accepted. It is up to the student to ensure that materials submitted online via SmartSite are uploaded correctly by the deadline. When the submission has been completed correctly, you should receive an email confirmation from SmartSite with a unique ID. This email is the only acceptable proof of correct submission. Absences or tardiness for a lab or project deadline will result in automatic failure of that project, except in the case of documented

medical or family emergencies. Valid medical excuses are documented unpredictable events that in spite of good planning on the part of the student, make the student unable to complete the work or attend class meetings. A non-specific note from the Health Center is not a valid excuse. You need to bring a statement from an MD, a Registered Nurse, or a qualified Counselor clearly stating that you were in no condition to attend a class meeting or complete the work. The date and time when the student suffered the condition must also be written on the note. The faculty in charge is the only person who has authority to decide if an excuse is valid. Consideration of an excuse will always require a written document. The final will be held during your regularly scheduled and assigned period. Grading Errors: Clear and significant grading errors should be described and justified in writing and given to the teaching assistant within a week of assignments being returned. Due to the inherent subjectiveness of grading and to be fair to all students, only truly significant (as determined by the TA and/or instructor only) grading mistakes will result in a grade change. In addition to the description of the suspected grading error, you must write the following on your regrade request and sign immediately below it. "I certify that I have not altered this work in any way after it was returned to me. I understand that such altering would constitute a violation of the Code of Academic Conduct." POLICY ON COLLABORATION In this course, all work must be done "individually"meaning done entirely by the student whose name is on the work. However, asking other students conceptual questions and explaining high-level concepts are important steps in the learning process and are strongly encouraged. This is very different from giving or receiving aid related to a specific assigned problem--which is not permitted. Copying someone else's work or allowing your work to be copied in any setting (homework, lab, exams,...) does not promote learning, is unfair to honest students, and will be reported to Student Judicial Affairs. Students that observe inappropriate activity should report what they see (anonymously if desired) to a TA or the instructor. Encouraged collaboration: The following are encouraged and are allowed at all times. Discussing material covered in lecture, or the readings. Discussing the requirements of an assignment. Discussing features of the languages, tools, and libraries used in the class. Discussing general concepts of designing, coding, or debugging. Encouraged example statements/exchanges include, o "It worked well to test each module independently before assembling the whole system" o "When something doesn't work right, first look at all input signals in the waveform viewer." o "Why doesn't matlab let me use an index of 0 in an array?" Any discussion between you and the teaching assistants and instructors. You are welcome to discuss any and all ideas, design, code, debugging, and details with the instructor. Permitted collaboration, but only if documented: When you engage in more detailed discussions of assignments, you must include the name of the person(s) who assisted you and properly credit their contribution to your work. This is akin to acknowledging a reference in a research paper. These cases include: Discussing more detailed concepts of designing, coding, or debugging. Some example exchanges requiring citation are: o "I can't get test cases with a negative input to work."

"Did you check the sign extension of the subtracted input?"

Unpermitted collaboration: The overall guideline for unpermitted collaboration is that you must submit work that represents your original, independent effort. It should not be based on, influenced by, or copied from anyone else's work--including people not enrolled in the course. Copying code. This is the most blatant violation. You should not be writing down anyone else's work, or allowing anyone else to write down your work. Using work from past quarters. Using someone's work or solutions from a previous quarter is an obvious violation. Looking at someone else's work. You should never read anyone else's work before yours is submitted, whether it is on the screen or written out by hand. Debugging with another person. Working at the same computer as someone and trying to fix a bug is not allowed. It makes it too easy to look over someone else's code, and allows (sometimes unintended) code-copying. Describing to someone your problem and asking for advice on how to fix it is okay, but you should do the actual debugging yourself. Copying someone else's high-level design. Discussing high-level design with someone else and sharing ideas and critiquing each other's design is okay if attributed. However, just taking someone else's design is not allowed. It is akin to taking someone else's outline for a research paper and basing your paper on that. Discussing assignments in such detail that you duplicate a portion of someone else's work in your own design.

ALL violations of the above collaboration policy will be prosecuted as per UC Davis' Academic Integrity Policy. Sanctions include failure of the course and suspension/expulsion from the university.

LECTURE SCHEDULE: Week #1: Matlab Environment, Fundamental Operations & Scripts Lecture #1 January 8: Lecture #2 - January 10: Week #2: Vector/1D Arrays Lecture #3 - January 15 Lecture #4 - January 17 Week #3: Matrix/2D Arrays (Monday Martin Luther King, Jr. Day) Lecture #5 - January 22 Lecture #6 January 24 Week #4: Flow Control Lecture #7 January 29 Lecture #8 - January 31 Week #5: Custom Functions Lecture #9- February 5 Lecture #10 - February 7 Week #6 Lecture #11 - February 12 Lecture #12 - February 16 Week #7 Lecture #13 - February 19 Lecture #14 - February 21 Week #8 Lab #1: Introduction and walkthrough with teaching assistant Introduction & Scripts Built-in functions, I/O, Logical expressions, ii) Array I iii) Lab Theme Discussion Lab #2: 1-D array Array II Array III + Plotting & Elementary Data Import Lab #3: 1-D and 2-D array Matrix Numerical Techniques + Image & Sound Flow Control I & II Part 1 i) Matlab Core Techniques Chapter 1 & 2 ii) Gilat Textbook Chapter 1 i) Matlab Core Techniques Chapter 3 ii) Textbook Chapter #2 & 3 i) Matlab Core Techniques Chapter 3 ii) Textbook Chapter #2 & 3 i) Matlab Core Techniques Chapter 3 ii) Textbook Chapter 5)

i) Matlab Core Techniques Chapter 4 & 5 ii) Textbook Chapter #6) Lab #4: 1-D and 2-D array, logic functions, flow control Flow Control I & II Part 2 & i) Matlab Core Techniques Custom Functions Chapter 6 ii) Textbook Chapter #7 Engineering Design Lab #5: 1-D and 2-D array, logic functions, flow control Interpolation and Data Fitting + Textbook Chapter #8 & Monte Carlo Computations Numerical Calculus & Solution Textbook: Chapter 8 & 9 in of Nonlinear Equations textbook Lab #6: 1-D and 2-D array, logic functions, flow control, custom functions Cell Arrays and Structures Data Import Advanced & GUI Lab #7: 1-D and 2-D array, logic functions, flow control, custom functions (Hardware Lab) String Manipulations Pattern Matching Lab #8: 1-D and 2-D array, logic

Matlab Core Techniques Chapter 7

Lecture #15 February 26 Lecture #16 February 28 Week #9 Lecture #17- March 5 Lecture #18 March 7 Week #10 Lecture #19 - March 12 Lecture #20 - March 14

functions, flow control, custom functions, GUI Pattern Matching Object Oriented Programming Lab #9: 1-D and 2-D array, logic functions, flow control, custom functions, GUI, Classes TBA TBA Lab #10: Final Project TBA TBA

Das könnte Ihnen auch gefallen