|
1) Before beginning the programming assignment of a problem set, you should create a directory in your account for that problem set, and do the work for that problem set in that directory. The following sequence of commands will do this for unit5 (change the number for later assignments -- everything else will remain the same): [is01]~> cd
[is01]~> mkdir unit5
[is01]~> cd unit5
[is01]~/unit5>%
This makes
the new directory, and then switches you into it. Note that the
numbers in 2) Now, working on nice.harvard.edu, type in (or transfer the files), compile, and debug your programs. You'll end up with a bunch of files, some with a '.java' suffix and some with a '.class' suffix. 3)
Once you're ready to turn in your programs, you should use 'script'
to generate demo output. If your source file is "Rocks.java,"
you should name your script file "Rocks.out", so we can tell which
program it is the demo for! Here's how it works; at the [is01]~/unit5>% script -a Rocks.out From this
point on, until you type an 'exit' command at the [is01]~> bye...some messages appear: exit, Script done, file is Rocks.out... Now, you can print out the file "Rocks.out" and hand it in! Easy as pie! PLEASE always use the -a modifier with the script command - we DID have people who lost homework programs and projects this past semester because they overwrote their .java file by accidentally typing in the wrong file extension!! The -a modifier will always append your tests to the file. Once you have thoroughly tested your code and created "demo output" files, submitting your assignment is easy. There are two parts:
TO SUBMIT ELECTRONICALLY, connect to nice.harvard.edu and simply type (at the prompt): [is01]~> submit libe50b 51 ~/unit5 The syntax is picky: there are four parts to that command. The first two are easy, just type them in; the remainder require explanation:
That's it! BUT... it will only work if you've fully and correctly completed steps 1 - 3 above. If you have trouble, reread these instructions to make sure you've done everything indicated above. If all's well, you'll see a few messages, then a message stating that submission was successful.
ice3:~ % submit libe50b 51 ~/unit5
Ok, submitting the files in /home/j/j/jjackson/unit5
Creating temporary directory /tmp/jjackson.submit...
Copying assignment files to /tmp/jjackson.submit...
Opened file /home/l/i/libe50b/submit/asst51/jjackson.tgz
Submitting libe50b assignment 51... Done!
Temporary files removed.
By
the way, it's OK TO RE-SUBMIT revised versions of programs.
The 'submit' program will notice that you've already submitted, and will
cautiously let you re-submit, prompting you about proceeding.
IF YOU RE-SUBMIT, NOTE THE FOLLOWING:
If you resubmit, you'll see the same message that you had before. NOTE that if you resubmit, you need to include ALL the files due for that particular homework, as the resubmit overwrites all prior submissions. After 'submitting' as above, you should print out your files so they can be turned in to your Teaching Fellow. |