Hello!
So, after updating the volume implementation patch, I started working on
the centroid implementation and I realized I have implemented the grid
shooting code in volume.c, following which could mean that I'll have to
shoot rays again to find the centroid and again for surface area.
So, I'm going to change that design and follow the design shown in the doc
attached. Please tell me if there are any changes required. Sean did tell
me in the beginning that I setup the ray shooting such that I need to shoot
once and the structs filled will be used by the application functions like
volume, centroid, surface area, etc. iirc. My bad, I wasn't careful in the
design before.

Please review it ASAP.

https://docs.google.com/document/d/1WKSH-6MtEAySWZdMa-iy9iVlof1mS4CzA5iehOg5NMw/edit?usp=sharing

With Regards,
Kalpit Thakkar

On Thu, Jul 9, 2015 at 4:33 AM, Christopher Sean Morrison <brl...@mac.com>
wrote:

>
> On Jul 8, 2015, at 2:00 PM, Kalpit Thakkar <ceasy...@gmail.com> wrote:
>
> Which one is to be followed?
> *rt_generic_volume() *calling the libanalyze function for primitives
> having a NULL *ft_volume() *entry
>
>
> libanalyze heavily depends on librt.  librt cannot depend on libanalyze or
> that would introduce a cyclic dependency.  You could push your volume
> implementation down into rt_generic_volume() or leave it in libanalyze
> since it’s a method based on sampling.
>
> One of the users for this generic volume function in addition to the C++
> API will be the analyze command (see src/libged/analyze.c).  Both can call
> into librt or libanalyze.
>
> Cheers!
> Sean
>
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> BRL-CAD Developer mailing list
> brlcad-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>
>
------------------------------------------------------------------------------
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to