Editing User:Sharan.nyn/GSoC18/Report
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 1: | Line 1: | ||
== ''' Project Report : Check Command and Overlaps Tool ''' == | == ''' Project Report : Check Command and Overlaps Tool ''' == | ||
− | + | The work done for the project can be split into the following parts: | |
=== libanalyze function -- analyze_overlaps and libged command -- check_overlaps === | === libanalyze function -- analyze_overlaps and libged command -- check_overlaps === | ||
− | NOTE: This was later replaced with better code | + | NOTE: This was later replaced with better code by me ;) |
* The main goal behind adding a check_overlaps command was that libged's rtcheck command acted as a wrapper for the rtcheck program, and ran the rtcheck program with execvp command -- this was not desired as the execution was done in a different process. | * The main goal behind adding a check_overlaps command was that libged's rtcheck command acted as a wrapper for the rtcheck program, and ran the rtcheck program with execvp command -- this was not desired as the execution was done in a different process. | ||
* I added the check_overlaps command which had the same options as rtcheck command and the logic behind shooting of rays was done in libanalyze. | * I added the check_overlaps command which had the same options as rtcheck command and the logic behind shooting of rays was done in libanalyze. | ||
Line 14: | Line 14: | ||
=== rtcheck based on libanalyze's analyze_overlaps function === | === rtcheck based on libanalyze's analyze_overlaps function === | ||
− | NOTE: This was later replaced with better code | + | NOTE: This was later replaced with better code by me ;) |
* Since the logic for shooting the rays was in libanalyze function analyze_overlaps. | * Since the logic for shooting the rays was in libanalyze function analyze_overlaps. | ||
* My next task was to refactor rtcheck program to use analyze_overlaps. | * My next task was to refactor rtcheck program to use analyze_overlaps. | ||
Line 38: | Line 38: | ||
** [https://sourceforge.net/p/brlcad/code/71151/ r71151] [https://sourceforge.net/p/brlcad/code/71152/ r71152] [https://sourceforge.net/p/brlcad/code/71153/ r71153] [https://sourceforge.net/p/brlcad/code/71154/ r71154] [https://sourceforge.net/p/brlcad/code/71155/ r71155] | ** [https://sourceforge.net/p/brlcad/code/71151/ r71151] [https://sourceforge.net/p/brlcad/code/71152/ r71152] [https://sourceforge.net/p/brlcad/code/71153/ r71153] [https://sourceforge.net/p/brlcad/code/71154/ r71154] [https://sourceforge.net/p/brlcad/code/71155/ r71155] | ||
* Better object selection: [https://brlcad.org/wiki/File:Overlaps_tool2.gif better_object_sel.gif] | * Better object selection: [https://brlcad.org/wiki/File:Overlaps_tool2.gif better_object_sel.gif] | ||
− | * Final image: | + | * Final image: https://brlcad.org/wiki/File:Overlaps_tool_final.png |
− | |||
− | |||
− | |||
− | |||
=== new libanalyze API and check command that uses this API === | === new libanalyze API and check command that uses this API === | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |