|
[Sponsors] |
Failed: One "Pole" of axisymmetry problem exported to OpenFOAM ("wedge" type) |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
November 17, 2017, 18:13 |
Failed: One "Pole" of axisymmetry problem exported to OpenFOAM ("wedge" type)
|
#1 |
New Member
Join Date: May 2016
Posts: 14
Rep Power: 10 |
Dear all,
I tried to make a domain shown as follows, with one pole only. When it is exported to OpenFOAM, it indicates me the following errors. I checked with both situations but did not find anything wrong. However, the "blockMesh" in OpenFOAM can mesh it well without any errors. So I am suspicious PointWise cannot do the mesh like this. Or could you please give me some hint of it? Thank you. Error: Face processing failed. Info: Check your grid for one of the following invalid situations: Info: * Incompatible BC types used on opposite sides of a baffle or connection. Info: * Non-manifold connectivity. Error: (0) Could not write face files! Warning: Aborted Export CAE. Kind regards, Sam |
|
November 17, 2017, 20:34 |
|
#2 |
Senior Member
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 14 |
Please ZIP the pw file in the picture and attach. I will look at it on Monday when I am back in the office.
|
|
November 18, 2017, 02:43 |
|
#3 |
New Member
Join Date: May 2016
Posts: 14
Rep Power: 10 |
Hi David,
Thank you so much. I have attached the dropbox link as follows. https://www.dropbox.com/sh/n2gb438f6...qBS9ZIoGa?dl=0 Kind regards, Sam |
|
November 20, 2017, 11:28 |
|
#4 |
Senior Member
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 14 |
I have the file.
Which Pointwise version are you using to export the grid? |
|
November 20, 2017, 11:49 |
|
#5 |
Senior Member
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 14 |
The single corner pole is creating an UNSUPPORTED (non-canonical) QuadTri cell. That is, the cell is not a hex, prism, tet, or pyramid. See image.
If you look at the bottom of the Cell Connectivity page, you will see the two, unsupported cell types. The only workaround is to figure out a different way of creating your grid to eliminate these cells from being created. I hope this helps. |
|
November 20, 2017, 18:48 |
|
#6 |
New Member
Join Date: May 2016
Posts: 14
Rep Power: 10 |
Thank you David. I will turn to another option.
From the provided figure, why does it still show there are 81 hexes? I do not quite understand this image means. Thank you. Kind regards, Sam |
|
November 21, 2017, 08:40 |
|
#7 |
New Member
Join Date: May 2016
Posts: 14
Rep Power: 10 |
Dear David,
I want to have a 2D model, which is symmetrical to a line, while I have only meshed one side of the model. Is there any way in Pointwise to automatically generate the other side mesh and keep the "one side mesh" at the same time? I have tried with "mirror" and "periodic". But they both do not help. Mirror will copy the "one side mesh" to the other side but not keep it at the "one side". Periodic does give me the mesh I want, but the orient of the other side mesh is totally opposite to the "one side mesh", leading to the failure of export. So I would like to ask how to do that with Pointwise? Thank you so much. Kind regards, Sam |
|
November 21, 2017, 11:09 |
|
#8 | |
Senior Member
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 14 |
Quote:
Think of a normal hex cell. Pick any edge and move both its end points to the mid-point of the original edge. Both corners of the cell still exist. They just happen to be at the same XYZ location with a zero-length edge between them. Pointwise handles this degenerate topology internally. However, Pointwise has a limitation when exporting these "illegal" cells to UNSTRUCTURED, face-based formats like OpenFOAM. I suggest you contact Pointwise support and report this situation as a bug or feature request. There may be some way of handling this. |
||
November 21, 2017, 11:17 |
|
#9 | |
Senior Member
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 14 |
Quote:
|
||
November 22, 2017, 00:54 |
|
#10 |
New Member
Join Date: May 2016
Posts: 14
Rep Power: 10 |
Dear David,
Thank you for your explicit explanation. I am sorry for my vague description. I will show you my problem with steps. In Image 1, the right hand side mesh is already done, while the left hand side is nothing. I want to "symmetry" the RHS mesh to the left with respect to the middle line. I tried to use mirror, but it cannot preserve the RHS mesh. It is just copied to the LHS. Then I tried to use "periodic", but the export indicates the same error which I have presented before. I checked the orients of both domains, while it turns out the directions are opposite. I think that must be the reason for the failure of export. The directions of both domains are shown as follows, So I would like to ask how to "symmetry" a mesh with respect to a line or a surface. Kind regards, Sam |
|
November 22, 2017, 01:00 |
|
#11 |
New Member
Join Date: May 2016
Posts: 14
Rep Power: 10 |
Dear David,
I do not know how to upload images, so the images are in the following dropbox link. Sorry for bringing the inconvenience. https://www.dropbox.com/sh/lwpbo2no0...r7DyNjZVa?dl=0 Kind regards, Sam |
|
November 22, 2017, 11:34 |
|
#12 | |
Senior Member
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 14 |
Quote:
As you guessed, for 2D export all domains being exported MUST have the same relative orientation. Use Edit, Orient to adjust the domain orientations as needed. If you have both structured and unstructured domains, you must check/change their orientations in two steps.
I hope this helps. Bonus: To attach files to a post on this forum: While editing the post message, you can scroll down to the bottom of the page and use the Manage Attachments button. |
||
November 22, 2017, 19:06 |
|
#13 | |
New Member
Join Date: May 2016
Posts: 14
Rep Power: 10 |
Quote:
Thank you so much! It solved my problem. Kind regards, Sam |
||
December 13, 2017, 23:38 |
|
#14 |
New Member
Join Date: May 2016
Posts: 14
Rep Power: 10 |
Dear David,
I am using the copy-paste approach to do a mesh in Pointwise for a structured mesh for pyfr (e.g. pyfm ) and .gmsh. I have tried 2 ways but all failed 1. Direct conversion to pyfm and then run pyfr. 2. convert to gmsh first and then change it to pyfm and then run pyfr Could you please take a look at my mesh and help me for that? https://www.dropbox.com/sh/trw6byvf5...6W_ac8QWa?dl=0 Thank you in advance. The above 2 ways can correctly convert to pyfm, but when I run pyfr, it will give me the following error, Traceback (most recent call last): File "/usr/local/bin/pyfr", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.5/dist-packages/pyfr/__main__.py", line 110, in main args.process(args) File "/usr/local/lib/python3.5/dist-packages/pyfr/__main__.py", line 235, in process_run args, NativeReader(args.mesh), None, Inifile.load(args.cfg) File "/usr/local/lib/python3.5/dist-packages/pyfr/__main__.py", line 216, in _process_common solver = get_solver(backend, rallocs, mesh, soln, cfg) File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/__init__.py", line 16, in get_solver return get_integrator(backend, systemcls, rallocs, mesh, initsoln, cfg) File "/usr/local/lib/python3.5/dist-packages/pyfr/integrators/__init__.py", line 46, in get_integrator return integrator(backend, systemcls, rallocs, mesh, initsoln, cfg) File "/usr/local/lib/python3.5/dist-packages/pyfr/integrators/std/controllers.py", line 80, in __init__ super().__init__(*args, **kwargs) File "/usr/local/lib/python3.5/dist-packages/pyfr/integrators/std/controllers.py", line 14, in __init__ super().__init__(*args, **kwargs) File "/usr/local/lib/python3.5/dist-packages/pyfr/integrators/std/steppers.py", line 165, in __init__ super().__init__(*args, **kwargs) File "/usr/local/lib/python3.5/dist-packages/pyfr/integrators/std/steppers.py", line 8, in __init__ super().__init__(*args, **kwargs) File "/usr/local/lib/python3.5/dist-packages/pyfr/integrators/std/base.py", line 10, in __init__ super().__init__(*args, **kwargs) File "/usr/local/lib/python3.5/dist-packages/pyfr/integrators/base.py", line 58, in __init__ self._init_system(systemcls, backend, rallocs, mesh, initsoln) File "/usr/local/lib/python3.5/dist-packages/pyfr/integrators/base.py", line 88, in _init_system self.system = systemcls(*args, nreg=self.nreg, cfg=self.cfg) File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/base/system.py", line 58, in __init__ int_inters = self._load_int_inters(rallocs, mesh, elemap) File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/base/system.py", line 116, in _load_int_inters self.cfg) File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/navstokes/inters.py", line 13, in __init__ super().__init__(be, lhs, rhs, elemap, cfg) File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/baseadvecdiff/inters.py", line 12, in __init__ super().__init__(be, lhs, rhs, elemap, cfg) File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/baseadvec/inters.py", line 16, in __init__ self._gen_perm(lhs, rhs) File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/baseadvecdiff/inters.py", line 36, in _gen_perm self._elemap) File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/base/inters.py", line 15, in get_opt_view_perm vm = _get_inter_objs(interside, mat, elemap) File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/base/inters.py", line 11, in _get_inter_objs return [emap[type](eidx, fidx) for type, eidx, fidx, flags in interside] File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/base/inters.py", line 11, in <listcomp> return [emap[type](eidx, fidx) for type, eidx, fidx, flags in interside] File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/base/elements.py", line 346, in get_scal_fpts_for_inter rmap = self._srtd_face_fpts[fidx][eidx] File "/usr/local/lib/python3.5/dist-packages/pyfr/util.py", line 138, in __get__ value = self.fn(instance) File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/base/elements.py", line 109, in _srtd_face_fpts for ffpts in self.basis.facefpts] File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/base/elements.py", line 109, in <listcomp> for ffpts in self.basis.facefpts] File "/usr/local/lib/python3.5/dist-packages/pyfr/solvers/base/elements.py", line 108, in <listcomp> return [[np.array(fuzzysort(pts.tolist(), ffpts)) for pts in plocfpts] File "/usr/local/lib/python3.5/dist-packages/pyfr/nputil.py", line 92, in fuzzysort srtdidx[i:j] = fuzzysort(arr, srtdidx[i:j], dim + 1, tol) File "/usr/local/lib/python3.5/dist-packages/pyfr/nputil.py", line 96, in fuzzysort srtdidx[i:] = fuzzysort(arr, srtdidx[i:], dim + 1, tol) File "/usr/local/lib/python3.5/dist-packages/pyfr/nputil.py", line 85, in fuzzysort arrd = arr[dim] IndexError: list index out of range Kind regards, Sam |
|
December 22, 2017, 15:37 |
|
#15 |
Senior Member
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 14 |
The root problem is that the domain normals (k direction) are not consistently oriented. This will cause the exported grid to be invalid at the interfaces between the mis-oriented domains.
However, I can't get the domain orientations to align (Select all domains; Edit, Orient...) because of the periodic connections in the grid. I had to break the perodicity (Select all domains; Edit, Break Periodic), orient the domains consistently, and then do the export. Please report this case to Pointwise support and log a bug. It seems like orienting the domains should be possible even with periodic boundaries. Good luck. PS - You may also want to consider using a half-grid and a mirror plane instead of periodics. During export, you can optionally choose to mirror the exported grid. See CAE, Set Mirror Plane... |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
time step continuity problem in VAWT simulation | lpz_michele | OpenFOAM Running, Solving & CFD | 5 | February 22, 2018 20:50 |
Inlet patch problems | martyn88 | OpenFOAM Running, Solving & CFD | 6 | April 21, 2017 19:34 |
LES supersonic free jet | martyn88 | OpenFOAM | 22 | April 17, 2015 07:00 |
Problem with calculation of k | sdharmar | OpenFOAM Running, Solving & CFD | 5 | March 21, 2013 09:47 |
user defined function | cfduser | CFX | 0 | April 29, 2006 11:58 |