Menu
Logged-In As
ACCOUNTNot Logged In
Create a VOL wiki pageBRL-CAD
Status: ClosedTime to complete:
100 hrs
Mentors: Kesha Shah, Ch3ck
We have wiki pages for many of our more complex 3D objects, but we don't currently have one for our "VOL" volumetric primitive.
You can see examples of other primitive info pages here:
- http://brlcad.org/wiki/EBM
- http://brlcad.org/wiki/Sketch
- http://brlcad.org/wiki/DSP
This task involves writing a similar overview page on our wiki at http://brlcad.org/wiki/VOL
You'll obviously need to learn how to create a volumetric object in one of our geometry editors. Some pointers to get started are to run mged and run the "in" command to create a vol primitive interactively.
References:
- http://brlcad.org/wiki/MgedFAQ
- http://brlcad.org/w/images/c/cf/Introduction_to_MGED.pdf
- http://brlcad.org/w/images/5/52/MGED_Quick_Reference_Card.pdf
Uploaded Work
File name/URL | File size | Date submitted | |
---|---|---|---|
http://brlcad.org/wiki/VOL | n/a | December 04 2014 06:50 UTC |
I would like to work on this task.
This task has been assigned to Michael Huang. You have 100 hours to complete this task, good luck!
The work on this task is ready to be reviewed.
Hi, I wrote a page for the VOL primitive ( http://brlcad.org/wiki/VOL ), but I ran into a crash that I couldn't get around. I think what I did was correct (or at least not crash-inducing), but of course I'm not sure. The data file seems to be the right size (256 x 256 x 113 = 7405568 bytes).
The guide is practically complete... if you ignore the failure at the end.
The tutorial looks pretty good up until the end.
Are you working on windows? Your procedure had the same error when I used windows, but it worked fine in a FreeBSD environment. Join us on IRC at #brlcad (http://brlcad.org/wiki/IRC) and we can work out these issues.
One of the mentors has sent this task back for more work. Talk to the mentor(s) assigned to this task to satisfy the requirements needed to complete this task, submit your work again and mark the task as complete once you re-submit your work.
There are less than 24 hours left until the deadline, please submit your work soon.
The deadline of the task has been extended with 1 days and 0 hours.
There are less than 24 hours left until the deadline, please submit your work soon.
The deadline of the task has been extended with 1 days and 0 hours.
Thanks for extending the deadline.
I've tried my guide using BRL-CAD 7.24.2 in FreeBSD, Windows, and Ubuntu, but I've run into the same error at the end each time (http://brlcad.org/w/index.php?title=VOLoldid=7821 ).
I'm not sure what I can do to get it to work, so would it be possible for somebody else to try running it? The guide is complete, but I'd like to make sure it can work and would like to add a render to the page.
There are less than 24 hours left until the deadline, please submit your work soon.
How far have you been ? Update us here. If you need some time, I can extend by some hours. Its less than 20 hrs remaining.
At this point, I don't know what else I can try for BRL-CAD to not crash. I've also tried asking the IRC channel at a few different times during the past few days, and I asked here too for someone to try running it, but I have not received a response. I'm sure I've done something wrong on my end, but I don't know what I can do about it because of this.
I'm not really sure what else I can do, so I think I'll just resign to submitting the guide as it is, without an image.
The work on this task is ready to be reviewed.
Congratulations, this task has been completed successfully.
Michael, my apologies -- I wrote a reply to you a couple days ago, but for whatever reason it apparently didn't post. Basically, if you ran into crashes, that's on us.
Even if you fed bad inputs, it shouldn't crash -- it should give you a very stern message saying you messed up and that it's halting voluntarily (for example). ;)
If you want to try and fix the crash, that would be a good GCI task in itself. Simply reporting this as a new bug is worthy of a task too (but you'll need a little more info like a backtrace crash log). Let me know, and we can have either created for you. You could also report it to our bug tracker as confirmed with simple details on how to reproduce and it'd easily count towards one of the "confirm a bug report" tasks we already have posted.
Regardless, this looks like a good start to the article as any. Thank you for your efforts!
Thanks for the info! It was really stressing me out.