Re: [Gmsh] Change position of value scale

2019-12-05 Thread Marco Tiberga
Dear Christophe,

Thanks for the help!

Best,
Marco

-Original Message-
From: Christophe Geuzaine [mailto:cgeuza...@uliege.be] 
Sent: donderdag 5 december 2019 11:45
To: Marco Tiberga
Cc: Max Orok; gmsh@onelab.info
Subject: Re: [Gmsh] Change position of value scale



> On 5 Dec 2019, at 10:25, Marco Tiberga  wrote:
> 
> Dear Max,
>  
> Yes, that works!
> The scale is vertical now, even though I cannot move it to the right/left of 
> the view.

Here's how to have a vertical scale 100 pixels from the right edge of the 
window, centered vertically:

test.geo:

***
View "Test" {
  ST(0,0,0, 1,0,0, 0,1,0){1,2,3};
};

PostProcessing.HorizontalScales = 0; // Display value scales horizontally
View[0].AutoPosition = 0; // Position the scale or 2D plot automatically (0: 
manual)
View[0].Height = 200; // Height (in pixels) of the scale or 2D plot
View[0].Width = 20; // Width (in pixels) of the scale or 2D plot
View[0].PositionX = -100; // X position (in pixels) of the scale or 2D plot (< 
0: measure from right edge; >= 1e5: centered)
View[0].PositionY = 1e6; // Y position (in pixels) of the scale or 2D plot (< 
0: measure from bottom edge; >= 1e5: centered)
***

(There is a little bug with vertical alignment in the latest stable release, 
that was just fixed. Use the latest snapshot to test.)

Christophe



> . but it does not matter, better than nothing.
>  
> Thanks for the help, I scanned through the View options in the manual, I did 
> not think of looking at the PostProcessing ones as well.
> As a suggestion, I think that explaining what the 
> “PostProcessing.HorizontalScales = 0” does in the manual is useful to 
> everyone.
>  
> Best,
> Marco
>  
>  
> From: Max Orok [mailto:mo...@mevex.com] 
> Sent: woensdag 4 december 2019 20:21
> To: Marco Tiberga
> Cc: gmsh@onelab.info
> Subject: Re: [Gmsh] Change position of value scale
>  
> Maybe try setting PostProcessing.HorizontalScales = 0; ?
>  
> 
>  
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gmsh.info_doc_texinfo_gmsh.html-23Post-5F002dprocessing-2Doptions-2Dlist=DwIFaQ=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8=xDQrN9dIlh8hsy24roW04-s63YICVLB4nv0g5BCLJug=-P9U1Y5-mejSlzoFufhNKjjHSGR0Vrg0N-VXRWzaMWU=pFztDMtGRpA-cFtLowtnriTBPoujctfZKCyRFWInDpA=
>  
>  
> Sincerely,
> Max 
>  
> On Wed, Dec 4, 2019 at 1:52 PM Marco Tiberga  wrote:
> Dear Gmsh community,
>  
> Is there a way to change the position of the value scale in any kind of View?
> I tried with the most recent Gmsh snapshot, but if I go to “View options” -> 
> “Axes” -> “2D axes/value scale position” only the option “manual” seems to 
> actually be able to change the position. I am using the GUI, FYI.
>  
> However, I cannot obtain what I want.
> The “Automatic” position is at the bottom-center of the screen and the scale 
> is horizontal. If possible, I would like to have a vertical scale, to the 
> left or right of the view.
>  
> Thanks a lot for your help, in advance.
>  
> Best regards,
> Marco Tiberga
> PhD candidate
> Delft University of Technology
> Faculty of Applied Sciences
> Radiation Science & Technology Department
> Mekelweg 15, 2629 JB Delft, The Netherlands
> E-Mail: m.tibe...@tudelft.nl
> Website: http://www.nera.rst.tudelft.nl/
>  
>  
> ___
> gmsh mailing list
> gmsh@onelab.info
> https://urldefense.proofpoint.com/v2/url?u=http-3A__onelab.info_mailman_listinfo_gmsh=DwIFaQ=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8=xDQrN9dIlh8hsy24roW04-s63YICVLB4nv0g5BCLJug=-P9U1Y5-mejSlzoFufhNKjjHSGR0Vrg0N-VXRWzaMWU=XdyyzLmYB0NKS7XrkQBWCkRQYuQXAqE_VL5sB6tbkXs=
>  
> 
> 
> -- 
> Max Orok
> Contractor
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mevex.com=DwIFaQ=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8=xDQrN9dIlh8hsy24roW04-s63YICVLB4nv0g5BCLJug=-P9U1Y5-mejSlzoFufhNKjjHSGR0Vrg0N-VXRWzaMWU=5QP9foH-tRAB80LztLsn1h1ZzgR5mCzTLuJfcCEqin8=
>  
> 
> 
> ___
> gmsh mailing list
> gmsh@onelab.info
> https://urldefense.proofpoint.com/v2/url?u=http-3A__onelab.info_mailman_listinfo_gmsh=DwIFaQ=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8=xDQrN9dIlh8hsy24roW04-s63YICVLB4nv0g5BCLJug=-P9U1Y5-mejSlzoFufhNKjjHSGR0Vrg0N-VXRWzaMWU=XdyyzLmYB0NKS7XrkQBWCkRQYuQXAqE_VL5sB6tbkXs=
>  

