Editing User:Clouddrift/GSoC2014/Logs
From BRL-CAD
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 443: | Line 443: | ||
'''Monday, August 11''' | '''Monday, August 11''' | ||
− | + | I skip some codes in BOOL OPERATION to make program 'can' facetize the shifter in toyjeep.g. But it just cut off the main process and not reach the critical parts. | |
'''Tuesday, August 12''' | '''Tuesday, August 12''' | ||
− | + | Compared all files before and after change, I notice the nmg_shell_fuse(sA, tol) and nmg_shell_fuse(sB, tol) before calling nmg_crackshells(sA, sB, tol). The function nmg_shell_fuse remove the repeat elements vertex/edge/edge_g in sA and sB respectively. But in trunk, it's nmg_model_fuse, which acts on the whole model. It means the same elements between sA and sB can also be removed. But in branch nmgreorg, they are not. | |
+ | |||
+ | To restore the original function, I should write another version of | ||
+ | |||
+ | * nmg_vertex_fuse | ||
+ | * nmg_break_e_on_v | ||
+ | * nmg_face_fuse | ||
+ | * nmg_edge_fuse | ||
+ | * nmg_edge_g_fuse | ||
+ | |||
+ | I believe for this reason (sA and sB still have same element such as vertex), it cause the zero-length edge appearance when calling nmg_crackshells. The change is large, I decide to do the movement work (move some files to a new-created nmglib) at first after discuss with mentor. | ||
'''Wednesday, August 13''' | '''Wednesday, August 13''' | ||
− | + | Start the movement work and finish some basic parts. | |
+ | |||
+ | * move all nmg_XXX except a few e.g. nmg.c (becasue it includes import/export functionalities) into libnmg. | ||
+ | * move bspline dictionary into libnmg. | ||
+ | * leave all db relevant files in librt. | ||
+ | * leave all tree relevant files in librt. | ||
+ | * leave basic shapes definition (e.g. rcc sph arb8....) in librt. | ||
'''Thursday, August 14''' | '''Thursday, August 14''' | ||
− | + | Define the NMG_EXPORT just like the RT_EXPORT to make rtlib and nmglib import/export functions correctly when reading include files. But some functions reference each other which makes harder to separate them. | |
'''Friday, August 15''' | '''Friday, August 15''' | ||
− | The | + | The movement method done in Wednesday is wrong because they lose the history. With Sean's lesson, I revert codes to r62036. Then use the right way (svn mv) to do the movement and redo the following operations. |
− | |||
− | |||
− | |||
− | I |