Main.CheckinInfo History
Hide minor edits - Show changes to output
Changed line 1 from:
!!Checking In Assignments
to:
!!Electronic Check-In For Programming Assignments
Changed lines 25-27 from:
You may not like typing in such long commands. in that case, you can add an alias to your [@.cshrc@] For example, you may want to add the lines:\\
to:
You may not like typing in such long commands. in that case, you can add an alias to your [@.cshrc@] For example, you may want to add the lines:
>>frame<<
>>frame<<
Added lines 32-33:
>><<
Changed lines 38-40 from:
Let's say you wanted to turn in a file [@Results.txt@] for HW2:\\
to:
Let's say you wanted to turn in a file [@Results.txt@] for HW2:
>>frame<<
>>frame<<
Changed lines 56-57 from:
to:
>><<
Added line 60:
>>frame<<
Added line 82:
>><<
Changed lines 27-28 from:
alias ci320 '~cs320/bin/checkin'\\
alias pk320 '~cs320/bin/peek'\\
alias pk320 '~cs320/bin/peek'
to:
alias ci320 '~cs320/bin/checkin'
alias pk320 '~cs320/bin/peek'
alias pk320 '~cs320/bin/peek'
Changed line 7 from:
"[@HWx@]" should be whichever homework you are submitting (such as HW3 or HW1) "[@filenames@]" should be replaced with whatever filenames you want to submit (You don't need to submit all of the files at the same time if you don't want to. One at a time is fine as well, they will only overwrite the older files if they have the SAME name.
to:
"[@HWx@]" should be whichever homework you are submitting (such as HW3 or HW1); "[@filenames@]" should be replaced with whatever filenames you want to submit (you don't need to submit all of the files at the same time if you don't want to. One at a time is fine as well, they will only overwrite the older files if they have the SAME name.
Changed lines 7-8 from:
"[@HWx@]" should be whichever homework you are submitting (such as HW3 or HW1) "[@filenames@]" should be replaced with whatever filenames you want so submit (You don't need to submit all of the files at the same time if you don't want to. One at a time is fine as well, they will only overwrite the older files if they Have the SAME name.
to:
"[@HWx@]" should be whichever homework you are submitting (such as HW3 or HW1) "[@filenames@]" should be replaced with whatever filenames you want to submit (You don't need to submit all of the files at the same time if you don't want to. One at a time is fine as well, they will only overwrite the older files if they have the SAME name.
Changed lines 11-12 from:
!Making Sure Things Were Checked In Right
to:
!!Making Sure Things Were Checked In Right
Changed line 23 from:
!! Making it easier
to:
!!Making it easier
Changed line 5 from:
[@~cs320/bin/checkin HWx filenames@]
to:
%frame%[@~cs320/bin/checkin HWx filenames@]
Changed lines 27-28 from:
alias ci155 '~cs101/bin/checkin'\\
aliaspk155 '~cs101/bin/peek'\\
alias
to:
alias ci320 '~cs320/bin/checkin'\\
alias pk320 '~cs320/bin/peek'\\
alias pk320 '~cs320/bin/peek'\\
Changed lines 30-31 from:
to your [@.cshrc@] and the effect would be that you would only need to type: [@ci155 HW2 myfile.txt@] instead of [@~cs101/bin/checkin HW2 myfile.txt@] and [@pk155@] instead of [@~cs101/bin/peek@].
to:
to your [@.cshrc@] and the effect would be that you would only need to type: [@ci320 HW2 myfile.txt@] instead of [@~cs320/bin/checkin HW2 myfile.txt@] and [@pk320@] instead of [@~cs320/bin/peek@].
Changed line 36 from:
% cd cs101/Assign2
to:
% cd cs320/Assign2
Changed line 39 from:
% ~cs101/bin/checkin HW2 Results.txt
to:
% ~cs320/bin/checkin HW2 Results.txt
Changed line 55 from:
% ~cs101/bin/checkin HW2 Results.txt
to:
% ~cs320/bin/checkin HW2 Results.txt
Changed line 65 from:
% ~cs101/bin/peek
to:
% ~cs320/bin/peek
Changed lines 1-19 from:
!For Students: Checking In Assignments
Login to a Linux machine (if you aren't on one already).
type [@~cs320/bin/checkin HWx filenames@] "HWx"
should be whichever homework you are submitting (such as HW3 or
HW1) "filenames" should be replaced with whatever filenames you
want so submit (You don't need to submit all of the files at the
same time if you don't want to. One at a time is fine as well,
they will only overwrite the older files if they Have the SAME
name.
The checkin program will tell you some messages. Hopefully, they
will say encouraging things like "Checkin successfull", and the
current date/time, and other useful information. It will also
tell you if it has made any backups of older files.
Login to a Linux machine (if you aren't on one already).
HW1) "filenames" should be replaced with whatever filenames you
name.
The checkin program will tell you some messages. Hopefully, they
to:
!!Checking In Assignments
Login to a Linux machine (if you aren't on one already). "cd" to the subdirectory containing the file(s) to check in. Type
[@~cs320/bin/checkin HWx filenames@]
"[@HWx@]" should be whichever homework you are submitting (such as HW3 or HW1) "[@filenames@]" should be replaced with whatever filenames you want so submit (You don't need to submit all of the files at the same time if you don't want to. One at a time is fine as well, they will only overwrite the older files if they Have the SAME name.
The checkin program will tell you some messages. Hopefully, they will say encouraging things like "Checkin successful", and the current date/time, and other useful information. It will also tell you if it has made any backups of older files.
Login to a Linux machine (if you aren't on one already). "cd" to the subdirectory containing the file(s) to check in. Type
[@~cs320/bin/checkin HWx filenames@]
"[@HWx@]" should be whichever homework you are submitting (such as HW3 or HW1) "[@filenames@]" should be replaced with whatever filenames you want so submit (You don't need to submit all of the files at the same time if you don't want to. One at a time is fine as well, they will only overwrite the older files if they Have the SAME name.
The checkin program will tell you some messages. Hopefully, they will say encouraging things like "Checkin successful", and the current date/time, and other useful information. It will also tell you if it has made any backups of older files.
Changed lines 13-61 from:
Decide how paranoid you want to be:
Type [@~cs101/bin/peek@] and you will be presented with a list
of every file you have ever submitted to the checkin program in this class.
As well as dates, times, sizes, and the assignment it was submitted for.
Type [@~cs101/bin/peek HWx@] (where HWx is the
assignment you are checking on) and you will be presented with a
list of every file you have ever submitted for that assignment.
(:if false:)
Type <u><tt>~cs101/bin/peek HWx filename</tt></u> (where HWx is
the assignment you are checking on, and filename is the file you
want to look at) and it will dump the contents of the file to
your screen. If the file is long, you may want to consider
"piping it thru more" (meaning, type <u><tt>~cs101/bin/peek HWx
filename | more</tt></u>. You could also redirect the output to
file in your home dir.
</ul>
<li> Once you feel secure enough that it worked, you can relax.
</ol>
<h2>For Students: Checking Grades</h2>
<ol>
<li> Login to a Linux machine (if you aren't on one already). (Try davis)
<li> Type <u><tt>~cs101/bin/grade</tt></u> and you will be presented
with grades for each of your graded assignments.
<li> Type <u><tt>~cs101/bin/grade HWx</tt></u> (where HWx is the
assignment you are checking on) and you will be presented with
with the grade and comments for that assignment.
</ol>
<h2>For Students: Making it easier</h2>
You may not like typing in such long commands.
in that case, you can add an alias to your <tt>.cshrc</tt>
for example, yo umay want to add the lines<br>
<tt><u>alias ci155 '~cs101/bin/checkin'</u></tt><br>
<tt><u>alias pk155 '~cs101/bin/peek'</u></tt><br>
to your <tt>.cshrc</tt> and the effect would be that you would only need to type:<br>
<tt><u>ci155 HW2 myfile.txt</u></tt> instead of <tt><u>~cs101/bin/checkin HW2 myfile.txt</u></tt>... and<br>
<tt><u>pk155</u></tt> instead of <tt><u>~cs101/bin/peek</u></tt>.<br>
<h2>For Students: An Example</h2>
Lets say you wanted to turn in a file <tt>Results.txt</tt> for HW2:<br>
<pre>
to:
Login to a Linux machine (if you aren't on one already). Decide how paranoid you want to be:
* Type [@~cs320/bin/peek@] and you will be presented with a list of every file you have ever submitted to the checkin program in this class. As well as dates, times, sizes, and the assignment it was submitted for.
* Type [@~cs320/bin/peek HWx@] (where HWx is the assignment you are checking on) and you will be presented with a list of every file you have ever submitted for that assignment.
* Type [@~cs320/bin/peek HWx filename@] (where HWx is the assignment you are checking on, and filename is the file you want to look at) and it will dump the contents of the file to your screen. If the file is long, you may want to consider "piping it thru more" (meaning, type [@~cs320/bin/peek HWx filename | more@]. You could also redirect the output to file in your home dir.
Once you feel secure enough that it worked, you can relax.
!! Making it easier
You may not like typing in such long commands. in that case, you can add an alias to your [@.cshrc@] For example, you may want to add the lines:\\
[@
alias ci155 '~cs101/bin/checkin'\\
alias pk155 '~cs101/bin/peek'\\
@]
to your [@.cshrc@] and the effect would be that you would only need to type: [@ci155 HW2 myfile.txt@] instead of [@~cs101/bin/checkin HW2 myfile.txt@] and [@pk155@] instead of [@~cs101/bin/peek@].
!!An Example
Let's say you wanted to turn in a file [@Results.txt@] for HW2:\\
[@
* Type [@~cs320/bin/peek@] and you will be presented with a list of every file you have ever submitted to the checkin program in this class. As well as dates, times, sizes, and the assignment it was submitted for.
* Type [@~cs320/bin/peek HWx@] (where HWx is the assignment you are checking on) and you will be presented with a list of every file you have ever submitted for that assignment.
* Type [@~cs320/bin/peek HWx filename@] (where HWx is the assignment you are checking on, and filename is the file you want to look at) and it will dump the contents of the file to your screen. If the file is long, you may want to consider "piping it thru more" (meaning, type [@~cs320/bin/peek HWx filename | more@]. You could also redirect the output to file in your home dir.
Once you feel secure enough that it worked, you can relax.
!! Making it easier
You may not like typing in such long commands. in that case, you can add an alias to your [@.cshrc@] For example, you may want to add the lines:\\
[@
alias ci155 '~cs101/bin/checkin'\\
alias pk155 '~cs101/bin/peek'\\
@]
to your [@.cshrc@] and the effect would be that you would only need to type: [@ci155 HW2 myfile.txt@] instead of [@~cs101/bin/checkin HW2 myfile.txt@] and [@pk155@] instead of [@~cs101/bin/peek@].
!!An Example
Let's say you wanted to turn in a file [@Results.txt@] for HW2:\\
[@
Changed lines 49-50 from:
to:
@]
Changed lines 52-53 from:
to:
[@
Changed lines 73-129 from:
<h2>For Students: Some things to keep in mind</h2>
<ul>
<li> All assignments are to be submitted electronically and are
automatically <b>time stamped</b>, so we know when files were
submitted. PLEASE SUBMIT ASSIGNMENTS ON TIME!
<li> <b>Logs are kept</b> of everything, so if you try to submit files and it
does not work correctly, we can look at the logs to help identify the
problems.
<li> It is <b>YOUR responsibility</b> to ensure that you have
submitted all the files that are required for each assignment. All
files you submit should be named appropriately. If you fail to submit
a homework, we cannot grade it! And if we can't grade it.. we have to
assume a ZERO! So <b>please be sure to submit things properly</b>.
<li> You can <b>run the checkin program on the same file as many times
as you like</b>. The checkin program will keep every copy, but only
the MOST RECENT will be graded. If for some reason you want an older
version to be graded, please let us know!
<li> The checkin program <b>only runs on Linux machines</b>. Almost
all of the machines in the labs run linux. But if for some reason you
log in on a machine that runs another OS, you can log in to a linux
machine (like armstrong, basie, brubeck, davis, ellington, etc..) and
run the checkin program from there.
<li> The checkin program will let you <b>check in any file at all</b>,
wether it is a text file, or an executable, or a jpeg, or a video
game, or a... you get the idea... So please be careful what you
submit!
<li> The checkin program will NOT alter your copy of the file being
submitted. It will just send a duplicate of it for grading. Don't
wory about it harming your files. It will not.
<li> Every assignment has three dates associated with it:
<ol>
<li> <b>Assigned date</b>: If you try to submit a file BEFORE it is
assigned, the checkin program will not let you.
<li> <b>Due Date</b>: The checkin program will remind you of the due
date of an assignment when you submit it. If you are before the due
date, it will let you know how much longer you have to re-sumbit a
newer version before the due date. If you are after the due date, it
will let you know that the assignment is late. Hopefully you will
still get some partial credit.
<li> <b>Drop Dead Date</b>: The date after which the homework will not
be accepted. The checkin program will simply not let you submit after
this date. After this date, there is no partial credit. Sorry!
</ol>
</ul>
(:ifend:)
to:
@]
!!Some things to keep in mind
* All assignments are to be submitted electronically and are automatically '''time stamped''', so we know when files were submitted. PLEASE SUBMIT ASSIGNMENTS ON TIME!
* '''Logs are kept''' of everything, so if you try to submit files and it does not work correctly, we can look at the logs to help identify the problems.
* It is '''YOUR responsibility''' to ensure that you have submitted all the files that are required for each assignment. All files you submit should be named appropriately. If you fail to submit a homework, we cannot grade it! And if we can't grade it.. we have to assume a ZERO! So '''please be sure to submit things properly'''.
* You can '''run the checkin program on the same file as many times as you like.''' The checkin program will keep every copy, but only the MOST RECENT will be graded. If for some reason you want an older version to be graded, please let us know!
* The checkin program '''only runs on Linux machines'''. Almost all of the machines in the labs run linux. But if for some reason you log in on a machine that runs another OS, you can log in to a linux machine and run the checkin program from there.
* The checkin program will let you '''check in any file at all''', whether it is a text file, or an executable, or a jpeg, or a video game, or a... you get the idea... So please be careful what you submit!
* The checkin program will NOT alter your copy of the file being submitted. It will just send a duplicate of it for grading. Don't worry about it harming your files. It will not.
* Every assignment has three dates associated with it:
** '''Assigned date''': If you try to submit a file BEFORE it is assigned, the checkin program will not let you.
** '''Due Date''': The checkin program will remind you of the due date of an assignment when you submit it. If you are before the due date, it will let you know how much longer you have to re-sumbit a newer version before the due date. If you are after the due date, it will let you know that the assignment is late. Hopefully you will still get some partial credit.
** '''Drop Dead Date''': The date after which the homework will not be accepted. The checkin program will simply not let you submit after this date. After this date, there is no partial credit. Sorry!
!!Some things to keep in mind
* All assignments are to be submitted electronically and are automatically '''time stamped''', so we know when files were submitted. PLEASE SUBMIT ASSIGNMENTS ON TIME!
* '''Logs are kept''' of everything, so if you try to submit files and it does not work correctly, we can look at the logs to help identify the problems.
* It is '''YOUR responsibility''' to ensure that you have submitted all the files that are required for each assignment. All files you submit should be named appropriately. If you fail to submit a homework, we cannot grade it! And if we can't grade it.. we have to assume a ZERO! So '''please be sure to submit things properly'''.
* You can '''run the checkin program on the same file as many times as you like.''' The checkin program will keep every copy, but only the MOST RECENT will be graded. If for some reason you want an older version to be graded, please let us know!
* The checkin program '''only runs on Linux machines'''. Almost all of the machines in the labs run linux. But if for some reason you log in on a machine that runs another OS, you can log in to a linux machine and run the checkin program from there.
* The checkin program will let you '''check in any file at all''', whether it is a text file, or an executable, or a jpeg, or a video game, or a... you get the idea... So please be careful what you submit!
* The checkin program will NOT alter your copy of the file being submitted. It will just send a duplicate of it for grading. Don't worry about it harming your files. It will not.
* Every assignment has three dates associated with it:
** '''Assigned date''': If you try to submit a file BEFORE it is assigned, the checkin program will not let you.
** '''Due Date''': The checkin program will remind you of the due date of an assignment when you submit it. If you are before the due date, it will let you know how much longer you have to re-sumbit a newer version before the due date. If you are after the due date, it will let you know that the assignment is late. Hopefully you will still get some partial credit.
** '''Drop Dead Date''': The date after which the homework will not be accepted. The checkin program will simply not let you submit after this date. After this date, there is no partial credit. Sorry!
Added lines 1-163:
!For Students: Checking In Assignments
Login to a Linux machine (if you aren't on one already).
"cd" to the subdirectory containing the file(s) to check in.
type [@~cs320/bin/checkin HWx filenames@] "HWx"
should be whichever homework you are submitting (such as HW3 or
HW1) "filenames" should be replaced with whatever filenames you
want so submit (You don't need to submit all of the files at the
same time if you don't want to. One at a time is fine as well,
they will only overwrite the older files if they Have the SAME
name.
The checkin program will tell you some messages. Hopefully, they
will say encouraging things like "Checkin successfull", and the
current date/time, and other useful information. It will also
tell you if it has made any backups of older files.
!Making Sure Things Were Checked In Right
Login to a Linux machine (if you aren't on one already).
Decide how paranoid you want to be:
Type [@~cs101/bin/peek@] and you will be presented with a list
of every file you have ever submitted to the checkin program in this class.
As well as dates, times, sizes, and the assignment it was submitted for.
Type [@~cs101/bin/peek HWx@] (where HWx is the
assignment you are checking on) and you will be presented with a
list of every file you have ever submitted for that assignment.
(:if false:)
Type <u><tt>~cs101/bin/peek HWx filename</tt></u> (where HWx is
the assignment you are checking on, and filename is the file you
want to look at) and it will dump the contents of the file to
your screen. If the file is long, you may want to consider
"piping it thru more" (meaning, type <u><tt>~cs101/bin/peek HWx
filename | more</tt></u>. You could also redirect the output to
file in your home dir.
</ul>
<li> Once you feel secure enough that it worked, you can relax.
</ol>
<h2>For Students: Checking Grades</h2>
<ol>
<li> Login to a Linux machine (if you aren't on one already). (Try davis)
<li> Type <u><tt>~cs101/bin/grade</tt></u> and you will be presented
with grades for each of your graded assignments.
<li> Type <u><tt>~cs101/bin/grade HWx</tt></u> (where HWx is the
assignment you are checking on) and you will be presented with
with the grade and comments for that assignment.
</ol>
<h2>For Students: Making it easier</h2>
You may not like typing in such long commands.
in that case, you can add an alias to your <tt>.cshrc</tt>
for example, yo umay want to add the lines<br>
<tt><u>alias ci155 '~cs101/bin/checkin'</u></tt><br>
<tt><u>alias pk155 '~cs101/bin/peek'</u></tt><br>
to your <tt>.cshrc</tt> and the effect would be that you would only need to type:<br>
<tt><u>ci155 HW2 myfile.txt</u></tt> instead of <tt><u>~cs101/bin/checkin HW2 myfile.txt</u></tt>... and<br>
<tt><u>pk155</u></tt> instead of <tt><u>~cs101/bin/peek</u></tt>.<br>
<h2>For Students: An Example</h2>
Lets say you wanted to turn in a file <tt>Results.txt</tt> for HW2:<br>
<pre>
% cd cs101/Assign2
% ls
Results.txt SomeOtherFile.txt SomeThingElse.txt
% ~cs101/bin/checkin HW2 Results.txt
Checking in files for assignment 'HW2'
Current time is: Mon Aug 8 12:16:03 2005
Assignment is ON TIME!
If you wish, you may turn in another (presumably better)
version up until Fri Dec 9 23:59:59 2005
and it will replace this version.
File Results.txt was checked in.
%
</pre>
Now, suppose you made a mistake and wish to fix it and submit a new copy..
<pre>
% emacs Results.txt
% ~cs101/bin/checkin HW2 Results.txt
Checking in files for assignment 'HW2'
Current time is: Mon Aug 8 13:45:35 2005
Assignment is ON TIME!
If you wish, you may turn in another (presumably better)
version up until Fri Dec 9 23:59:59 2005
and it will replace this version.
Renaming old Results.txt to Results.txt.old
File Results.txt was checked in.
% ~cs101/bin/peek
Size Date Time Assignment File
---------- --------------- -------- ---------- ----
13703 Mon Aug 8 2005 13:45:35 HW2 Results.txt
13814 Mon Aug 8 2005 12:16:03 HW2 Results.txt.old
2 Files listed
%
</pre>
<h2>For Students: Some things to keep in mind</h2>
<ul>
<li> All assignments are to be submitted electronically and are
automatically <b>time stamped</b>, so we know when files were
submitted. PLEASE SUBMIT ASSIGNMENTS ON TIME!
<li> <b>Logs are kept</b> of everything, so if you try to submit files and it
does not work correctly, we can look at the logs to help identify the
problems.
<li> It is <b>YOUR responsibility</b> to ensure that you have
submitted all the files that are required for each assignment. All
files you submit should be named appropriately. If you fail to submit
a homework, we cannot grade it! And if we can't grade it.. we have to
assume a ZERO! So <b>please be sure to submit things properly</b>.
<li> You can <b>run the checkin program on the same file as many times
as you like</b>. The checkin program will keep every copy, but only
the MOST RECENT will be graded. If for some reason you want an older
version to be graded, please let us know!
<li> The checkin program <b>only runs on Linux machines</b>. Almost
all of the machines in the labs run linux. But if for some reason you
log in on a machine that runs another OS, you can log in to a linux
machine (like armstrong, basie, brubeck, davis, ellington, etc..) and
run the checkin program from there.
<li> The checkin program will let you <b>check in any file at all</b>,
wether it is a text file, or an executable, or a jpeg, or a video
game, or a... you get the idea... So please be careful what you
submit!
<li> The checkin program will NOT alter your copy of the file being
submitted. It will just send a duplicate of it for grading. Don't
wory about it harming your files. It will not.
<li> Every assignment has three dates associated with it:
<ol>
<li> <b>Assigned date</b>: If you try to submit a file BEFORE it is
assigned, the checkin program will not let you.
<li> <b>Due Date</b>: The checkin program will remind you of the due
date of an assignment when you submit it. If you are before the due
date, it will let you know how much longer you have to re-sumbit a
newer version before the due date. If you are after the due date, it
will let you know that the assignment is late. Hopefully you will
still get some partial credit.
<li> <b>Drop Dead Date</b>: The date after which the homework will not
be accepted. The checkin program will simply not let you submit after
this date. After this date, there is no partial credit. Sorry!
</ol>
</ul>
(:ifend:)
Login to a Linux machine (if you aren't on one already).
"cd" to the subdirectory containing the file(s) to check in.
type [@~cs320/bin/checkin HWx filenames@] "HWx"
should be whichever homework you are submitting (such as HW3 or
HW1) "filenames" should be replaced with whatever filenames you
want so submit (You don't need to submit all of the files at the
same time if you don't want to. One at a time is fine as well,
they will only overwrite the older files if they Have the SAME
name.
The checkin program will tell you some messages. Hopefully, they
will say encouraging things like "Checkin successfull", and the
current date/time, and other useful information. It will also
tell you if it has made any backups of older files.
!Making Sure Things Were Checked In Right
Login to a Linux machine (if you aren't on one already).
Decide how paranoid you want to be:
Type [@~cs101/bin/peek@] and you will be presented with a list
of every file you have ever submitted to the checkin program in this class.
As well as dates, times, sizes, and the assignment it was submitted for.
Type [@~cs101/bin/peek HWx@] (where HWx is the
assignment you are checking on) and you will be presented with a
list of every file you have ever submitted for that assignment.
(:if false:)
Type <u><tt>~cs101/bin/peek HWx filename</tt></u> (where HWx is
the assignment you are checking on, and filename is the file you
want to look at) and it will dump the contents of the file to
your screen. If the file is long, you may want to consider
"piping it thru more" (meaning, type <u><tt>~cs101/bin/peek HWx
filename | more</tt></u>. You could also redirect the output to
file in your home dir.
</ul>
<li> Once you feel secure enough that it worked, you can relax.
</ol>
<h2>For Students: Checking Grades</h2>
<ol>
<li> Login to a Linux machine (if you aren't on one already). (Try davis)
<li> Type <u><tt>~cs101/bin/grade</tt></u> and you will be presented
with grades for each of your graded assignments.
<li> Type <u><tt>~cs101/bin/grade HWx</tt></u> (where HWx is the
assignment you are checking on) and you will be presented with
with the grade and comments for that assignment.
</ol>
<h2>For Students: Making it easier</h2>
You may not like typing in such long commands.
in that case, you can add an alias to your <tt>.cshrc</tt>
for example, yo umay want to add the lines<br>
<tt><u>alias ci155 '~cs101/bin/checkin'</u></tt><br>
<tt><u>alias pk155 '~cs101/bin/peek'</u></tt><br>
to your <tt>.cshrc</tt> and the effect would be that you would only need to type:<br>
<tt><u>ci155 HW2 myfile.txt</u></tt> instead of <tt><u>~cs101/bin/checkin HW2 myfile.txt</u></tt>... and<br>
<tt><u>pk155</u></tt> instead of <tt><u>~cs101/bin/peek</u></tt>.<br>
<h2>For Students: An Example</h2>
Lets say you wanted to turn in a file <tt>Results.txt</tt> for HW2:<br>
<pre>
% cd cs101/Assign2
% ls
Results.txt SomeOtherFile.txt SomeThingElse.txt
% ~cs101/bin/checkin HW2 Results.txt
Checking in files for assignment 'HW2'
Current time is: Mon Aug 8 12:16:03 2005
Assignment is ON TIME!
If you wish, you may turn in another (presumably better)
version up until Fri Dec 9 23:59:59 2005
and it will replace this version.
File Results.txt was checked in.
%
</pre>
Now, suppose you made a mistake and wish to fix it and submit a new copy..
<pre>
% emacs Results.txt
% ~cs101/bin/checkin HW2 Results.txt
Checking in files for assignment 'HW2'
Current time is: Mon Aug 8 13:45:35 2005
Assignment is ON TIME!
If you wish, you may turn in another (presumably better)
version up until Fri Dec 9 23:59:59 2005
and it will replace this version.
Renaming old Results.txt to Results.txt.old
File Results.txt was checked in.
% ~cs101/bin/peek
Size Date Time Assignment File
---------- --------------- -------- ---------- ----
13703 Mon Aug 8 2005 13:45:35 HW2 Results.txt
13814 Mon Aug 8 2005 12:16:03 HW2 Results.txt.old
2 Files listed
%
</pre>
<h2>For Students: Some things to keep in mind</h2>
<ul>
<li> All assignments are to be submitted electronically and are
automatically <b>time stamped</b>, so we know when files were
submitted. PLEASE SUBMIT ASSIGNMENTS ON TIME!
<li> <b>Logs are kept</b> of everything, so if you try to submit files and it
does not work correctly, we can look at the logs to help identify the
problems.
<li> It is <b>YOUR responsibility</b> to ensure that you have
submitted all the files that are required for each assignment. All
files you submit should be named appropriately. If you fail to submit
a homework, we cannot grade it! And if we can't grade it.. we have to
assume a ZERO! So <b>please be sure to submit things properly</b>.
<li> You can <b>run the checkin program on the same file as many times
as you like</b>. The checkin program will keep every copy, but only
the MOST RECENT will be graded. If for some reason you want an older
version to be graded, please let us know!
<li> The checkin program <b>only runs on Linux machines</b>. Almost
all of the machines in the labs run linux. But if for some reason you
log in on a machine that runs another OS, you can log in to a linux
machine (like armstrong, basie, brubeck, davis, ellington, etc..) and
run the checkin program from there.
<li> The checkin program will let you <b>check in any file at all</b>,
wether it is a text file, or an executable, or a jpeg, or a video
game, or a... you get the idea... So please be careful what you
submit!
<li> The checkin program will NOT alter your copy of the file being
submitted. It will just send a duplicate of it for grading. Don't
wory about it harming your files. It will not.
<li> Every assignment has three dates associated with it:
<ol>
<li> <b>Assigned date</b>: If you try to submit a file BEFORE it is
assigned, the checkin program will not let you.
<li> <b>Due Date</b>: The checkin program will remind you of the due
date of an assignment when you submit it. If you are before the due
date, it will let you know how much longer you have to re-sumbit a
newer version before the due date. If you are after the due date, it
will let you know that the assignment is late. Hopefully you will
still get some partial credit.
<li> <b>Drop Dead Date</b>: The date after which the homework will not
be accepted. The checkin program will simply not let you submit after
this date. After this date, there is no partial credit. Sorry!
</ol>
</ul>
(:ifend:)