— 
Prof. Christophe Geuzaine
University of Liege, Electrical Engineering and Computer Science 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.montefiore.ulg.ac.be_-7Egeuzaine=DwIFaQ=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8=xDQrN9dIlh8hsy24roW04-s63YICVLB4nv0g5BCLJug=-P9U1Y5-mejSlzoFufhNKjjHSGR0Vrg0N-VXRWzaMWU=0_XKk_DxPsgEsLpeNCGI8Cf5vEadfEeSUmha65oPan8=
 



___
gmsh mailing list
gmsh@onelab.info
http://onelab.info/mailman/listinfo/gmsh


Re: [Gmsh] Change position of value scale

2019-12-05 Thread Marco Tiberga
Dear Max,

Yes, that works!
The scale is vertical now, even though I cannot move it to the right/left of 
the view.. but it does not matter, better than nothing.

Thanks for the help, I scanned through the View options in the manual, I did 
not think of looking at the PostProcessing ones as well.
As a suggestion, I think that explaining what the 
“PostProcessing.HorizontalScales = 0” does in the manual is useful to everyone.

Best,
Marco


From: Max Orok [mailto:mo...@mevex.com]
Sent: woensdag 4 december 2019 20:21
To: Marco Tiberga
Cc: gmsh@onelab.info
Subject: Re: [Gmsh] Change position of value scale

Maybe try setting PostProcessing.HorizontalScales = 0; ?

[image.png]

http://gmsh.info/doc/texinfo/gmsh.html#Post_002dprocessing-options-list<https://urldefense.proofpoint.com/v2/url?u=http-3A__gmsh.info_doc_texinfo_gmsh.html-23Post-5F002dprocessing-2Doptions-2Dlist=DwMFaQ=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8=xDQrN9dIlh8hsy24roW04-s63YICVLB4nv0g5BCLJug=qUtGaLYrjPCKHK3eKYmQv6iMH0TArZJR0a1__z42B84=_xFNXVlwRiYdTzkAs9E8_ogFRAdlhy0gKmXVISByvGk=>

Sincerely,
Max

On Wed, Dec 4, 2019 at 1:52 PM Marco Tiberga 
mailto:m.tibe...@tudelft.nl>> wrote:
Dear Gmsh community,

Is there a way to change the position of the value scale in any kind of View?
I tried with the most recent Gmsh snapshot, but if I go to “View options” -> 
“Axes” -> “2D axes/value scale position” only the option “manual” seems to 
actually be able to change the position. I am using the GUI, FYI.

However, I cannot obtain what I want.
The “Automatic” position is at the bottom-center of the screen and the scale is 
horizontal. If possible, I would like to have a vertical scale, to the left or 
right of the view.

Thanks a lot for your help, in advance.

Best regards,
Marco Tiberga
PhD candidate
Delft University of Technology
Faculty of Applied Sciences
Radiation Science & Technology Department
Mekelweg 15, 2629 JB Delft, The Netherlands
E-Mail: m.tibe...@tudelft.nl<mailto:m.tibe...@tudelft.nl>
Website: http://www.nera.rst.tudelft.nl/


