shapeworks-users

Text archives Help


Re: [shapeworks-users] Running ShapeWorks on 3D objects


Chronological Thread 
  • From: <prateepm@sci.utah.edu>
  • To: shapeworks-users@sci.utah.edu,"Christophe Van Dijck" <Christophe.VanDijck@kuleuven.be>
  • Subject: Re: [shapeworks-users] Running ShapeWorks on 3D objects
  • Date: Thu, 03 Jul 2014 12:11:32 -0600

Hi Christophe,

Depending on the configurations of your machine, I would say the processing time might vary from couple of minutes to ~1 hour. Also, please make sure while using ShapeWorks you enable its threading functionality, which makes things considerably faster.

--
Best
Prateep


On Wed, 2 Jul 2014 08:56:04 +0200
"Christophe Van Dijck" <Christophe.VanDijck@kuleuven.be> wrote:
Hi Elizabeth,



I have a dataset of 100+ femurs, but in STL format (so triangular meshes). I
think I can work myself around the code to get it working with STLs, but I
was wondering how long it would take to handle 100+ cases of 25.000
vertices.



Regards,

Christophe



From: Elizabeth Jurrus [mailto:liz@sci.utah.edu] Sent: dinsdag 1 juli 2014 19:32
To: shapeworks-users@sci.utah.edu; Christophe Van Dijck
Subject: Re: [shapeworks-users] Running ShapeWorks on 3D objects



Hi Christophe,

ShapeWorks is designed to work on 3D volumes, but takes as input, labeled
images. How big is your volume (in terms of pixels)?

- liz



On 07/01/2014 03:36 AM, Christophe Van Dijck wrote:

Hello,



My name is Christophe Van Dijck and I'm a PhD student at KULeuven. I was
wondering if ShapeWorks could be applied to 3D objects (with a vertex count
up to 25.000) and if this would be a computationally heavy operation.



Kind regards,



Christophe Van Dijck



____________________________________________________________________________




Ir. Christophe Van Dijck, PhD student
KU Leuven

Department of Mechanical Engineering

Biomechanics Section (BMe)

Celestijnenlaan 300C,

B-3001 Heverlee, Belgium

Phone: +32 16 74 49 06

Email: christophe.vandijck@kuleuven.be










Archive powered by MHonArc 2.6.18.

Top of page