Hi Michael, Although I am interested, I think it is unnecessary at this stage. If you receive no offers through elance, let me know. I am definitely capable of doing this kind of stuff.
Regards, Marco On Mon, Dec 2, 2013 at 2:30 PM, Michael Klitgaard <mich...@klitgaard.dk>wrote: > For this task, I think the blob on voxel side would be okay, but off > course, the materials would be a nice feature. > I have some screendumps of the model(s) I can send, if someone is > interested. > It isn't very sensitive, but putting them on a public mailinglist is > probadly a no go. > > Sincerely > Michael > > > On Mon, Dec 2, 2013 at 1:55 PM, Marco Nawijn <naw...@gmail.com> wrote: > >> More interesting challenge would be to also keep metadata of the original >> CAD model such that you don't have a big BLOB on the voxel side. >> This would mean that during the tesselation process of each of the >> parts, somehow we need to extract this information. This is particularly >> useful if the original model is an assembly. It would be nice to also have >> this part information (and thereby the option to color correspondingly) >> in the voxel image. >> >> This probably puts some additional effort in the tesselation part. >> >> Interesting stuff.... >> >> Marco >> >> >> >> On Mon, Dec 2, 2013 at 1:51 PM, Marco Nawijn <naw...@gmail.com> wrote: >> >>> I could not resist. So I, quickly checked the project description. >>> Seems quite straightforward: >>> 1. Build tesselation from CAD model, export to VTK (use PythonOCC for >>> this) >>> 2. Read into VTK and obtain bounding box >>> 3. Generate a 3D structured mesh with 5x5x5 cells in the bounding box >>> 4. Loop over all cells in the structured mesh and check if it is "in" >>> the tesselated >>> geometry >>> >>> One question that remains is when you decide that a voxel is "in" the >>> tesselated >>> geometry. If the center of the voxel is in, or if all of the corners of >>> the voxel are in? >>> >>> So I guess a week of work (make something relatively robust, document >>> properly) >>> should be feasible. (I am not offering it though...;) ). >>> >>> Regards, >>> >>> Marco >>> >>> >>> >>> On Mon, Dec 2, 2013 at 1:35 PM, jelle feringa <jelleferi...@gmail.com>wrote: >>> >>>> >>>> Thanks for the heads-up Michael, that's a 1st for this list, so thanks >>>> for that! >>>> >>>> -jelle >>>> >>>> On Dec 2, 2013, at 1:28 PM, Michael Klitgaard <mich...@klitgaard.dk> >>>> wrote: >>>> >>>> Hi everyone, >>>> >>>> I don't know if it is bad to post here, but my employer have put a task >>>> on elance.com about converting a CAD model to a voxel. >>>> I would preferable have this done in PythonOCC if I am to support it >>>> later. >>>> >>>> >>>> https://www.elance.com/j/voxelize-cad-file-stp-igs-format/50003768/?backurl=aHR0cHM6Ly93d3cuZWxhbmNlLmNvbS9yL2pvYnMvcS1weXRob24v >>>> >>>> It's just a heads up if anyone is interested. >>>> >>>> >>>> Sincerely >>>> Michael >>>> _______________________________________________ >>>> Pythonocc-users mailing list >>>> Pythonocc-users@gna.org >>>> https://mail.gna.org/listinfo/pythonocc-users >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pythonocc-users mailing list >>>> Pythonocc-users@gna.org >>>> https://mail.gna.org/listinfo/pythonocc-users >>>> >>>> >>> >> >> _______________________________________________ >> Pythonocc-users mailing list >> Pythonocc-users@gna.org >> https://mail.gna.org/listinfo/pythonocc-users >> >> > > _______________________________________________ > Pythonocc-users mailing list > Pythonocc-users@gna.org > https://mail.gna.org/listinfo/pythonocc-users > >
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
