[Gmsh] keeping entities in group after translation (self answer)

Christophe Geuzaine cgeuzaine at ulg.ac.be
Sat Feb 27 16:12:53 CET 2010


On 24/02/10 17:58, jean pierre aubry wrote:
> hello
>
>
> i am answering myself as nobody seems to be interested in that
> problem!!!
>
> i may help someone
>
> I have found the following sequence does the job if inserted in the text
> (.geo) file
>
>
> Physical Line("potgc") = {582, 473, 460, 447, 434, 421, 414, 420, 432,
> 445, 458, 471, 484, 583};
>
> Physical Line("potgc285") = {Rotate {{0, 0, 1}, {0, 0, 0}, -Pi/2} {
>   Duplicata { Line{582, 473, 460, 447, 434, 421, 414, 420, 432, 445, 458,
> 471, 484, 583}; }
> }};
>
> quite easy with cut and paste and then mixing the groups if necessary
>
> that's quite useful in construction job of frame structures with many
> translations, rotations and or symmetry
>
> i may help someone!!

Hi Jean-Pierre - To avoid the copy/paste I guess you could also define a 
list of entities first, say

a[] = {582, 473, 460, 447, 434, 421, 414, 420, 432, 445, 458,
        471, 484, 583}

Physical Line("potgc") = a[];

Physical Line("potgc285") = { Rotate {{0, 0, 1}, {0, 0, 0}, -Pi/2} {
   Duplicata { Line{a[]}; } } };


>
> jean pierre aubry
>
>
> _______________________________________________
> gmsh mailing list
> gmsh at geuz.org
> http://www.geuz.org/mailman/listinfo/gmsh
>
>


-- 
Prof. Christophe Geuzaine
University of Liege, Electrical Engineering and Computer Science
http://www.montefiore.ulg.ac.be/~geuzaine