tl;dr: Do NOT copy code, else grades will be lowered and we'll go to the COD

If you are a current student, please Log In for full access to the web site.

Note that this link will take you to an external site (

The primary goal of the labs and tutor problems is educational. We ask you to work through these exercises because we feel that the experience will cement the basic technical ideas and lead you to think about bigger conceptual issues. It is your responsibility to take advantage of the opportunity to do this; working too closely with others will rob you of the chance to engage deeply with the material and may lead to poorer understanding and, ultimately, worse performance on the exams.

We encourage students to discuss assignments in this subject with other students and with the teaching staff to better understand the concepts. However, there are limits to what you can do, to ensure that everybody has a good individual learning experience.

This page is designed to give you a sense of what kind of interactions are allowed, and which are not, when working on 6.08 coursework. The policies below are in place in order to help with our primary goal for the exercises (i.e., that you deepen your understanding of the course materials by working through them).

Regardless of the assignment, **you should never use results from other
students, nor from the staff**, in
preparing your solutions to online tutor problems. You should not take credit for computer code or graphics that
were generated by other students unless you developed those materials while
working with your lab partner.

In addition, **students should never share their solutions (or staff solutions)**
with other students, including through public code repositories such as Github.

You are expected to give your best effort and work as far as you can on your
own *for every exercise* before asking for help or using other resources. You
should spend **at least 10 minutes** working though each exercise before
consulting any external resources (including online resources, course staff, or
your fellow students).

If you are still stuck on a problem, you may talk about the question with a staff member or a fellow student, but all exchanges of information should be general in nature. See the sample interactions below for examples of what is considered okay, and what is inappropriate.

After having received help on an exercise and reaching a solution, you should wait a day or so, and then try to work through the exercise again from scratch on your own.

You will work with a partner in the labs. You and your partner can equally share all results, code, and graphs that you develop as a team.

You should work through the entirety of the lab *as a team* to produce one
result, and each partner should be prepared to discuss their results with a
staff member during a lab checkoff. A "divide-and-conquer" approach, where
each partner only works through a portion of the lab, is unacceptable.

When you have completed an exercise or an experiment, you should share your results with your partner. Each partner should enter tutor exercises on their own account, and by the end of the lab, each partner should have a copy of any results, code, and graphs that you developed as a team.

You will work with a partner (or partners) for the independent design project. You will jointly be responsible for all deliverables, including demos and presentations.

Incidents of plagiarism will result in a grade of zero on the assignment and,
at the discretion of the staff, may be reported to the Committee on Discipline
(COD). More information about what constitutes plagiarism can be found at

http://integrity.mit.edu/

Scenario: Alyssa and Ben sit down to work on a homework set together...

After trying a question on his own, Ben asks Alyssa for help. Alyssa asks Ben
a leading question that helps him discover a reasonable next step to take when
solving the problem.

**OKAY!**

After trying a question on his own, Ben asks Alyssa for help. Alyssa talks Ben
through some of the finer points of op-amps using a separate but related
example problem. Ben then tries to apply these ideas to the problem he was stuck on.

**OKAY!**

Alyssa notices that Ben is struggling with a problem, so she gives him her answer
and explains to him how she arrived at it.

**NOT OKAY**

After trying a question on his own, Ben asks Alyssa for help, and she explains
that it is easy: you just take equation 3.12 from this book, insert equations
2.5 and 3.2, integrate, and you should get the right answer!

**NOT OKAY**

After trying a question on his own, Ben asks Alyssa for help. Alyssa describes
in detail the steps she took to solve the problem.

**NOT OKAY**

Bob has access to a "bible" of 6.01 answers from previous terms, which he
consults when he gets stuck.

**NOT OKAY**

After having made reasonable efforts individually, Alyssa and Ben talk in
general terms about different approaches to doing a problem. They draw
diagrams on a whiteboard. When Alyssa discovers a useful Python structure, she
mentions it to Ben. When Ben makes an observation about op-amps, he shares it
with Alyssa.

**OKAY!**

As Alyssa and Ben type lines of code, they speak the code aloud to the other
person, to make sure they both have the right code.

*or...*

**NOT OKAY**

In a tricky part of the homework, Alyssa and Ben look at each other's screens
and compare them so that they can get their code right.

**NOT OKAY**

After they have both solved a problem, Alyssa and Ben talk in detail about the
approaches they took, and the relative merits/drawbacks of each.

**OKAY!**

Alyssa and Ben sit down to work on a homework set together. They decide to
divide up the problems: Alyssa will work through the even-numbered problems,
and Ben the odd-numbered ones. When they are done, they will discuss their
work with each-other so that each has a complete solution.

**NOT OKAY**

Scenario: Louis had a very busy week. He has already used his two automatic extensions and has made almost no progress on the week's problem set. Ben wants to help.

Ben works near Louis and answers his questions when they come up, after Louis
has made a reasonable effort.

**OKAY!**

Ben opens his laptop and consults his own code when helping Louis.

**NOT OKAY**

Ben has been helping Louis or a while, but he needs to get back to his own work.
He gives his code to Louis, after Louis promises only to look at it when he really has to.

**NOT OKAY**

This page was last updated on Saturday February 02, 2019 at 03:47:19 PM (revision

`445146c`

).\ / /\__/\ \__=( o_O )= (__________) |_ |_ |_ |_Course Site powered by CAT-SOOP 14.0.4.dev5.

CAT-SOOP is free/libre software, available under the terms

of the GNU Affero General Public License, version 3.

(Download Source Code)

CSS/stryling from the Outboxcraft library Beauter, licensed under MIT

Copyright 2017