Re: [brlcad-devel] Fwd: [brlcad-users] Parallel g-stl conversion?

You wouldn't necessarily need parallel processing to get more than an order of magnitude performance improvement, but why not right? :) The main trick with parallel processing is just managing access to data. If multiple threads are reading/writing the same data, you have to make sure only one

Re: [brlcad-devel] Fwd: [brlcad-users] Parallel g-stl conversion?

A piece of me wants to take this on, as it would be a good opportunity to learn some parallel processing skills, which has been on my todo list for a while now. Might go well, might not... Any pointers as to where a good starting point might be? On 10/04/2013 9:04 AM, "Christopher Sean Morrison"

[brlcad-devel] Fwd: [brlcad-users] Parallel g-stl conversion?

Anyone care to give this optimization a try? The solution is to use some spatial partitioning (e.g., a kd-tree) during the processing. Data coherence would be another. Both would be pure gravy. For tools like g-stl where we know we're going to triangles, it might make sense to triangulate ri

[brlcad-devel] 2nd Call For Papers, 20th Annual Tcl/Tk Conference 2013

[[ Notes: Karl Lehenbauer of FlightAware is confirmed as our Keynote speaker. http://www.flightaware.com ]] 20'th Annual Tcl/Tk Conference (Tcl'2013) http://www.tcl.tk/community/tcl2013/ September 23 - 27, 2013 Bourbon Orleans Hotel New Orleans, Louisiana, USA http://www.bourbonorleans.co

Re: [brlcad-devel] Volume/Surface of hollow objects

On Apr 09, 2013, at 10:55 AM, Csaba Nagy wrote:Now "analyze sph_hollow.r" gives me: analyze: unable to process ID_COMBINATION solid Volume and surface area calculations are not implemented for combination (created via 'r') objects.  That message could be improved to somehow say sph_hollow.r is no

Re: [brlcad-devel] Problem with BRL-CAD generated DXF file

On Apr 09, 2013, at 12:40 PM, Harmanpreet Singh wrote:On Sat, Apr 6, 2013 at 7:42 AM, Christopher Sean Morrison wrote: > On Apr 5, 2013, at 2:02 PM, Harmanpreet Singh wrote: >> Layer definition is incomplete, do not have code 70 (flags) and 62 (linetype) >> And layer name contains

Re: [brlcad-devel] INTRODUCTION

On Apr 09, 2013, at 01:15 PM, Sabhya Kaushal wrote:I would like to ask this, though. From where can I obtain the patch/debugging exercises that you talk of?Participating in Open Source is all about working on things that are useful and interesting.  Any bug, small feature, or code improvement make

Re: [brlcad-devel] INTRODUCTION

Hi Sean, Thanks for the feedback. I would like to ask this, though. From where can I obtain the patch/debugging exercises that you talk of? Also, can I send my submissions for more than one projects that I mentioned? Because the very reason that I enumerated so many choices was that I could not

Re: [brlcad-devel] Problem with BRL-CAD generated DXF file

On Sat, Apr 6, 2013 at 7:42 AM, Christopher Sean Morrison wrote: > On Apr 5, 2013, at 2:02 PM, Harmanpreet Singh wrote: >> Layer definition is incomplete, do not have code 70 (flags) and 62 (linetype) >> And layer name contains invalid chars "/" & "." > > This is certainly actionable and should be

Re: [brlcad-devel] INTRODUCTION

On Apr 09, 2013, at 11:22 AM, Sabhya Kaushal wrote:Hello all! Hello Sabhya!  Welcome and thanks for the introduction.I am, in particular, interested in the following idea(s) that havebeen displayed on the project ideas link page of your organisation,that I would be happy to work on and that I can

[brlcad-devel] INTRODUCTION

Hello all! I am a pre-final year Computer Science Engineering student from Panjab University, Chandigarh, India. As a budding programmer, I am very much interested in joining your organisation for Google Summer Of Code 2013. I am, in particular, interested in the following idea(s) that have been

[brlcad-devel] Volume/Surface of hollow objects

Hi Sean, I'm back with questions - I'm still not clear how the surface/volume of hollow objects should be interpreted. I created a simple setup to clear that: in sphout.s sph 0 0 0 2 in sphin.s sph 0 0 0 1 c -r sph_hollow.r (sphout.s - sphin.s) B sph_hollow.r This is basically a hollow sphe