Om's 551 page

CSCI 551 TA page, HW1 related announcements

Hi, my name is Omprakash Gnawali. I am a TA for John Heidemann's CSCI551 in Spring 2003. On this page, you will find hints and announcements related to homeworks, exams, and the course. Please make a habit of checking this page before you email me with your questions.

February 20, 2003
I just sent out grades for hw1. If you still haven't received it, you should contact me as soon as possible. Here is the statistics on HW1:

mean(79), stddev(10), min(57), max(96)

Test cases for Q3:

in1 out1 in2 out2 in3 out3 in4 out4

February 5, 2003

If you want to test your code on a little-endian machine (Intel etc), you need to compile your code in that platform and run it. The department does not provide an easy platform (linux) to do this. You can either use the windows workstations and use VC++ etc to test your code or run the code in your own Intel linux machine. Alternative approach is to reason through your code and to convince yourself that the code works in any platform. If you want to make your code cross-platform, you should make sure it compiles cleanly on aludra or nunki.

January 30, 2003

The second sample output file had a bug and now it has been corrected. It did not print the right flags.

If you are interested in reading more about the byte and bit ordering issues you might want to read the following:

Cohen, D., On Holy Wars and a Plea for Peace, Internet Experimental Note (IEN) 137, 1 April 1980. A longer version is published in IEEE Computer Magazine, pp 48-54, October 1981.
J. Reynolds, R. Braden, rfc2223bis-03.txt , Section 3.4

January 29, 2003

Information for HW1 Q3:

You should name your file hw1q3.c
I will compile your file using the following command on aludra:
```
          gcc -o hw1q3 hw1q3.c
```
I will run your program like this:
```
       ./hw1q3 < inputfile
```
Print out the header to stdout and make sure the format is exactly as it appears on the sample output. Make sure when you "diff" your output with the sample output you don't see any difference. Having consistent format helps me grade fast and return your grades fast.
Make sure you test your code on a little-endian (eg. Intel) and on a big-endian (eg. SPARC) system. Testing your code on both the architectures is the best way to make sure that your code works in both the endian worlds. I will test your code in both the endian worlds.
Sample input/output 1: hw1input1 hw1output1
Sample input/output 2: hw1input2 hw1output2