For me this sounds like having the original mesh data with additional
management information like the edge list you mentioned. I.e. the
double connected edge list could be a structure on top of the low
level mesh interface.
It doesn't surprise me that you need additional data structures to
analys
Hi All
Have something to say while looking through these chain of mails regarding the
mesh healing. In this part of the project are we dealing only with "healing the
mesh". Today While going through the export options in SmartPlant SP3d piping
and equipment module found that, following is se
Daniel,
Yes, that was what i wanted to know.
I'm thinking we can convert both the native mesh types to the DCEL, and use
that for the healing process and storing as well. That will simplify my
conversion process and the healing process a lot. For example, I'd need to
check for free edges (those o
Rakshika,
About what level do you write? "heal bot1.s" would be a mged command
which is in fact a TCL command. This would call a libged function
ged_heal(). And this function would call your healing algorithm.
Was this your question?
Daniel
2016-05-23 13:41 GMT+02:00 Rakshika Bagavathy :
> D
Daniel,
There could be software specific commands. For example, in the BRL-CAD
software, say we've already created a bot - bot1.s or something like that.
We call the healing functions through a command: heal bot1.s. And something
similar for OpenSCAD.
I can't think of other possible methods.
Rak
Rakshika,
Which alternatives for passing the meshes do you see?
Daniel
2016-05-22 21:06 GMT+02:00 Rakshika Bagavathy :
> Daniel,
>
> I've decided to go with the abstract classes method you suggested. I wanted
> to know how we'd pass the actual native type (bot/ polyset) to the portable
> module.
Daniel,
I've decided to go with the abstract classes method you suggested. I wanted
to know how we'd pass the actual native type (bot/ polyset) to the portable
module.
Regards,
Rakshika.
--
Mobile security can be enabling
Rakshika,
If you understood you right polygonal_mesh is essentially a BRL-CAD
BoT and OpenSCAD's PolySet can be considered as a subset of BoT. I.e.
your approach could work.
> So, this way out conversion just lies in these two functions ...
:))) everything lies in just one function: main()
> I
Daniel,
I understand your method now. Here i am explaining what i had proposed a
little earlier.
Intermediate mesh:
struct polygonal_mesh {
int num_verts;
int num_faces;
double *vertices; //size- 3*num_verts
int *faces; //size - 3*num_faces
/* Other necessary attributes (normals, etc.) and other
2016-05-16 23:40 GMT+02:00 Rakshika Bagavathy :
> Daniel,
>
>>
>> Ooh, generic container doesn't mean generic programming. In fact, it
>> would be explicitly a non-generic programming. (Do you know why?)
>
> I'm sorry, I'm not following what you mean.
How could the “type to be specified later” p
Hi Guys
Thanks for letting me join mailing list.
Please suggest me some work on programming which I could begin right now.
Regarding myself I am a hobby programmer.
This cad development effort is really fascinating as I am Piping Engineer and
day in day out in microstation, Intergra
Rakshika,
2016-05-16 23:40 GMT+02:00 Rakshika Bagavathy :
>> Ooh, generic container doesn't mean generic programming. In fact, it
>> would be explicitly a non-generic programming. (Do you know why?)
>
> I'm sorry, I'm not following what you mean.
This is the statement I was waiting for ;) Kee
Daniel,
> Ooh, generic container doesn't mean generic programming. In fact, it
> would be explicitly a non-generic programming. (Do you know why?)
>
> I'm sorry, I'm not following what you mean.
I'm writing code as i write this mail. What i'm trying to do is write a
structure that is elaborate
2016-05-05 22:06 GMT+02:00 Rakshika Bagavathy :
...
>> > They can which is why the decision needed is whether to (A) use a
>> generic container of vertices, faces, and normals that directly converts to
>> BRL-CAD and trivially converts to OpenSCAD or (B) a general polyset
>> structure that directl
Hello,
> BRL-CAD's rt_bot_internal structure contains attributes such as vertices,
> faces, normals, etc. explicitly, while the
>
> > OpenSCAD Polyset class contains a vector of vector of 3D vectors as a
> set of polygons.
>
> Heh, they have a what??? :)
Sean, i apologise for the trivial languag
>> I will edit my proposal and abstract accordingly. After talking to kintel on
>> the IRC, it is now clear that: geometry storage and geometry processing can
>> be done with different data structures.
>
> They can which is why the decision needed is whether to (A) use a generic
> container of v
> i wanted to know if we are to go forward with the portable module for mesh
> healing along with OpenSCAD.
Developing something that OpenSCAD can also use should be a primary objective
if this is of interest to them.
> I will edit my proposal and abstract accordingly. After talking to kintel
17 matches
Mail list logo