___
gmsh mailing list
gmsh@onelab.info<mailto:gmsh@onelab.info>
http://onelab.info/mailman/listinfo/gmsh<https://urldefense.proofpoint.com/v2/url?u=http-3A__onelab.info_mailman_listinfo_gmsh=DwMFaQ=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8=xDQrN9dIlh8hsy24roW04-s63YICVLB4nv0g5BCLJug=qUtGaLYrjPCKHK3eKYmQv6iMH0TArZJR0a1__z42B84=vQWj1_NaXq8Ch7hU7drxqMwPffNWdeYRI7WX8ETha4E=>


--
Max Orok
Contractor
www.mevex.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mevex.com=DwMFaQ=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8=xDQrN9dIlh8hsy24roW04-s63YICVLB4nv0g5BCLJug=qUtGaLYrjPCKHK3eKYmQv6iMH0TArZJR0a1__z42B84=hEpgsb8iQgb9wNvhzgjRFugwMCBaHL4jtlZd3L8WtSw=>

[Image removed by sender.]
___
gmsh mailing list
gmsh@onelab.info
http://onelab.info/mailman/listinfo/gmsh


[Gmsh] Change position of value scale

2019-12-04 Thread Marco Tiberga
Dear Gmsh community,

Is there a way to change the position of the value scale in any kind of View?
I tried with the most recent Gmsh snapshot, but if I go to "View options" -> 
"Axes" -> "2D axes/value scale position" only the option "manual" seems to 
actually be able to change the position. I am using the GUI, FYI.

However, I cannot obtain what I want.
The "Automatic" position is at the bottom-center of the screen and the scale is 
horizontal. If possible, I would like to have a vertical scale, to the left or 
right of the view.

Thanks a lot for your help, in advance.

Best regards,
Marco Tiberga
PhD candidate
Delft University of Technology
Faculty of Applied Sciences
Radiation Science & Technology Department
Mekelweg 15, 2629 JB Delft, The Netherlands
E-Mail: m.tibe...@tudelft.nl<mailto:m.tibe...@tudelft.nl>
Website: http://www.nera.rst.tudelft.nl/


___
gmsh mailing list
gmsh@onelab.info
http://onelab.info/mailman/listinfo/gmsh


Re: [Gmsh] Gmsh crashes exporting vec fields in .pvtu format

2019-11-25 Thread Marco Tiberga
Dear Christophe,

Sorry, I thought I had to compile from source. I did not see the link to the 
Windows snapshot before, my bad...
I confirm you that both files can be correctly exported now! 

Thanks a lot.

Best,
Marco

-Original Message-
From: Christophe Geuzaine [mailto:cgeuza...@uliege.be] 
Sent: maandag 25 november 2019 14:16
To: Marco Tiberga
Cc: gmsh@onelab.info; Max Orok
Subject: Re: [Gmsh] Gmsh crashes exporting vec fields in .pvtu format



> On 25 Nov 2019, at 12:03, Marco Tiberga  wrote:
> 
> Dear Christophe,
> 
> Unfortunately, I cannot try with the most recent git snapshot, but I can 
> provide you with a simple test.
> 
> Attached, you find two very simple, random, scalar and vector fields.
> If I open them with Gmsh and then try to File-->Export them in pvtu, Gmsh 
> crashed. 
> If I do exactly the same two passages (open, then export) with Gmsh 2.14.0, 
> the program does not crash.
> 

Both files work with the latest snapshot.

(To give it a try just download the latest snapshot for your OS - you don't 
have to recompile from source.)

Christophe

