Difference between revisions of "User:Sharan.nyn/GSoC18/Report"
From BRL-CAD
Sharan.nyn (talk | contribs) |
Sharan.nyn (talk | contribs) (→libanalyze function -- analyze_overlaps and libged command -- check_overlaps) |
||
| Line 2: | Line 2: | ||
The work done for the project can be split into the following parts: | 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 === | ||
| + | * 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. | ||
| + | * The overlaps were processed on libged side with callback functions. | ||
=== rtcheck based on libanalyze's analyze_overlaps function === | === rtcheck based on libanalyze's analyze_overlaps function === | ||
Revision as of 05:08, 10 August 2018
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
- 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.
- The overlaps were processed on libged side with callback functions.
