Submitting Code

This is the archived version of this course from the Spring 2013 semester. You might find something more recent by visitning my teaching page.

All code for the projects must be submitted electronically, from the USNA cs linux environment. There will be specific requirements for commenting and file names for all code.

All programming problems must be submitted electronically, before the class when they are due, from the USNA cs linux environment. If you need help accessing the environment from Bancroft hall, ask the instructor or a fellow classmate. All code is expected to be clearly commented and cleanly written so it is easy to understand. (Unclear or poorly-formatted code is grounds for requiring a revision.)

Naming

Unless otherwise specified, all code must be submitted as Java, C++, or Python programs. You should name your file "Prob.java", "prob.py", or "prob.cpp" as appropriate. Depending on the language, I will run your program from the CS Linux environment with one of the following commands, where arg1, arg2, etc. are any command-line arguments:

Java:

javac Prob.java
java Prob arg1 arg2 arg3 ...

C++:

g++ prob.cpp -o prob
./prob arg1 arg2 arg3 ...

Python:
```
python3 prob.py arg1 arg2 arg3 ...
```

(Notice, for Java, you must have a class named Prob that has the public static void main method defined.)

Environment

I've set up some useful aliases for you so you don't have to type so many directories every time. To get these aliases at your command prompt, add the following line to the file $HOME/.bashrc:

source /home/roche/486d/bashlines.sh

This will define some shortcuts (aliases) to run any programs we will need for this class.

The submit program

The program you will use to submit is located at /home/roche/submit, but can be run by typing 486sub if you edited your .bashrc file as described above. This program is accessible from the usna CS linux environment. You can use it from the MI 302 lab or log into one of the machines remotely.

When you run 486sub with no arguments, it will display something like

Open submissions matching your search:
prob 16

This means, unsurprisingly, that SI 486D has one thing open for submission, it's a problem, and it's number 16. To submit your file or files for this lab, you make a directory in your account (like mkdir prob20), then put any files to submit in there.

Once you have your local directory, and you confirm that the assignment is open for submission, you cd to that directory and run

486sub prob 16

(for example) to submit your files. This will check your files, and then bundle and submit them to your instructor. At the end you will see something like:

Submitting 486d prob 16 for user roche to Dr. Roche..
roche/
roche/hi.txt
Submission successful.

You can see that there is one file that was submitted, called hi.txt. Note the last line, telling me that it was successful. If you don't see this line, then something went wrong.

All this does is put all your files in a place where I can see them, with a timestamp and your username. You are free to submit the same assignment repeatedly, and I will only look at the most recent submission for grading purposes.