User:Clouddrift/GSoC2014/Logs

Community Bounding Period

Get the commit access

Submit two patches for nmg part of BRL-CAD. URLs as following.

• Unit test for nmg_mk

• Unit test for nmg_copy

Read the relavant Codes

Read and be familiar with nmg-related codes in BRL-CAD.

Acquired knowledge

• Keep code style consistent is important for Open Source Community.

• Comments greatly helps others to understand the function of routines and structs. Codes should be changed before fully tracking the call order of routines and totally understanding the comments of them.

• That's a really good ideas to submit one or two patch to know the coding convention of the community. As a chinese saying goes, sharpening your axe will not delay your job of cutting wood.

Work Perod

Week 1

Monday, May 19

Read TODO, HACKING, COPYING and other files again. Be ready for formal coding job.

Tuesday, May 20

Find and read some pages about the details in using SVN and CMake.

Wednesday, May 21

Get the commit access for BRL-CAD successfully. What a day to celebrate! Now, I begin my work on a branch for NMG reorganization. Remove model and nmgregion struct, Then ready to fix all compilation errors.

Thursday, May 22

Rewrite nmg struct to fit BRL-CAD better. Remove model and nmgregion struct, Then change shell struct as following.

• remove member: l (bu_list);
• remove member: r_p (nmgregion pointer);
• add member: magic (uint32_t);
• add member: manifolds (char pointer);
• add member: maxindex (long);

Friday, May 23

Fix the rest compilation errors due to fit the new nmg structure. The code files are corrected as following.

• nmg_ck.c;
• nmg_class.c;
• nmg_copy.c;
• nmg_eval.c;
• nmg_mk.c;
• nmg_info.c;
• nmg_plot.c;
• nmg_pr.c;
• nmg_tri.c;

Saturday, May 24

Waiting for update.

Acquired knowledge

• Committing without breaking the build is always the best choice. Try to use comment to achieve this point and record such codes in TODO file for fixing later.