|
This page is to provide information to students for the CS551 Spring
2005 session. I will regularly update this page for any changes to the
class projects and also post some FAQ's. Please continue to regularly check
this page for updates.
Home Work #1 - Corrections/FAQ:
- Problem 3 part a) should be changed to the following statement.
"a) What are the contents of this advertisement from
AS1
to AS2 that
concern routes to D?". Thanks to
Sophia for noticing this.
- Problem 2: The initialization of
the structures should be as follows (for syntactical correctness -
otherwise it should not affect your solution):
struct message m1 = { '1',
0x12345678, "test", "extra1" };
struct message m2 = {
'2', 0x87654321, "second-message", "extra2" };
Project A - FAQ and Information:
- Look out for more information regarding input and output files and any correction made to the project A over here
- Project description has been updated. The link to the file is
here. I have
made all the changes with the tag (NEW:2/28) in front of them to
make it easy to find the changes/addition to the project
requirements.
-
Sample Input file to test your program is now uploaded
over here .
-
Project clarifications 3/15/2005:
- We will not be testing the case of providing an
incorrect filename to download (as suggested in the orignal document
pg 2).
- Delay are for outgoing replies for only client to client
interaction. This would involve the case when a node gets a segment
update message, or a segment download message. In both of these
cases, before replying the node will delay the packet transmission.
- The packet drop/sent statistics are to be kept per *node*, both
tracker and client.
Use following hex values when logging to file: GROUP_SHOW_INTEREST 0xFFFF
GROUP_ASSIGN 0xAAAA
Log message for each clients should show *all* messages received
or sent by that client. This clarification is so that students do
not assume that only the messsage shown in the example output (pg
11) are to be logged.
Links to sample input and output files (as you should output)
are over here: manager.conf,
0.out, 1.out and
tracker.out.
CLARIFICATION: Seed node *should not* stop showing
interest to the tracker after its first task. Similarly all nodes
that complete downloading a file should also not stop showing
interest, only change their type.
Re-grading Policy for Project A
You may request your project to be re-graded.
Since we are grading large number of students, it is possible that
grading mistakes exist. You may ask for regrade in this case. Before
you request a re-grade, however, please run your project against all
the test cases provided (soon), and compute your score according to
the grading policy. Please approach the grader for re-grading *only*
if your score on the project differs from the computed score by at
least 4 points. This policy is designed to discourage trivial
re-grade requests. If you visit the grader for re-grade, the grader
will *thoroughly* check your program. This might increase your grade
for project A. But this might also discover additional bugs or
errors in your program which we did not find during the
initial grading procedure. So, *keep in mind* that there is a chance
that you might end up receiving less points than your original
grade. We *will deduct* points for additionally discovered
bugs/errors. So, check your program thoroughly before requesting for
regrade. No crying, begging, or threatening will work on the grader.
551 Proj A sample source code available over
HERE. Be aware that this code is to be
used for reference, but in any case the authors are not going to
explain any section of the code.
Project B - FAQ and Information:
- An updated version of the project is now uploaded
HERE. New sections are marked with tag (NEW:4/13).
|