[Csci551-talk] screen output messages
asyed at usc.edu
Fri Mar 18 14:29:26 PST 2005
No I dont care, just print the right output to the log file. I just want
that the hex value printed in the log file should be consistent across
all students (and it had no reason to be before since we didnt specify
it), hence the 0xFFFF and 0cAAAA values now. .
From: S. Rubin [mailto:srubin at flash.net]
Sent: Friday, March 18, 2005 12:40 PM
To: Affan, Syed; csci551-talk at mailman.isi.edu
Cc: cs551 at catarina.usc.edu
Subject: RE: [Csci551-talk] screen output messages
Then, what is the 0xFF and 0xAA for as a new requirement? I number the
with my own numbers and later convert them into strings to be written
into the log files
as shown in the project paper sample outputs. Do you care if I use
non-hex values for
my own purposes as long as I print the correct string into the log file?
our internal choice of values affect the ease of grading for you since
you will be seeing
"Affan, Syed" <asyed at usc.edu> wrote:
I dont think the requirement is to print anything on the screen. Simply
log the output. We will only grade based on the log file.
From: csci551-talk-bounces at mailman.isi.edu
[mailto:csci551-talk-bounces at mailman.isi.edu] On Behalf Of S. Rubin
Sent: Friday, March 18, 2005 10:31 AM
To: csci551-talk at mailman.isi.edu
Subject: [Csci551-talk] screen output messages
I know that there are no stated requirements, except for the 0xFF and
messages, regarding what to display on the screen. I noticed that if I
"inter-client" messages for each segment request/receipt, the I/O really
down the "download" progress.Could the person grading the program be
with "client<-->tracker" messages and perhaps some milestone reaching
like start/finish download, new client comes/goes, etc. We record
the log files anyway, so all steps can be traced.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Csci551-talk