Status Report for Week 1: Submitted on 31-May-2010
The status reports serve two purposes. They help your mentor evaluate your progress and help you stay on schedule. They also help you write your midterm and final reports which will summarize these reports. You can create a report at the beginning of the week and update it during the week or create it at the end of the week. Updating throughout the week will ensure you don't forgot anything and will minimize the time spent on the weekly reports.
Accomplishments
Describe what you accomplished this week. Briefly summarize in the first paragraph then add more detail for each task or subtask enumerated on the main summary page. This is your main record of accomplishment so feel free to put as much detail as you would like including links/checkin IDs for code submitted to github. You mentor will review the accomplishments sections when writing your midterm and final evaluations.
Plan for Next Week
Describe what you plan to accomplish next week. Briefly summarize in the first paragraph then provide a little more detail for each task or subtask enumerated on the main summary page. You don't need a lot of detail here. This just helps you and your mentor to plan your week and helps you keep your schedule.
Problems Encountered and Lessons Learned
You should list any problems you've encountered here. List problems which have been solved as well as a brief description of the solution. This section will help you and other Opticks developers by providing lessons learned so problems are not repeated. You should also include unresolved issues so your mentor is aware of these problems. If you are slipping off schedule, make your you bring this up and try and list reasons you are off schedule. If necessary, the schedule can be updated to account for schedule slips.
Other Items of Interest
Talk about anything else you want to mention which does not fit in the other sections.