 |
.. (לתיקייה המכילה) | |
General | |
|
Each assignment is submitted both manually, a printout of your work + documentation, and electronically. The manual submission goes to the course's box on Taub's 1st floor, and electornic one is through a link in the site. Submission should be done no later than the specified deadline. Note that deadlines contain an exact hour. Each day delay carries a penalty of 5 points. A day late is anything between 0.001 seconds and 24 hours after the deadline. Note: you must keep the confirmation number of your automatic submission in order to prove the fact of submission in case of any problem that could arise. If you submit your "dry" (printout) works after the deadline, it should go to the box of the TA in charge of this exercise, NOT to the course box. |
Code Conventions | |
|
The code conventions below must be followed in the MATAM assignments (except for Cshell). Adherence to the code conventions will be checked in the manual check. | |
| קישור: Link: Ссылка: وصلة: | http://webcourse.cs.technion.ac.il/234122/Spring2009/ho/WCFiles/Code Conventions.pdf |
Copying - read carefully | |
|
Copying will be handled severly in this course. Your dry works and wet submissions are randomally checked. If you have been caught cheating, you and the poor persons who did the mistake and let you copy, will start with being expelled from the course with a 0, and continue with "Vaadat Mishmaat". Please, do not come crying afterwards, especially those of you who worked hard and just let others to copy. |
Is it true that there is a lot of work in this course? | |
| Yes, there is quite alot :) |
So probably you will postpone some of the homeworks, right? | |
|
Wrong. No homework will be postponed during the semester. This is a matter of principle, so there is really nothing to do about it. |
Where can we work ? | |
|
You can work in the Windows Farms (rooms 018,022) or in the Linux/Windows Farm (room 016). The students from the faculties other than CS can work in the room 014 (Windows stations). You can get the passwords for your Windows/Linux accounts from the advisors. From any computer you work on, you can connect to the t2 computer, see Course Material -> Helpers -> Working with t2 ( = stud.technion.ac.il) : http://webcourse.cs.technion.ac.il/234122/Spring2009/en/ho_Helpers.html |
Where can I find the printout of my work ? | |
|
All the printouts with the grader remarks can be found in exercises return room (near the "mazkirut"). |
Reserve Duty | |
|
Reserve duty during the period of an assignment entitles you to a day postponement on each day of reserve duty. There is no need to come in advance and ask for postponement ; you can just submit late without asking anyone. Just to remind you; late submission of the dry works is to the box of the TA in charge of the assignment. When you return from the service, bring a copy of your reserve duty certification to the TA in charge, and to him only. |
Late Submission | |
|
The only legal late submission is due to reserve duty, explained above. Any other late submission carries a fine of 5 points per each late day. It is not possible to submit more then 7 days late. Late dry submissions are only to the box of the TA in charge of that assignment. Do not submit to the course box, since it will intermix with the next assignment. Late wet submissions are as usual, via the web site. |
Why have I received -55 as "Manual check grade" ?? | |
|
This means that your dry work was not checked for some reason. It might be because you submitted it late, put it in the wrong cell, in the wrong TA box or that you been caught copying. In any case, besides the latter, contact the TA in charge of the course. |
Can I appeal on the automatic checker's results? | |
|
No, you cannot. The automatic checker, and the examples it checks, are written in a way which assures that if you followed our instructions, you will have no reason to appeal. Pay attention to our examples, how EXACTLY to run them, and make sure you test your program with them before you submit it. Beware from common pitfalls such as first testing your program, and only then document it - many times people are sure their code is working, and then when they put remarks they make errors like not closing ./* .. this will cause all tests to crash, and you lose many points. |