Hello,
A few more doubts!
1. For the NEAR_ZERO function in "common.cl", the epsilon value used should
be *"RT_PCOEFF_TOL"* or *"RT_DOT_TOL"? *Basically, what are these two
different tolerance value for?
2. In the "part", "rhc" and "rpc" codes, in place of "*segp->seg_in"*
and "*segp->seg_out",
hits[0] and hits[1] *are used in the kernels. But in the "*hrt*" code,
these variables are not used. Would it be correct to define these in the
kernels? If yes, should it be linked the same way as in other files?
3. In "common.cl", *'bn_complex_t' *is defined but '*bn_poly_t' *is not.
So I I defined it in "common.cl" itself.
Regards
Shailesh
On Mon, Mar 20, 2017 at 2:37 PM, Vasco Alexandre da Silva Costa <
vasco.co...@gmail.com> wrote:
> On Sun, Mar 19, 2017 at 6:41 PM, Shailesh Tripathi , B.Tech., Electronics
> Engg., IIT (BHU), Varanasi (INDIA) <shailesh.tripathi.ec...@iitbhu.ac.in>
> wrote:
>
>> Hello,
>> While writing the.cl file, I got stuck at a data type "*bn_poly_t*" and "
>> *bn_complex_t*". To use this in kernels, can these definitions be
>> imported or do I need to define these structures in the .cl file itself. Is
>> there a way to import these, or if not, defining them would not be any
>> issue. :)
>>
>
> The necessary types are defined in the include file "common.cl", which
> should also be included in the existing sample primitive implementations
> like 'ehy_shot.cl'.
>
In "common.cl", *'bn_complex_t' *is defined but '*bn_poly_t' *is not. So I
I defined it in "common.cl" itself.
>
> --
> Vasco Alexandre da Silva Costa
> PhD in Computer Engineering (Computer Graphics)
> Instituto Superior Técnico/University of Lisbon, Portugal
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
