[Gmsh] Cyclic boundary condition (same mesh when extruding a surface ?) (Durufle marc)
gdemesy at physics.utoronto.ca
gdemesy at physics.utoronto.ca
Fri Jun 18 14:36:19 CEST 2010
Hi Marc,
Here is an example that combines extruded meshes/rotations:
http://www.geuz.org/pipermail/gmsh/attachments/20090602/b144063e/attachment.geo
Hope this will help,
Guillaume
gmsh-request at ace20.montefiore.ulg.ac.be a écrit :
> Send gmsh mailing list submissions to
> gmsh at geuz.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.geuz.org/mailman/listinfo/gmsh
> or, via email, send a message with subject or body 'help' to
> gmsh-request at geuz.org
>
> You can reach the person managing the list at
> gmsh-owner at geuz.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gmsh digest..."
>
>
> Today's Topics:
>
> 1. Re: freefem (Geordie McBain)
> 2. Cyclic boundary condition (same mesh when extruding a surface
> ?) (Durufle marc)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 18 Jun 2010 09:52:53 +1000
> From: Geordie McBain <gdmcbain at freeshell.org>
> Subject: Re: [Gmsh] freefem
> To: Luis Casillas <casillasluis at lanl.gov>
> Cc: gmsh at geuz.org
> Message-ID:
> <AANLkTimK12vmQCH3zd8owe7JuY_f5ozFOiX3rN9lnb5b at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> 2010/6/18 Luis Casillas <casillasluis at lanl.gov>:
>> Hi,
>> I continue with the attempt to export a mesh to freefempp,
>> the strange thing is that I have had success in a few cases,
>> but in most of them I get errors, I'm attaching a pair of meshes that
>> don't work,
>> thanks
>
> Hello. There's a little error in domain1.geo that makes the mesh
> produced with
>
> $ gmsh -2 -format mesh -string 'Mesh.SaveElementTagType=2;' -o
> domain1.3.mesh domain1.geo
> $ gawk -f 3to2.awk domain1.3.mesh > domain1.mesh
>
> wrong: the top-right subdomain has the wrong orientation, clockwise
> rather than anticlockwise. Change the line in domain1.geo defining
> its boundary as follows:
>
> $ diff domain1{,a}.geo
> 52c52
> < Line Loop(21) = {18,19,20,10,14};
> ---
>> Line Loop(21) = {-18,-19,-20,-10,-14};
>
> Then it works fine; e.g. the FreeFem++ file
>
> mesh Th = readmesh ("domain1a.mesh");
> cout << "area: " << int2d (Th) (1.0) << "." << endl;
>
> happily and correctly computes the area as 100.
>
> I didn't look at the other two meshes.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 18 Jun 2010 08:41:27 +0000 (GMT)
> From: Durufle marc <marc_durufle at yahoo.fr>
> Subject: [Gmsh] Cyclic boundary condition (same mesh when extruding a
> surface ?)
> To: gmsh at geuz.org
> Message-ID: <542760.66132.qm at web26402.mail.ukl.yahoo.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
> I want to mesh a part of a 3-D domain (which is cyclic), and impose
> cyclic boundary conditions, but the problem is that in my solver I
> assume that the two surfaces of the 3-D cell are the same. I send
> you an exemple of a part of a sphere. And by following
> recommendations of a previous message :
> http://www.geuz.org/pipermail/gmsh/2010/005511.html
> I didn't get the same mesh when I extruded the surface by rotation.
> So, is there a solution to have the same surface mesh for the two
> surfaces ? (teta = 0 and teta = pi/4)
> In the given example (for a periodic mesh), surfaces of the cube
> didn't have the same mesh actually :(
>
> Thanks for your help.
>
>
>
> ________________________________
> De : "gmsh-request at ace20.montefiore.ulg.ac.be"
> <gmsh-request at ace20.montefiore.ulg.ac.be>
> ? : gmsh at geuz.org
> Envoy? le : Jeu 17 juin 2010, 18h 35min 49s
> Objet : gmsh Digest, Vol 89, Issue 19
>
> Send gmsh mailing list submissions to
> gmsh at geuz.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.geuz.org/mailman/listinfo/gmsh
> or, via email, send a message with subject or body 'help' to
> gmsh-request at geuz.org
>
> You can reach the person managing the list at
> gmsh-owner at geuz.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gmsh digest..."
>
>
> Today's Topics:
>
> 1. Help (Henri Pascal-Jenny)
> 2. Question about reclassify (Martin Vymazal)
> 3. Re: freefem (Luis Casillas)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 17 Jun 2010 11:26:36 +0200
> From: "Henri Pascal-Jenny" <henri.pascal-jenny at sogeti.com>
> Subject: [Gmsh] Help
> To: <gmsh at geuz.org>
> Message-ID: <00e801cb0dff$31b3f550$1c7de20a at so.fr.ad.sotranet.net>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi
>
>
>
> I am facing the problem of finding the minimum-3D box enclosing AS CLOSE AS
> POSSIBLE a set of 3D mesh points .
>
>
>
> I would like to avoid the use of a too-sophisticated algorithm .
>
> (cf. http://en.wikipedia.org/wiki/Minimum_bounding_box_algorithms)
>
>
>
> Actually, when used straightforwardly, the method "BoundingBox" available
> in a gmesh-session returns a 3D box
>
> which box does not always correspond to the minimum volume enclosing the set
> of points
>
>
>
> ( imagine a thin and not fully-planar shape tilted in respect to the axes of
> a standard coordinates-frame )
>
>
>
> In fact, the matter comes from the bulk orientation of the envelop of the
> set of points under consideration.
>
>
>
> The usage is :
>
> BoundingBox { expression, expression, expression, expression, expression,
> expression };
>
> what forces the bounding box of the scene to the given expressions (X min, X
> max,
>
> Y min, Y max, Z min, Z max).
>
>
>
> Therefore, I am wandering if there is a way of operating the "BoundingBox"
> method in order to get in the end the truly-minimum 3D box enclosing.
>
> Actually, I guess that there is a preliminary thing to do related to the
> coordinates system ; maybe I am wrong.
>
>
>
> Well, I would appreciate it very much if anyone could supply me for any
> piece of information regarding my problem.
>
> Thanks a lot in advance for your attention and your cooperation.
>
>
>
>
>
> Regards
>
> Henri Pascal-Jenny
>
>
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://www.geuz.org/pipermail/gmsh/attachments/20100617/9522a6bb/attachment-0001.htm>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 17 Jun 2010 17:37:03 +0200
> From: Martin Vymazal <martin.vymazal at vki.ac.be>
> Subject: [Gmsh] Question about reclassify
> To: gmsh at geuz.org
> Message-ID: <20100617173703.14972p7a6eirqrkv at horde.vki.ac.be>
> Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";
> format="flowed"
>
> Hello,
>
> I would like to ask if it is possible to launch the 'reclassify'
> command from command line. I normally use it from the gui, but since
> all the other mesh processing is done using scripts, it would be nice
> if I could do this also without opening the gui.
>
> I have one more little question. Suppose I run reclassify, I get a lot
> of surfaces and I hide some of them by clicking in the gui. Is it
> possible to create a new geo/msh file which contains only entities
> currently set as visible? What I mean is that I don't want to save a
> file which is the original mesh with additional info about visibility,
> but I'd like to have a new file in which the 'invisible' parts are
> completely absent.
>
> Thank you.
>
> Best regards,
>
> Martin Vymazal
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 17 Jun 2010 09:41:22 -0600
> From: Luis Casillas <casillasluis at lanl.gov>
> Subject: Re: [Gmsh] freefem
> To: gmsh at geuz.org
> Message-ID: <8FA18878-46E8-4817-B926-BBD404D49B94 at lanl.gov>
> Content-Type: text/plain; charset="us-ascii"; Format="flowed"
>
> Hi,
> I continue with the attempt to export a mesh to freefempp,
> the strange thing is that I have had success in a few cases,
> but in most of them I get errors, I'm attaching a pair of meshes that
> don't work,
> thanks
>
> Luis
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: domain1.geo
> Type: application/octet-stream
> Size: 1175 bytes
> Desc: not available
> URL:
> <http://www.geuz.org/pipermail/gmsh/attachments/20100617/991789f2/attachment.geo>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: domain1.mesh
> Type: application/octet-stream
> Size: 3000 bytes
> Desc: not available
> URL:
> <http://www.geuz.org/pipermail/gmsh/attachments/20100617/991789f2/attachment.mesh>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: domain2.mesh
> Type: application/octet-stream
> Size: 9150 bytes
> Desc: not available
> URL:
> <http://www.geuz.org/pipermail/gmsh/attachments/20100617/991789f2/attachment-0001.mesh>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: domain2.unv
> Type: application/octet-stream
> Size: 52586 bytes
> Desc: not available
> URL:
> <http://www.geuz.org/pipermail/gmsh/attachments/20100617/991789f2/attachment.unv>
> -------------- next part --------------
>
>
> ------------------------------
>
> _______________________________________________
> gmsh mailing list
> gmsh at geuz.org
> http://www.geuz.org/mailman/listinfo/gmsh
>
>
> End of gmsh Digest, Vol 89, Issue 19
> ************************************
>
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://www.geuz.org/pipermail/gmsh/attachments/20100618/e230f030/attachment.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: quartier_sphere2.geo
> Type: application/octet-stream
> Size: 807 bytes
> Desc: not available
> URL:
> <http://www.geuz.org/pipermail/gmsh/attachments/20100618/e230f030/attachment-0001.geo>
>
> ------------------------------
>
> _______________________________________________
> gmsh mailing list
> gmsh at geuz.org
> http://www.geuz.org/mailman/listinfo/gmsh
>
>
> End of gmsh Digest, Vol 89, Issue 20
> ************************************
>
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.