No, I pulled from the repository. I made a mistake that the file was blade3_2.msh not blade3_4.msh. I attached "blade3_2.png". Note surface cells 89 and 90 at the bottom. Can you check blade3_2.msh again?
On Mon, Mar 5, 2018 at 9:12 PM, [email protected] < [email protected]> wrote: > Hi > > I have run the same command on your geometry and I don’t have the problem > you mentioned. > > Do you compile Gmsh from the sources ? If yes, could you try with the most > recent version on the gitlab (https://gitlab.onelab.info/gmsh/gmsh.git) ? > > Anthony Royer > > Le 5 mars 2018 à 11:00, Orxan Shibliyev <[email protected]> a écrit : > > The geo file is attached. When "gmsh blade3.geo -part_split -part 9" is > applied "blade3_4.msh" has two edges which are isolated from their cells. > My version is 3.0.7. > > On Mon, Mar 5, 2018 at 10:30 AM, Christophe Geuzaine <[email protected]> > wrote: > >> >> >> On 4 Mar 2018, at 19:31, Orxan Shibliyev <[email protected]> wrote: >> >> Hi >> >> I do the following command: >> >> gmsh file.geo -part_split -part 9 >> >> Sometimes, I get a partitioned file such that a surface edge which is >> supposed to be part of a quadrangle is stored alone. Is there a way to >> force surface edges to be stored together with their cells? In other words, >> I do not want an isolated edge whose only one point is connected to mesh >> and other point is dangling. >> >> >> Can you send a simple example where this happens? >> >> >> Thanks, >> Orhan >> _______________________________________________ >> gmsh mailing list >> [email protected] >> http://onelab.info/mailman/listinfo/gmsh >> >> >> — >> Prof. Christophe Geuzaine >> University of Liege, Electrical Engineering and Computer Science >> http://www.montefiore.ulg.ac.be/~geuzaine >> >> Free software: http://gmsh.info | http://getdp.info | http://onelab.info >> >> > <blade3.geo> > >
_______________________________________________ gmsh mailing list [email protected] http://onelab.info/mailman/listinfo/gmsh
