Lab Times & Submission Policy - Fall 2008

Tuesday 7:45 PM – 9:35 PM at H-862 - Hadi Otrok (h_otrok@encs.concordia.ca)

Thursday 5:45 PM – 7:35 PM at H-862 - Mourad Azzam (mourad@ece.concordia.ca)
The contact information of your lab instructors is indicated above.  You must contact the lab instructors directly to schedule a demonstration of a lab---DO NOT email to the list.

Please note that you are expected to demo in the lab that is assigned to you.  The lab instructors have the right to give priority to students registered in their own lab section.

Each laboratory assignment is to be done by one or two people.  For a team of two students, each person is equally responsible; the tutor will ask questions of each of you, and your mark on the assignment can differ if you exhibit different abilities in the question session.

Prior to the demonstration, you must submit certain items (depending on the laboratory) using the Electronic Assignment Submission (EAS) facility of the faculty.  This is located at https://fis.encs.concordia.ca/eas.  The following are the requirements for this submission:

  1. Submit only the source code and log files (eventually readme files) (*.cpp, *.h, *.txt, *.doc) and not the whole Visual C++  project. Usually, the archive size should be under 20K.

  2. Use only Zip type archive to pack your files (not *.ace or *.rar). Do not use autoexecutable archives.

  3. After submission you will receive an electronic receipt with a timestamp and the file name that you have submitted. If not, something went wrong during the submission. If not sure, check with the marker (usually one of the tutors).

  4. Submit the lab only under the category "programming assignment" and under the right number. Do not submit the programs under the "theoretical assignment" category.

  5. Avoid multiple submissions for the same lab assignment. By default, the marker will consider only the latest submission. If this one is submitted after the deadline, you will get a late submission penalty. Also, if the latest submission does not work, the other submissions will not be considered.

  6. Sign each source code file by including on the top commented lines which contain: the name, the student ID, and the lab number, for both you and your team partner (if any).  Otherwise, for a team of two, the marker has no way to know that he/she has to assign the program grade to more than one student.

  7. Check your email account regularly, since the marker may contact you for further details (missing files, environment incompatibilities, compile options, etc.).  


Note:  Since the EAS is keyed to your CSE (ENCS) login name, and since sending mail to a student may be automated based on the corresponding email account, you must always monitor your CSE (ENCS) account for email.  Your membership in the class mailing list may be keyed to another email address, but if you want email concerning EAS to reach you, you must log in to your CSE (ENCS) account, or somehow arrange to forward all mail received to your desired email destination.