On Mon, May 16, 2016 at 3:08 PM, Param Hanji <param.catchch...@gmail.com>
wrote:
>
> On Mon, May 16, 2016 at 6:01 PM Vasco Alexandre da Silva Costa <
> vasco.co...@gmail.com> wrote:
>
>> http://brlcad.org/wiki/User:Catchchaos/GSoC2016/Proposal
>>>
>>> It's very similar to my original proposal that I had submitted. Have a
>>> look and let me know if you feel any changes are required.
>>>
>> The proposal looks fine. The question is how can we do the unit testing.
>> It would be nice if you had a simplified ANSI C version (this can be
>> extracted from the existing BRL-CAD code) for each step before coding the
>> OpenCL prototypes. In this way you could detect any issues early on in the
>> implementation.
>>
>
> By simplified version, do you mean something like the one you provided for
> shoot.c in the other thread? And what kind of errors are we looking for?
>
You could basically copy the segments list results from clt_frame() to the
CPU side and then process the list with ANSI C rt_boolweave and
rt_boolfinal. Then send the processed results from the CPU back to the GPU
side for rendering.
Then when you implement rt_boolweave and rt_boolfinal on the GPU side in
OpenCL you can compare your results with the CPU side results to make sure
they are correct.
Regards,
--
Vasco Alexandre da Silva Costa
PhD in Computer Engineering (Computer Graphics)
Instituto Superior Técnico/University of Lisbon, Portugal
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
