Jelle,2.

> >> I do think that there is sufficient reason to implement meshing and
> boundary / initial conditions in pythonOCC however.
> Please Jelle, I beg you, what do you mean by "to implement [...] *boundary
> / initial conditions*"?
> Is it only to create groups of elements or nodes in the generated mesh?
>
>
> In Salome terminology, its would be GroupOnGeom ( adding groups to Brep
> topology ), and methods for adding / subtracting groups.
> Those groups than can be used in the .comm simulation specification.
>
> f1,f2,f3,f4,f5,f6 = Topo(box).faces()
> smesh_mesh.GroupOnGeom(f1,'load')
> smesh_mesh.GroupOnGeom(f4,'fixate')
>
> So, its just defining and naming a group. That's all.
>

 Ok, so if I answer to my own question, how "implementing boundary / initial
conditions in pythonOCC"?, the answer will be first implement the ability to
create and name groups of elements / nodes from Brep topological entities.

I now understand (please, could you definitiely confirm? :-)), and this
seems a reachable "first" step.
Once that groups have name in the MED file, they can be called from a *.comm
file.

For this first step, finally, would you need a *.comm example file?

Best regards,

Pierre
_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users

Reply via email to