Submission Instructions

To make your submission file, make a directory and copy all required files into it. Change to that directory and type:

           tar -cvf part#.tar *
           gzip part#.tar

To submit type(submit will usually be working at least a few days before the due date ;):

           ~????001/Bin/submit # part#.tar.gz

In all cases '#' represents the number of the project part you are submitting(1,2,3 or 4). The filename is not really important; It is important that the file is in .tar.gz format and that your Main.java and other required files are not in a subfolder of the tar file. Subfolders are allowed, such as the cmsc420 package folder. You must include the following with every submission: All necessary source files (*.java etc.) to compile your program. A file called README, all upper case, which contains your name, login id, and any information you would like to add. If you leave out the README your project will fail to submit! There may also be other per project required files that will be checked by the submit program. You are welcome to use a makefile for development (javac doesn't track dependencies very well) but I should be able to run your project with the following two commands:

           javac Main.java
           java Main

No promises are made that I will read your READMEs, but they are useful when problems come up with a project. There is a 100K filesize limit. Please don't include .class files- I will probably strip them out before testing your projects anyway. Every early submission will overwrite the previous early submission, every ontime submission will overwrite any previous ontime submissions, every 1day late submission will overwrite any previous 1day late submission and so on. So I will have one submission for every valid submission period. (Late policy TBA). I will grade every submission that is saved(including applicable bonuses and penalties) and you will get the highest grade among them If there are any errors in my IO you are still responsible for them- the spec is what is in charge. So if you match all my current IO and submit early and then someone points out that I printed the wrong error message for some function, you have to fix your project and resubmit ;) You should be coding to match the command specification, not my sample IO. Here is a (c++) makefile that you might use as a hint for how to set up dependencies for make. Note that that's a TAB before $(CC), and make does care. (You'll get an 'invalid separator' error, or something like that if you use spaces).

CC = cxx
FLAGS =
LFLAGS = -lm

proj4: bpnode.o bptree.o cell.o main.o pmedge.o pmpoint.o  pmquadtree.o util.o
	$(CC) $(LFLAGS) *.o -o proj4

bpnode.o: bpnode.cpp bpnode.h bpdata.h
	$(CC) -c $(FLAGS) bpnode.cpp

bptree.o: bptree.cpp bptree.h bpdata.h
	$(CC) -c $(FLAGS) bptree.cpp

cell.o: cell.cpp cell.h bpdata.h pmpoint.h pmedge.h celledge.h
	$(CC) -c $(FLAGS) cell.cpp

main.o: main.cpp bptree.h cell.h celledge.h pmedge.h pmpoint.h util.h psdraw.h $
	$(CC) -c $(FLAGS) main.cpp                     

pmedge.o: pmedge.cpp pmedge.h pmpoint.h util.h
	$(CC) -c $(FLAGS) pmedge.cpp

pmpoint.o: pmpoint.cpp pmpoint.h pmedge.h
	$(CC) -c $(FLAGS) pmpoint.cpp

pmquadtree.o: pmquadtree.cpp pmquadtree.h pmpoint.h pmedge.h util.h psdraw.h
	$(CC) -c $(FLAGS) pmquadtree.cpp

util.o: util.h util.cpp
	$(CC) -c $(FLAGS) util.cpp

clean:
	rm -f *.o
	rm -f proj4
	rm -f core

Web Accessibility