CS 3723
Programming Languages  
Fall 2013
  Submission of Recitations  

Paperless Course: I will use email for electronic submission of recitations, to make do with less paper in this course. All work for recitations will be submitted by email, graded, and returned by email. The email address to use will be the first one below, where δοτ is a "dot" and ατ is an "at-sign":

    < nealδοτwagnerδοτextraατgmailδοτcom >
            (for all recitations and nothing else)

    < nealδοτwagnerατgmailδοτcom >
            (for everything else: questions, etc.)

Submission Requirements:
  • Subject Header in Email: Your header line for a submission should be: "R<i>, <your last name>", where "<i>" is the recitation number and "<your last name>" is your last name. Thus a student with last name "Hadrian" would use

      R0, Hadrian

    for their subject line of Recitation 0, and two students with last names "Claudius" and "Nero" would submit Recitation 3 with

      R3, Claudius, Nero

    as the subject line.

  • Individuals, or Teams of At Most Two: If you don't work by yourself, then a team of two (but never more than two) is allowed in this course. For two students to submit as a team, they must work together during one of the regular time slots for the week of the particular recitation. There are no other circumstances under which two students may submit a joint recitation. One of the students will submit the recitation by email, but both names must appear at the head of the submission. Both students must have signed up as a pair on the regular sign-in sheet.

      There will be no sign-in sheet and no required attendance at a recitation during the first two weeks because there are no Monday classes.

    The particular pairing into teams can change from week to week.

    Despite wanting to allow teams of two, I see negatives about such teams, since one member can do much or all of the work and get much or all of the benefit. This would show up on the exams. A team of three is much worse, and that's why I don't want to allow teams of three or more. I emphasize that working by yourself is always permitted.

  • Form of Submissions: I prefer submissions that are a single text file (.txt).   Absolutely no WORD or Zip files (no .doc, no .zip files), nothing created with Microsoft Wordpad, no Rich Text Format files (.rtf), and no binary files. HTML and PDF are OK, but I don't want a whole list of attached files that have to be opened one-by-one. If you work in Windows, you could use Notepad, but must be careful to save as "text only" (.txt).

    If you would normally want to submit several files, just concatenate them into one file. On Unix systems, you can use something like:

      % cat rec1_part1.txt rec1.java rec1.output rec1_part2.txt > rec1.txt

    Normally, however, you would want to do the concatenation inside an editor, identifying each separate file and providing some kind of line of characters separating different parts.

    I recognize that it will sometimes be annoying to write answers to recitation requirements as a text file, particularly for mathematical formula. You should not worry about making these answers good-looking or neat.

    Submissions for a recitation should not contain extraneous or excessive material, but should be limited to the recitation requirements.

  • Deadlines: Each recitation has a full credit due date and time (usually Monday at midnight during the week after the recitation, but Wednesday for the first two weeks, since there is no Monday class). After that there is a 75% credit due date and time (usually Friday at midnight during the week after the recitation). Following the second deadline, the recitation is not good for any credit.

    I intend to be strict about these deadlines. If some special problem comes up, that is what the 75% fallback credit is for, and if a special problem keeps you from meeting the second deadline, you just shouldn't have cut it that close, and it is only one out of 14 recitations. In the end, you should send something to meet the deadlines even if it is not complete.

    For the deadline I will use the timestamp on the email, which should be when the email is processed. There could be a delay between when you submit the email and the timestamp, but I hope this won't be a problem.

    It is permissible to submit the recitation in time for the first deadline, and then to submit a better version in time for the second deadline. Your grade in this case will be the better of the two grades for the two submissions. In case of multiple submissions for the same deadline, only the latest will be graded, although all will be archived.

  • Programs with Runs: I will often have you submit computer programs as part of recitation assignments. Unless explicitly stated otherwise, program source must always be submitted, and it must always be followed by the results of a run.

Revision date: 2013-07-03. (Please use ISO 8601, the International Standard.)