CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > ANSYS > CFX

Store "hidden" information in CFX mesh file

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   June 6, 2018, 13:37
Default Store "hidden" information in CFX mesh file
  #1
New Member
 
Matthias Möller
Join Date: Oct 2017
Posts: 9
Rep Power: 8
mmoelle1 is on a distinguished road
I am using the ANSYS CFD mesh import/export API to generate binary ANSYS mesh files, perform simulations with CFX and read the data from the result files back into our applications to process them further.

Is it possible to store "hidden" information in the CFX mesh file? These "hidden" information would be some meta information telling our application how the mesh file was generated, e.g., a mathematical expression describing how mesh points have been distributed. Meta information could be stored either as text or in binary format.

The very same question applies to the ICEM ASCII format. Is it possible to store extra information, e.g., in form of additional comments there?

Any help is appreciated.

Matthias
mmoelle1 is offline   Reply With Quote

Old   June 6, 2018, 18:41
Default
  #2
Super Moderator
 
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,690
Rep Power: 143
ghorrocks is just really niceghorrocks is just really niceghorrocks is just really niceghorrocks is just really nice
If you are writing your own mesh input/output then can't you write whatever you like in the files?

Some alternative ideas: If the information is small you can put it in the file name. Alternately you can write a second metadata file with the same file name as the mesh file (but a different extension) but contains the metadata. Then the metadata file is clearly linked to the mesh file.
__________________
Note: I do not answer CFD questions by PM. CFD questions should be posted on the forum.
ghorrocks is offline   Reply With Quote

Old   June 7, 2018, 00:37
Default
  #3
New Member
 
Matthias Möller
Join Date: Oct 2017
Posts: 9
Rep Power: 8
mmoelle1 is on a distinguished road
Technically speaking, I can write this information to the file. The question is, under which category I should store it. It’s not vertices, elements, etcetera. Is there a category that is not directly interpreted as mesh entity?
mmoelle1 is offline   Reply With Quote

Old   June 7, 2018, 07:49
Default
  #4
Super Moderator
 
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,690
Rep Power: 143
ghorrocks is just really niceghorrocks is just really niceghorrocks is just really niceghorrocks is just really nice
So aren't you writing your own format? So can't you define it to have anything you like in it, including a spot for metadata?
__________________
Note: I do not answer CFD questions by PM. CFD questions should be posted on the forum.
ghorrocks is offline   Reply With Quote

Old   June 7, 2018, 07:54
Default
  #5
New Member
 
Matthias Möller
Join Date: Oct 2017
Posts: 9
Rep Power: 8
mmoelle1 is on a distinguished road
Apologise for the confusion. In our in-house software, we use our own file format, where we can store all these meta information. Some part of the simulation should be done using ANSYS CFX. For that purpose, we export our mesh data into the binary CFX mesh format using the ANSYS mesh and result file import/export API. The resulting mesh file is imported into CFX5Pre, a case file is created and the CFX5Solver is called.

What I would like to do is to write the meta information (possibly as hidden "vertices", "elements", ...) into the CFX mesh file so that it gets "transported" along the simulation pipeline and is available once we read in the RES files back into our in-house codes.
mmoelle1 is offline   Reply With Quote

Old   June 7, 2018, 08:03
Default
  #6
Super Moderator
 
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,690
Rep Power: 143
ghorrocks is just really niceghorrocks is just really niceghorrocks is just really niceghorrocks is just really nice
You can't do that. The CFX mesh file just contains the mesh and there is nothing in it which just gets passed through to the results file. Well, nothing that I am aware of anyway.

I would extract your metadata and put it in a separate file. Then in your post processing script you can read the meta data file. What sort of meta data are you intending to pass?
__________________
Note: I do not answer CFD questions by PM. CFD questions should be posted on the forum.
ghorrocks is offline   Reply With Quote

Old   June 7, 2018, 08:07
Default
  #7
New Member
 
Matthias Möller
Join Date: Oct 2017
Posts: 9
Rep Power: 8
mmoelle1 is on a distinguished road
A couple of integers (number of grid points in x,y,z direction of a structured grid) and strings of the form 'tan(x/2)' (I could convert them to binary data).

Thanks for your effort. I wanted to avoid separate files since users often combine the mesh file with the wrong meta information file (I have experienced that in the past).
mmoelle1 is offline   Reply With Quote

Old   June 7, 2018, 19:04
Default
  #8
Super Moderator
 
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,690
Rep Power: 143
ghorrocks is just really niceghorrocks is just really niceghorrocks is just really niceghorrocks is just really nice
You can put the file name of the mesh file the metadata refers to in the metadata test file. Also you can have a file name convention which says the mesh file and metadata file have the same file name, only the extension is different. These approaches would minimise the two files getting mixed up.

I cannot see any other option than having a separate metadata file.
__________________
Note: I do not answer CFD questions by PM. CFD questions should be posted on the forum.
ghorrocks is offline   Reply With Quote

Reply

Tags
cfx, icem, mesh and grid

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
[OpenFOAM.org] Error creating ParaView-4.1.0 OpenFOAM 2.3.0 tlcoons OpenFOAM Installation 13 April 20, 2016 17:34
[mesh manipulation] Importing Multiple Meshes thomasnwalshiii OpenFOAM Meshing & Mesh Conversion 18 December 19, 2015 18:57
[swak4Foam] Problem installing swak_2.x for OpenFoam-2.4.0 towanda OpenFOAM Community Contributions 6 September 5, 2015 21:03
"parabolicVelocity" in OpenFoam 2.1.0 ? sawyer86 OpenFOAM Running, Solving & CFD 21 February 7, 2012 11:44
DecomposePar links against liblamso0 with OpenMPI jens_klostermann OpenFOAM Bugs 11 June 28, 2007 17:51


All times are GMT -4. The time now is 01:25.