On Tue, Jun 7, 2016 at 8:41 PM Christopher Sean Morrison <brl...@mac.com>
wrote:
>
> It's called automatically when you invoke through any of the rt* tools and
> is manually in each saveview script as a simple "end;" directive. The
> command table translates the "end" string into a call to cm_end() via
> rt_do_cmd() which is called by the -c single command option handler and the
> -M stdin mode.
>
> That's a long way of saying that you shouldn't need to be directly calling
> cm_end() so you might be doing or understanding something else wrong?
>
> Yup, I realized that it is indeed automatically invoked. Most of the code
in primitive_util.c is written for lightmodel=5. To test my code, all I had
to do was call the rt binary with -l5 option. Trying to invoke cm_end()
manually was indeed unnecessary.
>
> Thanks a lot! Any leads on how to use the partition list output by
>>> boolfinal()? I'll need to convert this back into an array of segs to be
>>> further processed.
>>>
>> Can I just copy inhit and outhit directly for every partition in the
>>> list? To be honest, I'm little unclear about the difference between a
>>> partition and a segment.
>>
>>
> Be sure to read rt/boolweave.h as well as rt/shoot.h, rt/ray_partition.h,
> and rt/seg.h where it describes the role of segments and partitions.
>
> I had briefly looked at these files during the bonding period and found
things a little confusing. I'll have a thorough look at them now.
Another thing I realized is that while attempting to call boolweave() and
boolfinal(), I'm replicating a lot of the code written in librt/shoot.c.
This is because the structures used by GPU and CPU storage of segments are
a little different (CPU storage of course is more elaborate). The soltab
pointer in CPU seg structure is proving to be specially troublesome. Is it
vital that I replicate everything? And is there a more elegant way of
achieving this?
Best,
Param
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
