MIT (Fall 2008)   18.385  Rosales.

============================================================================
 Policies regarding homeworks, PLEASE READ THEM:

 As you know (from the syllabus), the problem sets will count for 20% of the
grade.  There will be about 8 of them (one per 1-2 week, more or less, except
when a test is due).

 A) COLLABORATION:  It is OK to exchange information with other students, in
    the sense of hints,  general ideas,  pitfalls to avoid and so on;  i.e.:
    "within reason" ---- "let me see/copy" your answer is not within reason.
    But, the final answer must be written 100% alone,  with understanding of
    every dot that goes in there.

    WARNING: ****************************************************************
    * The collaboration policy above applies ONLY to problem sets.          *
    * For take-home EXAMS (if any), the policy is 100% alone,               *
    * the only allowed consultations being with the Lecturer and TA.        *
    *************************************************************************

    WARNING: ****************************************************************
    * You are 100% responsible for any answer you supply, in either problem *
    * sets or exams, and I can call you any time to explain your answer. If *
    * I am not convinced that you understand what you wrote, you will loose *
    * credit,  up to and including loosing credit for the whole problem set *
    * (or exam) --- this depending on the degree of lack of understanding.  *
    *************************************************************************

 B) WARNING-WARNING-WARNING-WARNING-WARNING--CLARITY:
    ************************************************************************
    Your answers must be presented in a way that is easy to read. Type them
    (12 point)  or, if by hand, write clearly, use a LARGE enough font, and
    HIGH contrast ink or pencil.   The lecturer has serious trouble reading
    stuff not following these simple guidelines. Problem sets & exams (take
    home exams specially) that fail them may NOT be graded,  with NO credit
    given.

    For that matter, this being a graduate student level course: graduate
    student level of explanations will be expected. To get full credit, the
    arguments have to be clear, complete, and in reasonably good English.

    As for the level of rigor:  "Math. proof level" is not expected. The
    same  level as in the lectures, book, or notes ("reasonable scientist")
    is the expectation.
    ************************************************************************

 C) The TA will grade 5 problems in each set (from the assigned problems ---
    selected randomly), but answers will be provided for all. Please, do all
    the problems, since if you just happen to miss the ones picked, you will
    get no credit (even if you did all the others).  Also: it's the only way
    to "really" learn.
    The reason for this policy is to avoid in-a-hurry type of grading by the
    TA. I expect that by looking at just a few problems, the TA will be able
    to do a bang-up job with the grading.

 D) Answers to all the problems will be provided [hopefully very shortly
    after each set is due].

 E) The "suggested reading", "suggested problems"  and any other "suggested" 
    are for you alone to do or not do.  Thus: DO NOT hand in these problems!
    I recommend that you do as much as possible of this. 


 F) About COMPUTER ASSIGNMENTS (if any):

    a) Use any language or computer you like.  Athena accounts are available
       to all students.      I recommend the use of software like MacMath or
       Phaser if you have a home computer; it'll simplify your life.  Better
       yet: get the Student Edition of MatLab,  and port the Course Software
       there.

       In Athena you can find "dstool", but it's harder to use.    MatLab or
       Mathematica are easier to use and more flexible.  You can also use C,
       FORTRAN or whatever works for you.

    b) Include a BRIEF explanation of how the problem was solved (a printout
       of a program is really not enough!). WHAT is the IDEA!

    c) Results must be CONDENSED to some COMPREHENSIBLE and CONCISE form:
       * Use plots, tables or graphs. Do not show "raw" numerical output.
       * Make sure one does not have to hunt for the answers all over the
         place.  They must be EASY to find and identify.  Put them at the 
         beginning, for example, and then justify them.

    e) Include a printout of your program appended (AT THE END) --- if there
       is one.  If you used MacMath, Phaser or something like that, just say
       that and SPELL the numerical parameters and other such data used  ---
       these things usually give you a choice of time step, numerical method,
       etc. Do not trust the defaults!

    f) Look at your output and make very sure it makes sense! That a program
       "runs" does not mean it does so as intended.  For example, if you are
       using too large a time step, you will still get some output ... which
       can easily be nonsense!

===========================================================================
%
%% EOF