Hi Lucas,
I’ve just tried your model and if I create the loop from the GUI, it seems to
be ok. There must be a sign wrong in your arrays.
Try this:
// Create Line Loop
myLoop = newll;
//Curve Loop(myLoop) =
{-Lower_Line2[],Lower_Line3[],Lower_InputLine[1],-Lower_OutputLine[1]};
Physical Line('myLoop') =
{-Lower_Line2[],Lower_Line3[],Lower_InputLine[1],-Lower_OutputLine[1]};
Curve Loop(myLoop) = {271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281,
282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 296, 297,
298, 299, 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312, 313,
314, 315, 316, 317, 318, 319, 320, 321, 322, 323, 324, 325, 326, 327, 328, 329,
330, 331, 332, 333, 334, 335, 336, 337, 338, 339, 340, 341, 342, 343, 344, 345,
346, 347, 348, 349, 350, 351, 352, 353, 354, 355, 356, 357, 358, 359, 360, 361,
362, 363, 364, 365, 366, 367, 368, 369, 370, 371, 372, 373, 374, 375, 376, 377,
378, 3312, -500, -499, -498, -497, -496, -495, -494, -493, -492, -491, -490,
-489, -488, -487, -486, -485, -484, -483, -482, -481, -480, -479, -478, -477,
-476, -475, -474, -473, -472, -471, -470, -469, -468, -467, -466, -465, -464,
-463, -462, -461, -460, -459, -458, -457, -456, -455, -454, -453, -452, -451,
-450, -449, -448, -447, -446, -445, -444, -443, -442, -441, -440, -439, -438,
-437, -436, -435, -434, -433, -432, -431, -430, -429, -428, -427, -426, -425,
-424, -423, -422, -421, -420, -419, -418, -417, -416, -415, -414, -413, -412,
-411, -410, -409, -408, -407, -406, -405, -404, -403, -402, -401, -400, -399,
-398, -397, -396, -395, -394, -393, -392, -391, -390, -389, -388, -387, -386,
-385, -384, -383, -382, -381, -380, -379, -3311, 255, 256, 257, 258, 259, 260,
261, 262, 263, 264, 265, 266, 267, 268, 269, 270};
Hope that helps!
Ruth
> On 19 Jun 2018, at 14:03, Lucas Blattner Martinho
> <[email protected]> wrote:
>
> Dear all,
>
> I am having trouble creating line loops while using the OpenCASCADE geometry
> kernel. A line loop that seems to be well defined for Gmsh's native kernel
> is regarded as an open loop by OpenCASCADE...
>
> A more detailed description of the problem is provided below and the .geo
> files required to repeat the issue are available attached to this message.
>
> Does anybody understand why Gmsh exhibits sjuch a behavior ? Could anybody
> provide some help ?
>
>
> Best regards,
>
> Lucas Blattner
> G2Elab - Laboratoire de Génie Électrique de Grenoble
>
>
>
> Problem description :
>
>
> I am working on the geometry of a complex coil in the shape of a horse saddle
> (see .geo files attached to this message).
>
> File '"Lower.geo" contain the points and lines of the geometry. These were
> generated with the help of a computer program and are loaded by the main
> file "Saddle.geo" with an "Include" command.
>
> I am trying to make line loops using the lines contained in the
> aforementioned file to proceed creating surfaces and volumes. The lines ids
> are stored in vectors such as Lower_Line2[], Lower_InputLine[] and so on, all
> of which are defined in "Lower.geo".
>
> I am particularly interested in generating a thin volume with the aid of the
> "ThruSections" function provided by OpenCASCADE. The first step is the
> creation of the line loops required by this function..
>
> That said, I created a line loop in the main file "Saddle.geo". The loop
> seem to be OK, that is, it is closed and is created without console errors
> or warnings. This can be verified by taking a look at the physical regions
> "myLoop", which correspond to the same list of lines composing the loop.
>
> However, loading "Saddle.geo" after uncommenting the first line of the code
> (to enable the OpenCASCADE functions) results in the following error :
>
> Error : Line Loop is not closed
> Error : 'C:\xxxxxx\saddle.geo', line 6 : Could not add line loop
>
> This error makes it impossible to continue using ThruSections. Since the line
> loop seems to be correctly defined, I believe that it could be caused by a
> bug....
>
>
>
> <Lower.geo><Saddle.geo>_______________________________________________
> gmsh mailing list
> [email protected]
> http://onelab.info/mailman/listinfo/gmsh
_______________________________________________
gmsh mailing list
[email protected]
http://onelab.info/mailman/listinfo/gmsh