> Hope this is simple enough.
> 
> Kind regards,
> Marco Tiberga
> 
> 
> -Original Message-
> From: Christophe Geuzaine [mailto:cgeuza...@uliege.be] 
> Sent: zaterdag 23 november 2019 9:48
> To: Max Orok
> Cc: Marco Tiberga; gmsh@onelab.info
> Subject: Re: [Gmsh] Gmsh crashes exporting vec fields in .pvtu format
> 
> 
> Hi guys,
> 
> I have fixed a small (but that could lead to a crash) bug related to pvtu 
> export yesterday. Could you check if this fixes your issue? If not, could you 
> send a (simple) dataset together with a script (or steps to follow) to 
> reproduce the problem?
> 
> Thanks,
> 
> Christophe
> 
> 
> 
>> On 22 Nov 2019, at 15:36, Max Orok  wrote:
>> 
>> Thank you Marco, cc'ing the wider Gmsh community with these examples in case 
>> they can help.
>> 
>> 
>> On Thu, Nov 21, 2019 at 4:05 AM Marco Tiberga  wrote:
>> Dear Max,
>> 
>> 
>> 
>> Please find attached two .pos files of a scalar and a vector quantity I 
>> wanted to export in pvtu format.
>> 
>> It is a velocity field, and the vector field was built through the Scal2Vec 
>> plugin from the components.
>> 
>> 
>> 
>> On top of this, I have discovered that also the export of the .pos scalar 
>> view does not work.
>> 
>> What I usually do is to open the mesh (.msh file), merge a .msh file with 
>> the scalar field and then export the view in pvtu format: this works.
>> 
>> Instead, if I open the mesh, merge the .msh file with the scalar field, 
>> export the view into .pos format (the attached u_scal is an example), then 
>> open the new .pos file directly and finally try to export it in pvtu, Gmsh 
>> crashes.
>> 
>> So, I suspect the problem is in the export of .pos view to pvtu format.
>> 
>> 
>> 
>> Hope these are useful examples.
>> 
>> 
>> 
>> Best regards,
>> 
>> Marco
>> 
>> 
>> 
>> From: Max Orok [mailto:mo...@mevex.com] 
>> Sent: woensdag 20 november 2019 22:48
>> To: Marco Tiberga
>> Subject: Re: [Gmsh] Gmsh crashes exporting vec fields in .pvtu format
>> 
>> 
>> 
>> Hi Marco,
>> 
>> 
>> 
>> Would it be possible to get an example file that shows this behaviour?
>> 
>> 
>> 
>> Sincerely,
>> 
>> Max
>> 
>> 
>> 
>> On Wed, Nov 20, 2019 at 4:46 PM Marco Tiberga  wrote:
>> 
>> Good evening,
>> 
>> 
>> 
>> I would like to report a bug I found.
>> 
>> 
>> 
>> I needed to export a vector field in pvtu format (via File -> Export). 
>> However, Gmsh crashes as soon as it starts the export process. This does not 
>> happen when I export scalar fields.
>> 
>> However, I knew I was once able to do it. So, I went back with the versions, 
>> and I found out that the first buggy version is 2.14.1 (at that time, the 
>> export was done via File -> Save As).
>> 
>> 
>> 
>> I understand this is a minor bug (and the fix is not even urgent as far as I 
>> am concerned, as I was able to export my field using Gmsh 2.14.0), but it is 
>> useful to report it anyway.
>> 
>> 
>> 
>> 
>> 
>> Best regards,
>> 
>> Marco Tiberga
>> PhD candidate
>> 
>> Delft University of Technology
>> 
>> Faculty of Applied Sciences
>> 
>> Radiation Science & Technology Department
>> 
>> Mekelweg 15, 2629 JB Delft, The Netherlands
>&g

Re: [Gmsh] Gmsh crashes exporting vec fields in .pvtu format

2019-11-25 Thread Marco Tiberga
Dear Christophe,

Unfortunately, I cannot try with the most recent git snapshot, but I can 
provide you with a simple test.

Attached, you find two very simple, random, scalar and vector fields.
If I open them with Gmsh and then try to File-->Export them in pvtu, Gmsh 
crashed. 
If I do exactly the same two passages (open, then export) with Gmsh 2.14.0, the 
program does not crash.

Hope this is simple enough.

Kind regards,
Marco Tiberga


-Original Message-
From: Christophe Geuzaine [mailto:cgeuza...@uliege.be] 
Sent: zaterdag 23 november 2019 9:48
To: Max Orok
Cc: Marco Tiberga; gmsh@onelab.info
Subject: Re: [Gmsh] Gmsh crashes exporting vec fields in .pvtu format


Hi guys,

I have fixed a small (but that could lead to a crash) bug related to pvtu 
export yesterday. Could you check if this fixes your issue? If not, could you 
send a (simple) dataset together with a script (or steps to follow) to 
reproduce the problem?

Thanks,

Christophe



