On Feb 21, 2016, at 1:11 PM, Rakshika Bagavathy
wrote:
> Thanks for the advice. It does seem challenging. And i don't want to promise
> anything that i might not be able to do. So, i think it would be best if i
> went with another project. I went through the project page again and did a
> bi
Hey Sean,
Thanks for the advice. It does seem challenging. And i don't want to
promise anything that i might not be able to do. So, i think it would be
best if i went with another project. I went through the project page again
and did a bit of research on the topics. I'd like to work on the voxeli
You may need to multiply the lengths provided by the user with
gedp->ged_wdbp->dbip->dbi_local2base to get the internally used mm.
(?)
Daniel
2012/8/14 Anurag Murty :
> Daniel,
>
> Thanks a lot for the help! This answered ALL my questions. I was trying a
> out a very complicated method for the
Daniel,
Thanks a lot for the help! This answered ALL my questions. I was trying a
out a very complicated method for the same. This was very helpful. I just
made one change -- I added a "-t" option for the user to be able to modify
the threshold above which a voxel can be considered to be inside.
The attached source file should answer most of your questions.
Complete it with the features you want, polish and test it. Then I
hope you have the calm to move on to write the documentation.
Daniel
2012/8/13 Anurag Murty :
> Daniel,
>
> Thank you for your mail.
>
> There are still quite a few
Daniel,
Thank you for your mail.
There are still quite a few problems though. Firstly, when i use the
voxelize command, I get a set of RPP's in the same directory named
xyz. This leads to a lot of
clutter after I do an "ls" in mged. So I wanted to know if I can somehow
create a sub-directory for
Anurag,
At the first sight your pictures are looking good and with this are a
nice conclusion of your work in the GSoC.
Now, as already mentioned in other posts, you should try to finish
your work this week by updating the documentation, e.g.:
- create a man-page for g-voxel
- document the voxeli
Daniel,
Even i do not see the use of the way I wrote setRegionName now. I will
change the function and also look into the second part where you asked me
to use bu_list.
I will make these modifications and commit.
Thanks and Regards,
On Thu, Aug 2, 2012 at 10:40 PM, Daniel Roßberg
wrote:
> Anur
Anurag,
Two thoughts which came over me while reading through your libanalyze/voxels.c:
1.) Why is setRegionName() so complicated. As far as I can see the vp
parameter is only a dummy. A simple bu_vls_strcpy() should do the
job, shouldn't it?
2.) Why don't you use bu_list in the rayInfo/voxelR
Sean,
I actually moved those functions and committed before I saw this e-mail. So
I might have unnecessarily moved those functions. I will make the suggested
changes, and remember your advice about the naming conventions :)
Thanks you for the detailed review of my code!
Regards,
On Mon, Jul 16, 2
Anurag,
I was looking through the new voxelize command and had a few comments. It's
looking like really good progress but we should make sure we're encapsulating
across library boundaries so we don't end up with an ad hoc API. A few things
I noticed:
1) The three helper/callback functions p
2012/7/5 Anurag Murty :
> Daniel,
>
> I have made the changes you suggested in this mail and also made changes to
> libanalyze, analyze.h as discussed once previously.
> Right now I am trying to understand how to implement a command for this in
> libged.
Maybe you can use ged_facetize() as templat
Daniel,
I have made the changes you suggested in this mail and also made changes to
libanalyze, analyze.h as discussed once previously.
Right now I am trying to understand how to implement a command for this in
libged.
Also, you had once asked me discuss possible output formats for a voxelize
comm
Anurag,
Some thoughts regarding your voxelize() function:
- I would recommend to write the content of struct paramVoxelize as
normal parameters. (BTW, writing “struct paramVoxelize
userParameters;” (no * here) would make the bu_calloc() redundant.)
- The threshold parameter is something for the c
Daniel,
I have changed the g-voxel.c code so that the work is done inside of a
function (Voxelize) that has two input parameters :
1. the raytrace instance rtip
2. a userParameters structure that includes voxelSize in each dimension,
threshold value (what percentage to consider as filled), and out
Anurag,
I would recommend to write the function in g-voxel.c first. Moving it
to a library is easy then.
This function should contain almost all what's contained in main()
now. Think about how its prototype should look like (I think we
talked about it too). Write it down above the main() and m
Daniel,
I have implemented the g-voxel command which outputs the voxel file
according to format once suggested by you. I have also tested the output
for many cases and it seems to work fine. As discussed earlier, you had
asked me to move the functions into a library once I was done with a
working
Hi Sean!
I am presently working on some patches so that I can gain commit access. I
have also begun working on BRL-CAD taking pointers from the tutorial on the
site.
Thanks for the tips, I will do the raytracing commands well now.
Regards,
On Tue, May 8, 2012 at 12:42 AM, Christopher Sean Morris
On May 7, 2012, at 3:01 PM, H.S.Rai wrote:
> On Mon, May 7, 2012 at 10:12 PM, Suryajith Chillara
> wrote:
>> On Monday 07 May 2012 10:02 PM, Christopher Sean Morrison wrote:
>
>>> Anurag, you can ...
>
> Mistaken identity ;-)
Ooops! Indeed, my apologies Suryajith! :)
I was just looking ove
Anurag,
Welcome to the BRL-CAD project! You successfully managed the Google
Summer of Code application process. Now it's time to think about the
coming task. (However, it shouldn't be necessary to write a new
ray-trace algorithm for BRL-CAD. The existing one does quite a good
job ;)
You shoul
20 matches
Mail list logo
