Converting .g files with g2asc. Our program reads this ASCII version of
the .g file and works on it. Don't ask ;)
On Thu, Feb 20, 2014 at 9:50 PM, Christopher Sean Morrison
wrote:
>
> On Feb 20, 2014, at 7:31 PM, Daniel Hyams wrote:
>
> > Tough one, because I've had a really hard time finding
On Feb 20, 2014, at 7:31 PM, Daniel Hyams wrote:
> Tough one, because I've had a really hard time finding documentation that
> helps with the API's. The doxygen docs are there, but they haven't really
> been that much help to me.
*nod* We're actively working on this (comment migration, Doxyg
Tough one, because I've had a really hard time finding documentation that
helps with the API's. The doxygen docs are there, but they haven't really
been that much help to me.
I'd say in the raytrace.h file, I would have possibly found it. I know
that's still kind of an out-of-the-way place, but
On Feb 20, 2014, at 5:21 PM, Daniel Hyams wrote:
> Excellent, thanks Sean! I'm not really a modeler, but a developer using the
> ray tracing API's. I got confused when I was testing (with both my ray
> tracer and rtweight), because I thought that the "units" entry in the .g file
> told how t
Excellent, thanks Sean! I'm not really a modeler, but a developer using
the ray tracing API's. I got confused when I was testing (with both my ray
tracer and rtweight), because I thought that the "units" entry in the .g
file told how the numbers should be interpreted. Now that I see that this
is
On Feb 20, 2014, at 4:05 PM, Daniel Hyams wrote:
> Thanks Sean! I think the problem is my lack of understanding concerning how
> BRL-CAD stores its data. I think you're implying that BRL-CAD always stores
> its data in a particular unit (mm), so the "units" attribute of a .g file
> doesn't m
Thanks Sean! I think the problem is my lack of understanding concerning
how BRL-CAD stores its data. I think you're implying that BRL-CAD always
stores its data in a particular unit (mm), so the "units" attribute of a .g
file doesn't matter except as a convenience to the modeler when creating
new
On Feb 20, 2014, at 2:55 PM, Daniel Hyams wrote:
> It seems that if I have a model file (I was using a sphere as an example),
> and run
>
> rtweight modelfile.g all.g
>
> I'll get a certain mass. But if I then change the units in the model file,
> and run again
>
> rtweight modelfile.g all.
It seems that if I have a model file (I was using a sphere as an example),
and run
rtweight modelfile.g all.g
I'll get a certain mass. But if I then change the units in the model file,
and run again
rtweight modelfile.g all.g (with the same .density file as before)
I still get the same mass.