> On 22 Nov 2019, at 15:36, Max Orok  wrote:
> 
> Thank you Marco, cc'ing the wider Gmsh community with these examples in case 
> they can help.
> 
> 
> On Thu, Nov 21, 2019 at 4:05 AM Marco Tiberga  wrote:
> Dear Max,
> 
>  
> 
> Please find attached two .pos files of a scalar and a vector quantity I 
> wanted to export in pvtu format.
> 
> It is a velocity field, and the vector field was built through the Scal2Vec 
> plugin from the components.
> 
>  
> 
> On top of this, I have discovered that also the export of the .pos scalar 
> view does not work.
> 
> What I usually do is to open the mesh (.msh file), merge a .msh file with the 
> scalar field and then export the view in pvtu format: this works.
> 
> Instead, if I open the mesh, merge the .msh file with the scalar field, 
> export the view into .pos format (the attached u_scal is an example), then 
> open the new .pos file directly and finally try to export it in pvtu, Gmsh 
> crashes.
> 
> So, I suspect the problem is in the export of .pos view to pvtu format.
> 
>  
> 
> Hope these are useful examples.
> 
>  
> 
> Best regards,
> 
> Marco
> 
>  
> 
> From: Max Orok [mailto:mo...@mevex.com] 
> Sent: woensdag 20 november 2019 22:48
> To: Marco Tiberga
> Subject: Re: [Gmsh] Gmsh crashes exporting vec fields in .pvtu format
> 
>  
> 
> Hi Marco,
> 
>  
> 
> Would it be possible to get an example file that shows this behaviour?
> 
>  
> 
> Sincerely,
> 
> Max
> 
>  
> 
> On Wed, Nov 20, 2019 at 4:46 PM Marco Tiberga  wrote:
> 
> Good evening,
> 
>  
> 
> I would like to report a bug I found.
> 
>  
> 
> I needed to export a vector field in pvtu format (via File -> Export). 
> However, Gmsh crashes as soon as it starts the export process. This does not 
> happen when I export scalar fields.
> 
> However, I knew I was once able to do it. So, I went back with the versions, 
> and I found out that the first buggy version is 2.14.1 (at that time, the 
> export was done via File -> Save As).
> 
>  
> 
> I understand this is a minor bug (and the fix is not even urgent as far as I 
> am concerned, as I was able to export my field using Gmsh 2.14.0), but it is 
> useful to report it anyway.
> 
>  
> 
>  
> 
> Best regards,
> 
> Marco Tiberga
> PhD candidate
> 
> Delft University of Technology
> 
> Faculty of Applied Sciences
> 
> Radiation Science & Technology Department
> 
> Mekelweg 15, 2629 JB Delft, The Netherlands
> 
> E-Mail: m.tibe...@tudelft.nl
> Website: http://www.nera.rst.tudelft.nl/
> 
>  
> 
>  
> 
> ___
> gmsh mailing list
> gmsh@onelab.info
> http://onelab.info/mailman/listinfo/gmsh
> 
> 
> 
> --
> 
> Max Orok
> 
> Contractor
> 
> www.mevex.com
> 
> 
> 
> 
> 
> -- 
> Max Orok
> Contractor
> www.mevex.com
> 
> 
> ___
> gmsh mailing list
> gmsh@onelab.info
> http://onelab.info/mailman/listinfo/gmsh

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





vec_test.pos
Description: vec_test.pos


scal_test.pos
Description: scal_test.pos
___
gmsh mailing list
gmsh@onelab.info
http://onelab.info/mailman/listinfo/gmsh


[Gmsh] Gmsh crashes exporting vec fields in .pvtu format

2019-11-20 Thread Marco Tiberga
Good evening,

I would like to report a bug I found.

I needed to export a vector field in pvtu format (via File -> Export). However, 
Gmsh crashes as soon as it starts the export process. This does not happen when 
I export scalar fields.
However, I knew I was once able to do it. So, I went back with the versions, 
and I found out that the first buggy version is 2.14.1 (at that time, the 
export was done via File -> Save As).

I understand this is a minor bug (and the fix is not even urgent as far as I am 
concerned, as I was able to export my field using Gmsh 2.14.0), but it is 
useful to report it anyway.


Best regards,
Marco Tiberga
PhD candidate
Delft University of Technology
Faculty of Applied Sciences
Radiation Science & Technology Department
Mekelweg 15, 2629 JB Delft, The Netherlands
E-Mail: m.tibe...@tudelft.nl<mailto:m.tibe...@tudelft.nl>
Website: http://www.nera.rst.tudelft.nl/


___
gmsh mailing list
gmsh@onelab.info
http://onelab.info/mailman/listinfo/gmsh


Re: [Gmsh] Bug with periodic entities in extruded meshes with layers?

