>
> After it’s working, that’s the next logical step. Don’t want to
> scope-creep the complexity prematurely, but we will eventually want
> material objects defining the density (and other) material characteristics
> of an object (as a replacement for .density files and _DENSITY objects).
>
Sure. We should just try to make sure that what we build now is easily
deployable there. But I guess we will apply the same philosophy you
mentioned before: just go for it because the easy steps now make the
difficult steps possible.
The point of 0 points (hah) first is just to make sure the full range is
> covered. Someone will eventually figure out a way to set/delete/create 0
> points and the code should handle the edge case gracefully, sensibly.
>
Sure, I'll try to 'gracefully' handle the edge cases. I have an idea in
mind that I hope will be a good way to handle this.
> I don’t think we want to create some implicit behavior that we’d have to
> document somewhere. If there’s only one density point, it emanates
> outwards in all directions (i.e., a constant field). That’s not unlike the
> current material ID value which sets the density.
>
Agreed.
> The main consideration would be defining what does a density point outside
> the model means.
>
For this special case you mention, I would just calculate the density like
we normally would, as long as the point where we are asking for the value
is in fact inside geometry. The point can perfectly be influenced by
vectors that go far outside the geometry itself if that was the way the
user decided to define it, as long as it is inside geometry.
They can be handled only if the bounding volume does not contain any
> interior points. If there are interior points, like your example of a rod
> with density going up/down, it’s going to be different (and that’s what was
> deferred for later, to not waste time on the most complex general case).
>
You are right. I'll limit myself to two points for now and once that's
working we can start considering how to approach this situation.
I uploaded yesterdays work to my log and you can already have a look at it
if you like, but nothing is working yet and I am not completely happy with
the structure. Today I will substantially modify it and by tonight (Spanish
10pm aprox.) I might push another update.
Mario.
------------------------------------------------------------------------------
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
