Changes

Jump to navigation Jump to search
44 bytes removed ,  08:48, 3 April 2009
no edit summary
Line 69: Line 69:  
==== Technical Approach ====  
 
==== Technical Approach ====  
 
Below is the rough draft, it talks about the implementation in abstract way just to share the idea of implementation.
 
Below is the rough draft, it talks about the implementation in abstract way just to share the idea of implementation.
 
+
http://students.iiit.ac.in/~puneet_g/marbles.png
 
  −
        Marbles: Flow data diagram ( http://students.iiit.ac.in/~puneet_g/marbles.png )
        Line 104: Line 102:  
#* After coding, this is the most interesting part for me. Past I have also worked on code coverage tools for python and really love to <br>
 
#* After coding, this is the most interesting part for me. Past I have also worked on code coverage tools for python and really love to <br>
 
analyze the efficency of program. I will go for different testing tools on program, Some tools I would like to go with
 
analyze the efficency of program. I will go for different testing tools on program, Some tools I would like to go with
##* coverage
+
#* coverage
##* I will use boost algorithms to improve run-time if it comes under requirement. I have been using CPYTHON for coding competitions and <br> familiar with different tweaks to modify run time such as psycho module. This will help in increasing the robustness and stability of program.
+
#* I will use boost algorithms to improve run-time if it comes under requirement. I have been using CPYTHON for coding competitions and <br> familiar with different tweaks to modify run time such as psycho module. This will help in increasing the robustness and stability of program.
 
#Finalizing phase / Revision ( Time: from August 1 to END. )
 
#Finalizing phase / Revision ( Time: from August 1 to END. )
 
#* review of code/ algorithm
 
#* review of code/ algorithm
122

edits

Navigation menu