Dear Pierre, > 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.
Indeed. > I now understand (please, could you definitiely confirm? :-)), and this seems > a reachable "first" step. True. > Once that groups have name in the MED file, they can be called from a *.comm > file. Exactly! > For this first step, finally, would you need a *.comm example file? I stole an example from Kees Wouters' tutorials on caelinux.org You can check it out: its lives in the src/samples/Level2/FEM/ directory. Personally I think the .comm simulation syntax is quite ok with the EFICAS editor, but I **hate** the way the .astk / .export files are created. I'd love to work around this, perhaps the PyQT code you submitted offers perspective here? Cheers! Thanks again for your input! -jelle _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