2019-05-02 Thread Marco Tiberga
Dear Christophe,

Thanks a lot for your fast response! 
I will download the newest version as soon as it becomes available. In the 
meantime, the workaround you suggested did work.

Thanks again.

Kind regards,
Marco Tiberga
PhD candidate
Delft University of Technology
Faculty of Applied Sciences
Radiation Science & Technology Department
Mekelweg 15, 2629 JB Delft, The Netherlands
E-Mail: m.tibe...@tudelft.nl
Website: http://www.nera.rst.tudelft.nl/



-Original Message-
From: Christophe Geuzaine [mailto:cgeuza...@uliege.be] 
Sent: woensdag 1 mei 2019 15:26
To: Marco Tiberga
Cc: gmsh@onelab.info; Koen Hillewaert
Subject: Re: [Gmsh] Bug with periodic entities in extruded meshes with layers?



> On 1 May 2019, at 14:13, Marco Tiberga  wrote:
> 
> Dear Gmsh developers,
>  
> I have recently moved from Gmsh 3.0.6 to the most recent 4.3.0, and I have 
> noticed that the .msh files for extruded meshes with layers are slightly 
> different than before, because they contain periodicity relations.
> To me this is puzzling, because I do not have any periodic mesh. Why are the 
> periodicity relations written even on non-periodic meshes? is there a way to 
> turn this off?
>  
> Second, I have noticed that Gmsh is returning an error when reading these 
> .msh files. I have attached two meshes (2D and 3D) that prove this: the .msh 
> files have been generated from the attached .geo ones. For example, when I 
> open square.msh, I get “Error: Cannot find periodic counterpart of vertex 3 
> on edge 2 nor on 2”.
> Since these are two extremely simple meshes, I was wondering whether there is 
> a bug in the definition of the periodicity relations, or whether some 
> commands I am using need to be changed with the new Gmsh version.
>  

