Project 3 Clarifications

Last Updated 2013-06-03

• What To Turn in For Phase B - For phase B please turn in ALL files needed to run versions 1-5. Please submit any extra java files you may have created for testing or otherwise. We will be re-examining your version 1 and 2 code that you submit with phase B, so this is your opportunity to fix any bugs, improve the style of that code, etc. You DO need to submit testing code with phase B. You do NOT need to submit timing code with phase B - you will submit this on Thurs with your writeup - not to be graded, just to help us understand how you did your timing if there are any questions. You DO need to submit any above and beyond items with phase B.
• What To Turn in For Phase A - For phase A please turn in ALL files needed to run your version 1 and version 2. Please submit any extra java files you may have created for testing or otherwise. Phase A turn-in will be graded pimarily on correctness. You will be resubmitting you "final" version of version 1 and version 2 with phase B.

• Cutoffs - Strictly speaking, for functional correctness (which is the main thing we are looking for in phase-A turn-in) it will be fine to NOT have a cutoff at this point. For phase B turn-in, you should put in a cutoff. Note that question 6 in the writeup asks you to perform timing experiments involving different cutoffs.
• Invalid User Inputs - The point of specifying that "Any illegal input (i.e., not 4 integers on one line) indicates the user is done and the program should end." was to avoid specifying (and you having to implement) a complex spec of what to do when they user enters X. It will be fine if you want to be more forgiving and give the user feedback on what was wrong (e.g. "query not in valid range") and another chance then this will also be o.k. Although please do be sure that it IS easy to actually QUIT the program (say by typing a q).