____________________________________________________________________________

CSEE E6861y						        Handout #23d
Prof. Steven Nowick  					      March 15, 2016 
____________________________________________________________________________
____________________________________________________________________________

                            Midterm CAD Project
   
                  ========================================	
                  Writeup, Submission and Demo Information
	          ========================================	

---------------------------------------------------------------------------

=================
#1. Demo Schedule
=================

You will need to schedule a demo with the TA after the submission deadline
on 3/28. Both of the teammates in a group-of-two have to show up.

The demo will be held on Tuesday 3/29 and Wednesday 3/30, in the TA room, 
which is 30 minutes long for each group. The signup is 
first-come-first-serve based on Doodle Poll, to be released shortly.

----------------------------------------------------------------------------

===============
#2. Demo Format
===============

The demo will be running both on examples provided to you in this handout,
as well as 1~2 new examples. Also, you should be prepared to answer some basic
questions related to your program.

You will run the program on your own computer during demo session. Therefore, 
you should pre-setup the environment on your own computer beforehand. As a
reminder, the TA will be using your submitted code for his final grading runs.

Basically, you are to show how to run your program and how good/robust your
program is. Also, you can highlight any interesting findings/algorithms during
the demo. There is no grade assigned to the demo session, but a 5% deduction on
this problem will be applied if you do not show up. 

----------------------------------------------------------------------------

=========================================
#3. Project Writeup:  Requirements/Format
=========================================

You should include a *3~6 page writeup*, which includes

(i)   group members (full names)

(ii)  an introduction (overview) of your tool, including:
 
    - a summary of programming information (not too detailed; please include
      the more detailed programming information in the README file (see 
      below, #4) (about 1/2 to 1 page);

    - what function is implemented in your tool, etc.
   
(iii) a clear explanation of the data structures used, and information on
algorithms/strategies and optimizations that you did (about 1 to 2 pages);

(iv) what test you have done to your program, including what
examples you have chosen and why; what problem you found and how you fix it.
Do not include a print of complete output file if not necessary (1 to 2 pages);

(v) any additional observations, findings or important insights that you would
like us to know (1/2 to 1 page).

A succinct and clear write-up is preferred to a long vague one. But of course,
you are welcome to give a longer write-up if you have more to say.

You should aim for a clear and professional summary, organizing your structure
and content before starting to write.

----------------------------------------------------------------------------

======================
#4. What/How to Submit
======================

You are expected to hand in:
(i) By email (to kbhardwaj@cs.columbia.edu) -- A tar file containing 'source
code' and 'executables' with a README in it. README file should include:

  a) GROUP MEMBERS:  full names

  b) DETAILED PROGRAMMING INFORMATION:  programming language, platform
     requirements, etc.

     This should include:

       - Which platform you worked on (if you used CLIC/ACIS)
       - The compilation instruction (not all C compilers are compatible)
       - How to compile and run your tool, and any input arguments
       - Where the input/output files will be expected
       - what commands can be used

  c) MISCELLANEOUS:  any clarifications, information on what you didn't do, etc.

Basically, TA will re-compile your program based on the instruction you
provided and run your program when grading.

(ii) printed write-up handed in to TA/professor's office by deadline --
hardcopy


----------------------------------------------------------------------------

====================
#5. Grading Criteria
====================

The project will be graded on:

(i)   correctness of your program's output (about 80%)
(ii)  write-up (about 10%)
(iii) the quality of the whole project, including
     -how easy-to-use and clear your program is
     -any good optimizations done to improve the algorithm
     -other interesting features, etc. 
       (about 10%)

----------------------------------------------------------------------------

If you have any questions, please contact Professor or TA.