Description of the Machine Problems

• MP#1: Simple exercises in C.

• MP#2: Development of simple image/video compression algorithms.

• MP#3: Development of simple error control algorithms.

• MP#4: Development of simple network simulators.

• MP#5: Producing a Final Report.

General Rules for Working on Machine Problems

• You can work individually if you want. But starting from MP#2 (MP#1 you must do alone), you are encouraged to form pairs and collaborate to work on MPs. The grade will be based on the work turned in only, and both members will get the same grade. If you choose to team up, you and your partner are expected to share an equal load working on these MPs. I do reserve the right though to change the equal grade policy for team members if I happen to observe one person doing all the work and the other getting a free ride.

• Use of the labs:
  • Use your ECE accounts to access the Unix machines in our instruction labs. If you don't have an ECE account yet, you can request one from here. If you have one but don't remember your password, you can also reset it here.

  • For storage, your account should provide enough space so that you can develop your code there. From your account you will also be able to access a directory named /classes/ece445, where we will put all the software and data you will need to work on MPs.

  • To work from home, other networks, etc., you can ssh to ganesh.ece.cornell.edu. If you are working remotely, this will not allow you to display graphics (or it will be ridiculously slow most likely). But at least you can debug things.

  • Your programs must be compiled with the standard gcc compiler. Please don't send us questions about strange tools like MS Visual C++ (or similar), on which we will just not be able to help you. Your code must compile and run on the Unix machines in the lab.

• To submit your work:
  • Put all files you want to submit in a directory called mpN-name1-name2: name1 and name2 are the last names of the people turning in the homework, and N is the MP number (mpN-name/ if you choose to work alone).

  • Standing in the directory that contains mpN-name1-name2, execute the following command:
    
    tar -cvf mpN-name1-name2.tar mpN-name1-name2.

    Finally, attach the file mpN-name1-name2.tar to an email, and send it to the TA indicated in the "What you need to turn in" section at the bottom of each MP description.

    All MPs are due at most by 8am of the day following the date given in the "Timeline" section at the bottom of each MP description.

    We must be able to compile and execute your code. Please include with each assignment you turn in a README file telling us how to do this.

• Late MPs policy: there is no such thing. MPs not turned in by the deadline carry a weight of 0, unless you talk to me before and I give you permission to do otherwise. And please, don't even try asking for permission to turn in things late unless it is for a really good reason (e.g., a job interview). Fishing expeditions will not only not get you an extension, but what is even worse for you, they will put me in a very bad mood... :-)