Appropriate mesh file created in gmsh

[Ali1990dashti]

Dear community,
I am new in using moose and want to import my mesh into moose. I am using an open source code developed on top of moose (called Tiger) to change my mesh from .msh file into a exodus file to visualize it in paraview. I created my mesh using gmsh. Then I used a syntax of Tiger to change the mesh (--mesh-only) but the result which I am seeing in paraview is completely different from what I created in gmsh. My mesh has two blocks and 7 surfaces (uploaded fig). I want to do THM modelling using mentioned code (Tiger) on the uploaded mesh file but I can see the mesh I created. I have no idea what is the problem of my mesh. How can I check if my mesh is correctly prepared for moose? I do appreciate any help in advance.

mesh.zip

[ajacquey]

Hi Ali,

It would help if you share your .geo file you used to create the mesh with gmsh.
Without it, I can only give you some hints to check.

First, did you set the physical blocks in the .geo file?
It is usually done with:

Physical Volume(0) = {1};
Physical Volume(1) = {2};

with 1 and 2 being the volume you creates and 0 and 1 being the block number that you can use in the moose input file.

Then, you can do the same with the boundary surfaces:

Physical Surface("bottom") = {1};

Hope it helps.

[ajacquey]

This is what I mean with the ObjectId values.

[Ali1990dashti]

@ajacquey do you mean the tag number of surfaces and volumes should be reduced and be for example less than 100?

[ajacquey]

Yes,
Your 2 subdomains have now 7406 (unit_3) and 9290 (basement) as IDs.
And your sidesets 9291-9296.

When I first opened the exodus file in Paraview, I got a warning about large numbers but I think I clicked on 'Ok, don't show again' so I cannot see this warning anymore.

I don't know how your python gmsh API works but can you try to set the IDs directly instead of giving names for your physical volumes and surfaces?

[ajacquey]

FYI, I have the same issue with peacock

[GiudGiud]

@ajacquey @Ali1990dashti any news on this?

[Ali1990dashti]

@ajacquey , I changed the mesh but still I cannot see any result in paraview. I installed the last version of moose and also use paraview 5.9.

Changed_mesh.zip

[Ali1990dashti]

@ajacquey , Can I ask which version of paraview and conda are you using? I am seeing different things (almost nothing!!!) in my paraview. For moose also I installed it just two days ago. It has some problems with anaconda and I used following lines to install moose:

conda create -n moose -q -y
conda activate moose
conda install moose-tools
conda install moose-libmesh

[ajacquey]

@Ali1990dashti
I have Paraview 5.9.1
I updated moose and conda in May:
git commit 5cda0d3 on 2021-05-10

[Ali1990dashti]

@ajacquey, problem was my mesh. I was creating physical groups for blocks of my mesh but because of a mistake in a for loop, these physical groups were creating two times. Thanks for all your support. Sorry for my late feedback.