Research Project
Draft Deliverable
You must submit all of your current code and supporting files as well as a progress report as a 2-5 page PDF. The progress report should explain in detail 1) what you have done, 2) what obstacles your have encountered, 3) what modifications (if any) you wish to make to your original design proposal, and 4) how you plan to wrap up work on the project before the final deliverable due date.
If your group has been using online source control (e.g., Github) just include the repo URL at the top of your report. Additionally, if you worked entirely in your scratch folder on the cluster, you can just mention that at the top of your report and I will use that folder as your submission (try to clean it up a bit first!). Otherwise, submit your code as a zip file on Canvas.
Make sure your repository, folder, or zip contains all relevant source code and instructions on how to build and run it (Makefile and/or automated test script preferred!). Unless otherwise arranged, your code should compile and run on the cluster. If your program requires any data sets, make sure you include these as well. If they are larger than a few MB, please put them in your project-specific folder inside /scratch instead of uploading them to Canvas.
NOTE: I will attempt to reproduce your results, and if I am unable to do so
this may negatively affect your grade. Please make it as easy for me to
reproduce your results; e.g., by providing automated testing scripts or detailed
instructions in a README.txt or your report.
In addition to all the above, and in order to help me advise you more effectively, please include explicit answers to the following questions at the top of your report:
- In exactly ONE sentence, describe as precisely as possible your group's expected contribution to the field. In other words, what exactly will you give to the world of parallel and distributed systems that it didn't have before as a result of your project?
- How do you feel the project is going so far in general? Please provide a score from 1 to 5 where 5 is excellent, 3 is OK, and 1 is terrible.
- How urgently do you need feedback on this deliverable? Please choose one
one of the following options:
- Urgent - We REALLY need feedback ASAP in order to make more progress.
- Normal - We need feedback, but we know where we are and how to keep making progress for now.
- Non-critical - We have a good handle on the project and don't need quick feedback at this point.
- How effectively is your group finding meeting times and getting work
done? Please choose one of the following options:
- Great - No issues.
- OK - Some obstacles, but we're overcoming them.
- Rough - Some obstacles, and we're having difficulty overcoming them.
- Problem - Major obstacles that we need to talk about with you soon.
- Do you have any specific questions you'd like me to answer as part of your evaluation?
This submission will be graded on its correctness, completeness, thoroughness, and scope. Because every project is different, it is impossible to provide a single rubric. Each submission will be graded based on its individual merit and how well you have made progress toward the final deliverable as anticipated in your proposal document. I will provide some written feedback and assign you an overall letter grade for this submission according to the following rubric:
- A - Exceptional: Excellent progress w/ no major concerns.
- B - Good: Significant progress, but with some minor concerns.
- C - Satisfactory: Significant progress, but with major issues and/or concerns.
- D - Deficient: Lack of significant progress -- intervention required.
- F - Unacceptable: Lack of a good-faith effort -- intervention required.
The goal of this submission is to make sure you are on track to submit the final version when it is due. I would also suggest reading the final deliverable grading rubric as a guide to what I will be expecting for that submission as you work on this one. Finally, you should also update your poster deliverable (see the poster guidelines).