BRL-CAD provides a couple dozen distinct primitives. Each primitive is defined by a set of parameters. We'd like to have each primitive modeled with diagramming arrows and labels.
This task involves creating a hyperboloid of one sheet (HYP) and modeling the corresponding arrows/segments for all parameters. Scalars should be dashed lines, vectors should be arrows. Here's an example:
- http://brlcad.org/~starseeker/gci_primitive_figures/
Make something like that for the HYP, but with different material properties. That example put objects into a box for a particular visual effect. See if you can get a better effect without the exterior box (you'll have to change shader properties).
Submit your .g file and a ray traced rendering/diagram of the model. This command run within mged may help:
rt -s1024 -A0.75 -c {set ambSamples=128}
| File name/URL | File size | Date submitted | |
|---|---|---|---|
| HYP.g | 8.6 KB | December 18 2012 17:27 UTC | |
| HYP.PNG | 38.7 KB | December 18 2012 17:33 UTC | |
| labels.jpg | 111.2 KB | December 18 2012 18:46 UTC |
I would like to work on this task.
This task has been assigned to Sharan. You have 48 hours to complete this task, good luck!
I created the lines,spheres and arrows.
Everything but HYP is not raytraced.
Dont know why
The work on this task is ready to be reviewed.
hyp is traceable when its blasted alone
I read about hyp on your site-
http://brlcad.org/wiki/User:Pacman87
on 2008-06-04
that hyp is not traceable.I tried RT also but no luck.
I managed to get a raytraced image with the lines, spheres, arrows and labeled them in the labels.jpeg.
Still hyp is not traceable.
Used photoshop to combine two images and labeled them
The HYP is one of our newest incomplete primitives and you've apparently discovered a bug of some sort. I was able to reproduce the strangeness. Intersections and unions seem to behave just fine, but any subtraction produces an incorrect result. You get a task just for reporting the bug with a repeatable input. Thanks!
Congratulations, this task has been completed successfully.
A follow-on task has been posted to fix the bug observed and documented here:
http://www.google-melange.com/gci/task/view/google/gci2012/8105204