User:KeshaSShah/GSoC13/Reports

From BRL-CAD
< User:KeshaSShah‎ | GSoC13
Revision as of 05:17, 19 June 2013 by KeshaSShah (talk | contribs) (Week 1)

Week -1

April 19-22

  • Joined #brlcad channel on IRC
  • Subscribed to mailing list
  • Introduced myself to the community through mailing list
  • Downloaded Source Code
  • Compiled it successfully from the source using cmake
  • Made an account on SVN.
  • Had a glance at source folder and caught my eyes on an instance of duplication.
  • Made first patch and submitted it.
  • Looked through project ideas and found Code Refacoring most interesting and suitable for me.

April 23-30

  • University Final Exams

May 1

  • Checked out some TODO task in the domain of Code Reducing and Refactoring.
  • Picked up moving LIBWBD comments.
  • Used the grep command to find out the comments that needed to be moved.
  • Within just 10 minutes, I was able to successfully move all comments and submitted another patch
  • Discussed with Sean about my interest when he encouraged me to explore converting and processing geometry.

May 2

  • Read tutorial I and then tutorial IV on Converting Geometry and recieved some basic idea on STEP and other convertors available for importing and exporting between different CAD softwares.
  • Gone through project ideas again and liked two more ideas-namely Improving STEP Library and STEP AP242 Parser.

May 3

  • Proposal Submission Deadline on melange.
  • Made my User-Wiki-pages
  • Uploaded proposal on Melange and embedded wiki links in it.

May 4-5

May 6-8

  • Picked up Issue #47 to work upon.
  • Made a list of differences between pair of 13 similar files.
  • Untangles some calls from src/fedex_plus to src/clstepcore.
  • Discussed on IRC about the errors I encounter.
  • Read about how calls are made, maintainence of call-stack heap, the process of linking and Compiler warnings
  • Overall, have got some better understanding.

May 9

  • Installed doxygen and looked up some example codes.(for documentation part)
  • Made a test-bot for IRC #stepcode (it functionalities still remaining to be discussed with mentors.)

May 10-11

  • Read from some references and manuals and gone through cheat-sheet for learning GIT and GITHUB. (add, branch, commit, push, pull, reset, log etc.)
  • Installed gitk and used it.
  • Assigned #47 issue to myself.
  • Made a branch and committed and push the removal of 5 similar functions.
  • Revised some concept like virtual, pure functions, friend functions, use of const and static, extern etc.
  • Discussed with Mark for logs and bot of #stepcode on IRC
  • Reading doxygen manual.

May 12

  • Almost done with issue #47. Pushed the commits on branch ks-duplicate-files.
  • Known about the Debugger gdb- used back-trace feature.
  • Quick Guide to gdb Debugger.
  • Installed KDevelop IDE and planning to use it as it has nicer gdb GUI wrapper.

May 13-14

  • Getting "Abort (core dumped)" error. Pushed it to a new branch for Mark to review it.
  • Picked new issue #200.

May 15

  • Got Doxygen working correctly and tried few samples. Read manual to see how to comment.

May 17

  • Surfed for lazy-loading. Reading the process of loading (ch 7) of Bryant book.

May 18-May 26

Week 0

May 27

  • Accepted Students announced on Melange. Yupiie, selected ! :)

May 28-June1

  • I fully confirm and accept the stated participation requirements including giving full rights to my contributions, remaining visibly active, being engaged in discussion, providing regular updates on progress, complying with the development rules, and writing excellent code.
  • Reading Hacking Guide.
  • Will be returning on 5th June from di's marriage
  • Next Target: Obtain commit access till 17th June (before gsoc program begins)

June 2-June 16

  • Community Bonding Period.
  • Preparation of Release 7.24.0 - Release Note

Week 1

June 17

  • Worked upon Issue 21: Removed 100 warnings, errors and styles shown by cppcheck from about total 455.
  • I ran "rm -r *" from stepcode/ instead of build/, and cloned the repo again in stepcode/ through which I lost all my progress. Thanks to git cherry-pick command, through which i recovered it back ! #sighofrelief

June 18

  • Looked upon 100 more cppchecks to solve Issue 21.
  • Strangely, many cppchecks claimed wrong warnings. Like, a warning says, the varaible was not used, but in later part of the code, it was actually used.
  • Learnt "Be careful, don't believe warnings blindly unless you look upon code".
  • Github issue - The branch I am working doesn't have master changes, so after this issue completes, I will clone repo again and use the freshly cloned directory's .git/ folder.
  • IRC log.

June 19