New Gmsh versions indeed output by default periodic node information for 
extruded meshes (see https://gitlab.onelab.info/gmsh/gmsh/issues/439). The 
problem you encountered is due to the fact that the MSH2 writer saves the 
information even if the full mesh is not saved (i.e. only same parts are in 
physical groups).

The error will be fixed in the next development build. (Quick workaround until 
then: set "Mesh.IgnorePeriodicity = 1" when reading the mesh, e.g. "gmsh 
cube.msh -setnumber Mesh.IgnorePeriodicity 1".)

Christophe



> For your information, I have to use the MSH 2.2 format for compatibility with 
> my CFD code.
>  
> Thanks.
>  
> Best regards,
> Marco Tiberga
> PhD candidate
> Delft University of Technology
> Faculty of Applied Sciences
> Radiation Science & Technology Department
> Mekelweg 15, 2629 JB Delft, The Netherlands
> E-Mail: m.tibe...@tudelft.nl
> Website: http://www.nera.rst.tudelft.nl/
>  
>  
> ___
> gmsh mailing list
> gmsh@onelab.info
> http://onelab.info/mailman/listinfo/gmsh

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



___
gmsh mailing list
gmsh@onelab.info
http://onelab.info/mailman/listinfo/gmsh


[Gmsh] Bug with periodic entities in extruded meshes with layers?

2019-05-01 Thread Marco Tiberga
Dear Gmsh developers,

I have recently moved from Gmsh 3.0.6 to the most recent 4.3.0, and I have 
noticed that the .msh files for extruded meshes with layers are slightly 
different than before, because they contain periodicity relations.
To me this is puzzling, because I do not have any periodic mesh. Why are the 
periodicity relations written even on non-periodic meshes? is there a way to 
turn this off?

Second, I have noticed that Gmsh is returning an error when reading these .msh 
files. I have attached two meshes (2D and 3D) that prove this: the .msh files 
have been generated from the attached .geo ones. For example, when I open 
square.msh, I get "Error: Cannot find periodic counterpart of vertex 3 on edge 
2 nor on 2".
Since these are two extremely simple meshes, I was wondering whether there is a 
bug in the definition of the periodicity relations, or whether some commands I 
am using need to be changed with the new Gmsh version.

For your information, I have to use the MSH 2.2 format for compatibility with 
my CFD code.

Thanks.

Best regards,
Marco Tiberga
PhD candidate
Delft University of Technology
Faculty of Applied Sciences
Radiation Science & Technology Department
Mekelweg 15, 2629 JB Delft, The Netherlands
E-Mail: m.tibe...@tudelft.nl<mailto:m.tibe...@tudelft.nl>
Website: http://www.nera.rst.tudelft.nl/




square.geo
Description: square.geo


cube.geo
Description: cube.geo


cube.msh
Description: cube.msh


square.msh
Description: square.msh
___
gmsh mailing list
gmsh@onelab.info
http://onelab.info/mailman/listinfo/gmsh


Re: [Gmsh] mesh from STEP file: correct units

2019-04-24 Thread Marco Tiberga
Dear Max, Victor,

Thanks a lot for your prompt replies!
And yes, your suggestions were both right. With Gmsh 4.3 I can obtain what I 
want.
I was not using the most updated version of Gmsh because my code cannot handle 
the newest mesh format at the moment, but now I have found I can still use the 
2.2 format by setting Mesh.MshFileVersion=2.2.

Thanks again for your help!

Kind regards,
Marco

From: Max Orok [mailto:mo...@mevex.com]
Sent: woensdag 24 april 2019 1:38
To: Marco Tiberga
Cc: gmsh@onelab.info
Subject: Re: [Gmsh] mesh from STEP file: correct units

Hi Marco,

Here is the option you're looking for:
http://gmsh.info/doc/texinfo/gmsh.html#index-Geometry_002eOCCTargetUnit

It looks like it was only introduced in Gmsh 4 and higher, hopefully that isn't 
an issue (h/t Prof Geuzaine and Jeremy Theler).

Here is an earlier thread about the same issue if you need more info:
http://onelab.info/pipermail/gmsh/2019/012965.html

Max

On Tue, Apr 23, 2019 at 5:24 PM Marco Tiberga 
mailto:m.tibe...@tudelft.nl>> wrote:
Dear Gmsh developers,

I want to create a mesh from a STEP file, loading it from a geo file.
The mesh should be in m (as you can see from the step file, line 2916) , but 
from the numbers I visualize in gmsh, I deduce the lengths are still expressed 
in mm (the entire domain should be around 2.5m high, but I see 2500).

How can I perform the units conversion? I tried with
factor = 1.e-3;
allpoints[] = Point "*";
Dilate{{0,0,0},{factor,factor,factor}}{Point{allpoints[]};}
but it does not seem to work.

I attached the .geo and the .stp files I am using. I use Gmsh 3.0.6.

Thanks a lot for your help and sorry if the question is stupid, but I have 
little experience in using gmsh with step files.

Best regards,
Marco Tiberga
PhD candidate
Delft University of Technology
Faculty of Applied Sciences
Radiation Science & Technology Department
Mekelweg 15, 2629 JB Delft, The Netherlands
E-Mail: m.tibe...@tudelft.nl<mailto:m.tibe...@tudelft.nl>
Website: http://www.nera.rst.tudelft.nl/


___
gmsh mailing list
gmsh@onelab.info<mailto:gmsh@onelab.info>
http://onelab.info/mailman/listinfo/gmsh


--
Max Orok
Contractor
www.mevex.com<http://www.mevex.com>

[Image removed by sender.]
___
gmsh mailing list
gmsh@onelab.info
http://onelab.info/mailman/listinfo/gmsh


[Gmsh] .step file editing

2018-05-14 Thread Marco Tiberga
Dear GMSH developers,

I was looking into the GMSH reference manual to see whether it is possible to 
read .STEP files, to edit them, and/or to export them to .geo format.
I guess that the FAQ 4 in Appendix E.4 answers my questions.

However, it is not clear to me whether we can or not delete entities, after 
merging a .STEP file into a .geo one (this feature is both indicated as 
something already available and something coming in a later release).
Also, I was wondering whether the possibility export .STEP files to .geo format 
is actually something coming in the near-future releases or later.

Thanks a lot for the clarification.

Best regards,

Marco Tiberga
PhD candidate
Delft University of Technology
Faculty of Applied Sciences
Radiation Science & Technology Department
Mekelweg 15, 2629 JB Delft, The Netherlands
E-Mail: m.tibe...@tudelft.nl<mailto:m.tibe...@tudelft.nl>
Website: http://www.nera.rst.tudelft.nl/


___
gmsh mailing list
gmsh@onelab.info
http://onelab.info/mailman/listinfo/gmsh