building a 3d model with slices

Hi all, I'm reproducing a 3d laser scanned model using 2d slices. I've sliced the model at .75 intervals (for the sheet material) using the brep / plane intersection component.

The problem is the model is angled so the section curves won't include the actual projected boundary of the whole "slice". What I'd like to do is extract both the top and bottom sections of each slice and do a region union to make sure I have enough material all around. Ideally these unioned sections would be located in the middle of each slice in the z direction.

The sections are there - I just need to figure out how to manipulate them properly. Any help would be much appreciated..

Thx!

Attachments:

Sections.jpg, 98 KB

Replies to This Discussion

Permalink Reply by Chris Tietjen on January 2, 2011 at 8:34am

Here's a start.

Chris

Attachments:

Slicer.ghx, 211 KB

Permalink Reply by WoodDuck on January 2, 2011 at 11:10am

Thanks much for the reply Chris. I would like to try unioning all the curve sets in place at one time rather than 1 set at a time. The reason for this is I might end up with 25 - 30 separate slices depending on the model.

I re worked my def a bit though and I'm almost there - I have the top and bottom curves brought together in the middle of each slice as in your def. The last part of the puzzle is the region union - it doesn't want to do all the sets at once. I wonder if there's a way to pair up the curves by manipulating the lists?

Thanks

Attachments:

Slicer1.jpg, 270 KB
Slicer2.jpg, 88 KB
Slicer2.ghx, 230 KB

Permalink Reply by Chris Tietjen on January 2, 2011 at 5:05pm

I think I've got it. Let me know.

Attachments:

Slicer3.ghx, 312 KB

Permalink Reply by WoodDuck on January 3, 2011 at 8:44am

Hi Chris, thanks - that's the ticket! One weird thing: the region union errors out more often than not with "region union set is empty" yet it will still bake the desired curves. Maybe it's a bug? Anyway it works - thanks again for your help.

Cheers..

Attachments:

Slicer3.jpg, 267 KB

Permalink Reply by Chris Tietjen on January 3, 2011 at 1:31pm

It might have to do with even or odd number of slices...not sure though. More than likely it's got something to do with the definition rather than a component bug. In any case glad to hear that it's functional.

Chris

Permalink Reply by WoodDuck on January 3, 2011 at 2:06pm

Yes, I think you're right. The top slice has only one curve and throws it off. I'll have to figure out how to get 2 profile curves at the top to correct the error msg.

Thx..

RSS