|
[Sponsors] |
[snappyHexMesh] Snappy fails to load feature edges in VTK format |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
October 31, 2021, 04:09 |
Snappy fails to load feature edges in VTK format
|
#1 |
Senior Member
|
Hello Foamers,
it's been a while since my last time here around! I'm working with OpenFOAM 2012 (.com) on WSL Windows installation. I'm trying to mesh an engine cooling jacket with SHM, and after many trials I realized that I have a feature edges problem (i.e. surfaceFeatureExtract either creates too few or too many edges). To solve this, I'm trying to extract my feature edges with Paraview 5.10 on Windows and saving it as VTK legacy ù8.vtk). Actually Paraview uses the vtk legacy format data file version 5.1. I loaded into my dictionary as follows: features ( { file "wj_features_noGasket.vtk"; level 1; } { file "gasket.vtk"; level 3; } ); But when I run SHM, it stops complaining about the vtk format: Reading features. "eader : "# vtk DataFile Version 5.1 "itle : "vtk output "ataType : "ASCII line:4 tagATASET geomType : UNSTRUCTURED_GRID line:5 tag:POINTS Reading 1026 numbers representing 1026 coordinates. line:349 tag:METADATA Consuming 2 metadata information. line:356 tag:CELLS Reading 1025 cells or faces. --> FOAM FATAL IO ERROR: (openfoam-2012) Wrong token type - expected label (int32), found on line 357: word 'OFFSETS' file: /mnt/c/foamdata/WJ_snappy_kOmega/constant/triSurface/wj_features_noGasket.vtk at line 357. From Foam::Istream& Foam:perator>>(Foam::Istream&, int32_t&) in file primitives/ints/int32/int32IO.C at line 137. FOAM exiting Any clues on why this is happening? Thanks and hope to hear from you soon! Ciao Ivan |
|
October 31, 2021, 05:22 |
|
#2 |
Senior Member
M
Join Date: Dec 2017
Posts: 642
Rep Power: 12 |
Generally, sHM can work with stl, obj and vtk as stated in the docs.
However, I never seen anything else than "eMesh" used in the features subdictionary. Have you seen that anywhere and it worked? |
|
October 31, 2021, 05:35 |
|
#3 | |
Senior Member
|
Quote:
My feeling is that something changed in the new vtk format and it is now no more compatible, but I'd like to ask to the community. |
||
November 1, 2021, 07:14 |
|
#4 |
Senior Member
M
Join Date: Dec 2017
Posts: 642
Rep Power: 12 |
Yes, looks like it. Maybe try with an older Paraview-Version then?
What seems odd to me is, that it says something about cells, faces. I expected only line elements to be in the feature edge files. But I am guessing around here, sorry I am no big help. I'm also interested in the solution, though. |
|
Tags |
#featureedges, #snappyhexmesh, #vtk |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] SnappyHexMesh for internal Flow | vishwa | OpenFOAM Meshing & Mesh Conversion | 24 | June 27, 2016 08:54 |
[snappyHexMesh] No layers in a small gap | bobburnquist | OpenFOAM Meshing & Mesh Conversion | 6 | August 26, 2015 09:38 |
[snappyHexMesh] snappyHexMesh won't work - zeros everywhere! | sc298 | OpenFOAM Meshing & Mesh Conversion | 2 | March 27, 2011 21:11 |
[snappyHexMesh] snappyHexMesh aborting | Tobi | OpenFOAM Meshing & Mesh Conversion | 0 | November 10, 2010 03:23 |
[snappyHexMesh] external flow with snappyHexMesh | chelvistero | OpenFOAM Meshing & Mesh Conversion | 11 | January 15, 2010 19:43 |