[Gmsh] R: Problem in transformation of surfaces list

Alessandro Vicini alessandro.vicini at sitael.com
Fri Oct 20 12:09:44 CEST 2017


Hullo Ruth,

but the same kind of operation works fine in other cases that I have. The surface loops that define the volume are not changed by the rotation!

The reason why I need to do that operation AFTER having defined the volume is that I have an automatic procedure which reads a geo file, perform a translation/rotation on one geometry component specified through its physical surfaces IDs, generates the mesh and carry out the simulation . This is done in an outer loop so that many geometry modifications are analysed in the same run. For this reason the procedure appends the commands at the end of the geo file.
I guess the problem is related with the use of OpenCascade, because the same approach works fine in cases when the Built-In geometry kernel is used.

A.



Da: Ruth Vazquez Sabariego [mailto:ruth.sabariego at kuleuven.be]
Inviato: venerdì 20 ottobre 2017 12:02
A: Alessandro Vicini
Cc: gmsh at onelab.info
Oggetto: Re: [Gmsh] Problem in transformation of surfaces list

Hi Alessandro,

The problem is the order of the operations.
You do a rotation of surfaces that define volume 1.
That’s why they are kept.

The rotation is properly handled if you write it as follows:

tmp[] = Physical Surface {102,103};
Rotate {{1, 0, 0}, {-0.5, 0.65, -0.25}, Pi/6} {
   Surface {tmp[]};
}



Surface Loop(5) = {28, 23, 25, 27, 26, 24};
Surface Loop(6) = {9, 4, 6, 8, 7, 10, 1, 22, 18, 21, 20, 17, 19};
Surface Loop(7) = {15, 11, 13, 12, 16, 14};
Volume(1) = {5, 6, 7};
Physical Volume(999) = {1};


Best regards,
Ruth


—
Prof. Ruth V. Sabariego
KU Leuven
Dept. Electrical Engineering ESAT/Electa, EnergyVille
http://www.esat.kuleuven.be/electa<https://urlsand.esvalabs.com/?u=http%3A%2F%2Fwww.esat.kuleuven.be%2Felecta&e=83f3a71b&h=2cc88284&f=y&p=y>
http://www.energyville.be<https://urlsand.esvalabs.com/?u=http%3A%2F%2Fwww.energyville.be&e=83f3a71b&h=5a4cb613&f=y&p=y>

Free software: http://gmsh.info<https://urlsand.esvalabs.com/?u=http%3A%2F%2Fgmsh.info&e=83f3a71b&h=b3002766&f=y&p=y> | http://getdp.info<https://urlsand.esvalabs.com/?u=http%3A%2F%2Fgetdp.info&e=83f3a71b&h=993699b8&f=y&p=y> | http://onelab.info<https://urlsand.esvalabs.com/?u=http%3A%2F%2Fonelab.info&e=83f3a71b&h=017e41bc&f=y&p=y>






On 20 Oct 2017, at 10:46, Alessandro Vicini <alessandro.vicini at sitael.com<mailto:alessandro.vicini at sitael.com>> wrote:


Hullo everybody. In the last two lines of the attached geo file I retrieve the list of elementary surfaces ID from their physical IDs, and then apply a rotation to the list. However, only the edges are rotated, and the "old" surfaces and edges are not deleted after the operation. Why...? Thank you.

Alessandro


<Test.geo>_______________________________________________
gmsh mailing list
gmsh at onelab.info<mailto:gmsh at onelab.info>
http://onelab.info/mailman/listinfo/gmsh

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://onelab.info/pipermail/gmsh/attachments/20171020/40796131/attachment.html>


More information about the gmsh mailing list