|
|
I'm writing a 3d slicer program (a "Virtual MRI"), and am trying to make a
mock dataset to test it on. I have a test object, a half-torus, and have
applied a radial colormap to it. I need several different stacks of
slices, but I'll give a concrete example of where my problem lies:
My half-torus is in the XY plane. I wish to make a large number of parallel
slices along the y-axis. Currently, I'm doing this by intersecting it with
a very thin box, which is shifted incrementally along the y-axis by means
of the clock variable, and then photographing the result with an
orthographic camera. Geometrically, this works fine - I get a nice stack
of slice images - but I lose the colormapping, which is crucial to my
application.
Because I'm not slicing in-plane with the radial colormap, I can't just
apply it to each individual slice. I really need to have an appropriately
colored solid object, which I can slice from any direction, and have the
colormap be sliced too.
Can anyone help, please?
Post a reply to this message
|
|
|
|
http://povray.org/documentation/view/3.6.1/362/
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
|
|
|
You can just apply the color-mapped texture to the result of the CSG, like
difference {
object{...}
object{...}
texture{...}
}
instead of
difference {
object{... texture{...}}
object{...}
}
If that's a nuisance to do (like if your object is going to be declared
ahead of time), then I think you can just add the cutaway_textures keyword
instead, and the texture of the first object will be used for the whole
difference.
- Slime
[ http://www.slimeland.com/ ]
Post a reply to this message
|
|