Editing Deuces
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 119: | Line 119: | ||
| | ||
| + | {| style="background-color:#fefefe; border-style: solid; border-width: 4px;" width="100%" | ||
| + | | style="padding: 20px;" | | ||
| + | === Debug and fix a bug converting cylinders === | ||
| + | |||
| + | BRL-CAD has many 3D object types, one of them being a "Right Hyperbolic Cylinder". If you run MGED with "mged -c cylinder.g", then run "make rhc rhc" on the mged> command prompt, it will create one. If you then quit mged and run "dbupgrade -r cylinder.g" and reopen the file with "mged -c cylinder.g", the rhc object will be corrupted (try running "l rhc" in mged before and after). | ||
| + | |||
| + | This task's goal is to reproduce, identify, and fix the bug so that the rhc object doesn't get corrupted. To do this, you'll want to use a debugger like lldb or gdb or Visual Studio (there are tutorials all over the web if you've never used a debugger), or simply use print statements. | ||
| + | |||
| + | See the rt_rhc_import5(), ..export5(), .._import4(), and .._export4() functions as they implement the read/write support. | ||
| + | |||
| + | Code: | ||
| + | * src/librt/primitives/rhc/rhc.c, <- you'll probably need to modify this file | ||
| + | * src/librt/primitives/table.c | ||
| + | * include/rtgeom.h | ||
| + | |||
| + | | ||
| + | |} | ||
| + | | ||
{| style="background-color:#fefefe; border-style: solid; border-width: 4px;" width="100%" | {| style="background-color:#fefefe; border-style: solid; border-width: 4px;" width="100%" | ||
| Line 148: | Line 166: | ||
Implement this function: | Implement this function: | ||
| − | int estimate_volume(struct db_i *dbip, | + | int estimate_volume(struct db_i *dbip, struct directory *dp, size_t min_samples, double confidence); |
| − | |||
| − | |||
| − | |||
| − | For this function, you'll want to read up on some of BRL-CAD's basic data structures by looking at headers in the include/rt directory or by reading our | + | For this function, you'll want to read up on some of BRL-CAD's basic data structures by looking at headers in the include/rt directory or by reading our API documentation. Calling rt_db_internal() and rt_bound_internal() will get you the bounding box around geometry from which you can calculate a bounding sphere. Once you have the bounding sphere, randomly generate a set of min_samples*2 points on the surface of the sphere. Shoot a ray through those points using rt_shootray(), as in the ray tracing [[Example_Application|example]]. Keep track of a volume estimate and keep shooting sets of min_samples rays until the estimate is less than the specified confidence value. Volume of a sphere is (4/3 * pi * r^3) so dividing that by num_samples and multiplying all hit thicknesses by that factor is a preliminary method for calculating a running volume estimate. |
References: | References: | ||
| Line 160: | Line 175: | ||
* https://stackoverflow.com/questions/9600801/evenly-distributing-n-points-on-a-sphere | * https://stackoverflow.com/questions/9600801/evenly-distributing-n-points-on-a-sphere | ||
* https://karthikkaranth.me/blog/generating-random-points-in-a-sphere/ | * https://karthikkaranth.me/blog/generating-random-points-in-a-sphere/ | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| | ||
| Line 243: | Line 212: | ||
Reference: | Reference: | ||
* Come [https://brlcad.zulipchat.com talk with us] to make sure you get a copy of the latest version. | * Come [https://brlcad.zulipchat.com talk with us] to make sure you get a copy of the latest version. | ||
| − | |||
| − | |||
| − | |||
| | ||
| Line 253: | Line 219: | ||
{| style="background-color:#fefefe; border-style: solid; border-width: 4px;" width="100%" | {| style="background-color:#fefefe; border-style: solid; border-width: 4px;" width="100%" | ||
| style="padding: 20px;" | | | style="padding: 20px;" | | ||
| − | |||
=== Translate "Contributors Guide To BRL-CAD" To Any Language === | === Translate "Contributors Guide To BRL-CAD" To Any Language === | ||
| Line 488: | Line 453: | ||
Building on the previous GCI task work, take it to the next step. Try setting a vector to 1/3, 1/3, 1/3 and 0.1, 0.1, 0.1 and get proper values to print. Change the V3ARGS() macro if needed. If that all works, try to get bn_dist_pt3_pt3() to work. Report and discuss your progress. | Building on the previous GCI task work, take it to the next step. Try setting a vector to 1/3, 1/3, 1/3 and 0.1, 0.1, 0.1 and get proper values to print. Change the V3ARGS() macro if needed. If that all works, try to get bn_dist_pt3_pt3() to work. Report and discuss your progress. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| | ||
