Editing Analysis Library
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 3: | Line 3: | ||
libanalyze is a BRL-CAD library intended to provide a unified, organized API for analytical raytracing functionality. A proposal on this topic should review the functionality provided by the above tools, outline an API that would encapsulate and expose the core functionality, and specify testing procedures to ensure correctness of the results (analysis accuracy is very important for BRL-CAD, so checking the results is key). It may not be practical to actually implement all the libanalyze routines needed to provide full coverage of all the tools' functionality, so a student should identify core useful procedures (for example, g_qa uses three axis aligned grids of rays while rtcheck uses one grid that fires from the "view plane" in MGED - a logical API for this would be to use librt's ray bundle abilities (or enhance them if it can't produce the grid shapes currently) and provide a function that takes as arguments a view plane, mins and maxes within the view plane, and grid density of rays.) | libanalyze is a BRL-CAD library intended to provide a unified, organized API for analytical raytracing functionality. A proposal on this topic should review the functionality provided by the above tools, outline an API that would encapsulate and expose the core functionality, and specify testing procedures to ensure correctness of the results (analysis accuracy is very important for BRL-CAD, so checking the results is key). It may not be practical to actually implement all the libanalyze routines needed to provide full coverage of all the tools' functionality, so a student should identify core useful procedures (for example, g_qa uses three axis aligned grids of rays while rtcheck uses one grid that fires from the "view plane" in MGED - a logical API for this would be to use librt's ray bundle abilities (or enhance them if it can't produce the grid shapes currently) and provide a function that takes as arguments a view plane, mins and maxes within the view plane, and grid density of rays.) | ||
− | + | Requirements: | |
− | * | + | * Familiarity with C |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | Difficulty: hard | |
− | |||
− |