Changes

#* finish any documentation steps if left.

#* finish any documentation steps if left.

#* After coding, this is the most interesting part for me. Past I have also worked on code coverage tools for python and I really like this <br> efficency measurement whicha also helps a lot in improving run-time. I will go for different testing tools on program, Some tools I would like<br> to go with

#* After coding, this is the most interesting part for me. Past I have also worked on code coverage tools for python and I really like this <br> efficency measurement whicha also helps a lot in improving run-time. I will go for different testing tools on program, Some tools I would like<br> to go with

#*coverage or flegleaf tools for anlaysis. <br>

#*coverage or flegleaf tools for anlaysis.<br>

#*I will use boost algorithms to improve run-time if it comes under requirement. I have been using CPYTHON for coding competitions and familiar <br>

#*I will use boost algorithms to improve run-time if it comes under requirement. I have been using CPYTHON for coding competitions and familiar<br>

with different tweaks to modify run time such as psycho module. This will help in increasing the robustness and stability of program.

with different tweaks such as boost , psycho etc. to modify run time. 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