Checkoff date and explanation of max points per checkoff. Deductions
for late completion or insufficient work.

9/5  : 4 pts :

     * Webpage 
     * Self-assessment
     * Timely completion 

9/12 : 4 pts :

     * Mock CPU operation description
     * Changing operation of mock CPU to test different addresses / data
     * Finding the location of the max of three
     * Timely completion
     
9/19 (actually 9/21) : 4 pts :

     * Showing VGA circuit working
     * Doing the 'find the location of the largest number' circuit
     * Progress towards assembler / simulator being adequate

9/26 : 4 pts :

     * HW flow-charts as per details requested (details of regs and mux
       settings must be shown)
       
     * Groups making overall good progress (ahead in some
       aspects, for example) offsets some of the negatives earned

10/3 : 4 pts :

     * Walk thru the VHDL files of the thin-slice
     * Project proposal must be online

10/10 : 12 pts :

     * Thin-slice shown working in simulation
     * Webpage updated

OK I won't make date-specific comments for all dates. In general, for all dates:

   * If you see a 'tbd,' it means that the stated task has not been accomplished
   
   * If you see a lower score compared with others, it's very likely that you were late

   * REMEMBER THAT at the very end, you have to turn in a project report. The easiest best way to create an interesting project report is to record
     things that you observed and learned every week on the webpage. This way, you can avoid a 'big crunch' writing session at the end (which
     almost always results in forgotten facts and disorganized reports).

     DOCUMENTATION is key to everyone's success in modern life -- especially so for "budding engineers" such as you !!
   
-- end