From EG1004 Lab Manual
Revision as of 02:24, 31 August 2022 by Admin (talk | contribs) (1003 --> 1004)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The course consists of a weekly one-hour lecture, three-hour lab, one-and-a-half-hour recitation, and a semester-long design project. A supervising faculty member, a team of TAs, and a writing consultant manage each section.

Common Lecture

There will be common lecture for all the EG1004 sections each week, usually held in Pfizer Auditorium. The lectures are delivered by NYU Polytechnic School of Engineering faculty or outside experts discussing topics of general interest in engineering and technical work in general. To help you fully appreciate the lecture, and be able to pay attention to the speaker, we will usually distribute handouts of the speaker's slides after each lecture. Attending lecture is mandatory as attendance counts toward your grade.


Two laboratory TAs supervise all lab work in your section. There is also a supervisory TA called a Roaming TA that will observe all lab sessions running during that time block and participate at their discretion. The three-hour weekly lab begins with a five minute quiz based on the lab manual and the previous lecture. You are expected to be fully familiar with the lab and what is required before you arrive, and the quizzes are a way to insure that you are ready to participate in the lab. After the quiz, your TA will proceed with a prepared briefing (usually a PowerPoint presentation). You will then perform the required lab work in teams following the guidelines in this manual and the instruction provided by your TA.

After the lab, you will prepare a lab report and a presentation. Each lab that appears later in this manual contains a section called called Your Assignment. Refer to this material before you begin your work. Your lab must be submitted electronically. Two pages in this manual will show you how to do this:

Your TAs will also review this with you.

There is a two week limit on late lab reports. Twenty points will be deducted for all or part of each week that your lab report is late. Lab reports that are more than two weeks past their due date will receive an automatic grade of zero.

A member of the grading committee will grade your lab reports for technical content, and your writing consultant will grade your lab report for style and use of the English language.

Your lab section will typically consist of up to nine teams of two students each, for a total of eighteen students per section. You will be assigned a team partner on a rotating basis, following industry practice where engineers and scientists are formed into large teams based on availability and technical expertise. You may not always like your assigned teammate, but like industry you will both be expected to put your personal feelings aside and operate as an effective team.


Your supervising faculty member, writing consultant, and Recitation TA will run your one-and-a-half-hour weekly recitation. The supervising faculty member will be in charge of this session. Your team will prepare a PowerPoint presentation describing the lab, which you will deliver as a team in front of the class. The instruction team will provide pointed criticism so that the entire class will be able to improve their skills. Periodically during the term, your project team will instead present progress information about your semester-long design project.

There is no lateness on presentations. Presentations will not be accepted after the start of the recitation.

The writing consultants (one per section) attend the recitation each week. In addition to grading your lab reports and being part of the team commenting on your presentation, they will present a 10-minute mini-lesson about how to write correctly and persuasively.

The recitation will typically start with some comments from the supervising faculty member and the mini-lesson delivered by the writing consultant. Next, the team lab presentations will be done by the students in the class. At scheduled points during the semester, students are required to present Milestone presentations where project progress reports are made. After the presentations are complete, the supervising faculty member may have some final comments.

Semester-Long Design Project

There is a semester-long design project that runs in parallel with the other activities in the course. The projects will be described at your first recitation. It's early in the term, and you won't know much of the technical detail required to complete the project, so it's best to choose a project that you find interesting. You'll get the tools needed to successfully complete the project as the term progresses. Typical projects are robots that overcome challenges, automatic routing using digital logic, and building construction. There is enough variety in the projects that everybody will find something interesting. At a later class you'll then be asked to choose a project you find interesting, frequently with a second choice. Based on the preferences of the class, you'll then be formed into project teams. These teams have no relation to the lab teams discussed earlier. You will work with the same project partner for the remainder of the semester. The project will involve technical work, plus the skills needed to manage a project successfully, including setting and managing to meet a schedule, and setting and maintaining a cost. You will be giving several milestone presentations during the semester, where you will report your technical progress, and also how you are doing on cost and schedule issues. A session during the last week of classes is reserved for your final project presentation. This presentation serves two purposes. First, it is the final "milestone" presentation describing how you ended up. Second, it is a marketing presentation explaining why a customer should want to buy your product instead of your competition's. Again, this is an important skill to learn. If a technical professional can't persuade a customer to buy their product they will go out of business, even if they have a superior technical solution.

Refer to the syllabus for project due dates.