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

[OpenFOAM.org] Linking error when building paraview

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

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   January 6, 2021, 13:07
Default Linking error when building paraview
  #1
New Member
 
Join Date: Jan 2019
Posts: 4
Rep Power: 4
kryptomatrix is on a distinguished road
Hello,
I did this on my Arch Linux machine:


git clone https://github.com/OpenFOAM/OpenFOAM-6
git clone https://github.com/OpenFOAM/ThirdParty-6


source OpenFOAM-6/etc/bashrc
cd ThirdParty-6
./Allwmake
./makeParaView




The last command produced linking errors.
See https://www.mediafire.com/file/ck5df...8/out.txt/file for the output of the last command
kryptomatrix is offline   Reply With Quote

Old   January 29, 2021, 15:47
Default
  #2
Senior Member
 
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,178
Rep Power: 29
olesen will become famous soon enougholesen will become famous soon enough
The easiest is to just download a binary pack from kitware and use the built-in OpenFOAM reader. I don't know why everyone thinks that they have to build it themselves.
https://develop.openfoam.com/Develop...raview-plugins
olesen is offline   Reply With Quote

Old   January 29, 2021, 16:19
Default
  #3
New Member
 
Join Date: Jan 2019
Posts: 4
Rep Power: 4
kryptomatrix is on a distinguished road
If I install paraview 5.8.1, and and run "$ paraFoam -builtin" in a case generated by OpenFOAM version 6, should this still work? Because I tried it and paraview thinks that the output of OpenfOAM6 is corrupt.
kryptomatrix is offline   Reply With Quote

Old   January 30, 2021, 06:02
Default
  #4
Senior Member
 
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,178
Rep Power: 29
olesen will become famous soon enougholesen will become famous soon enough
Quote:
Originally Posted by kryptomatrix View Post
If I install paraview 5.8.1, and and run "$ paraFoam -builtin" in a case generated by OpenFOAM version 6, should this still work? Because I tried it and paraview thinks that the output of OpenfOAM6 is corrupt.
This should work without problem, unless your files are indeed corrupt or you have lagrangian positions that are actually barycentric coordinates. Might need to pay attention if you happened to have used OpenFOAM with label-size 64 or single precision.
olesen is offline   Reply With Quote

Old   January 30, 2021, 08:50
Default
  #5
New Member
 
Join Date: Jan 2019
Posts: 4
Rep Power: 4
kryptomatrix is on a distinguished road
Quote:
Originally Posted by olesen View Post
This should work without problem, unless your files are indeed corrupt or you have lagrangian positions that are actually barycentric coordinates. Might need to pay attention if you happened to have used OpenFOAM with label-size 64 or single precision.

Thank, I will try that and open a new bug report if that happens.




Quote:
you have lagrangian positions that are actually barycentric coordinates

This seems oddly specific. What's up with that?
kryptomatrix is offline   Reply With Quote

Old   January 30, 2021, 09:24
Default
  #6
Senior Member
 
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,178
Rep Power: 29
olesen will become famous soon enougholesen will become famous soon enough
Quote:
Originally Posted by kryptomatrix View Post
This seems oddly specific. What's up with that?
The contents of lagrangian positions information has changed a few times. Before OpenFOAM 1.4 it just contained x/y/z/cellid Information. From OpenFOAM 1.4-2.4 (approximately) it contained additional bits for which internal decomposed tet and fraction it contained (helps on restart for OpenFOAM). The reader thus has a toggle in its interface to handle the choice between things. In later versions of OpenFOAM, the internal handling changed radically and started using barycentric coordinates for the internal tracking. This is definitely a good thing, but raises the question about how downstream consumers deal with this change.
The org version made the decision to change the contents of the positions file to now have barycentric coordinates. There is no reasonable method for paraview to deal with this type of content. You (paraview in this case) would need to rebuild the entire volume mesh and perform the identical decomposition and coordinate calculations to determine the x/y/z position of the particle. Even if you manage to get all of this coded and these calculations done, it would mean that you would always need the volume mesh loaded to visualize particle motion!
The com version took a different approach. There the positions file contains x/y/z/cellid like previous versions, and the barycentric coordinates are written in a "coordinates" file. Downstream consumers such as paraview can easily read and process the "positions" file, quickly and easily independently of any volume mesh. The "coordinates" file is used by OpenFOAM for restart. If you really want to save diskspace, can disable writing of the "positions" with an etc/controlDict switch.
I clearly think that this approach is much better.
Probably need to add a mechanism to detect when the positions file actually contains barycentric coordinates etc and then simply reject these instead of giving an error, but then we would need to predict what different types of rubbish get called "positions" and this could be rather difficult.
olesen is offline   Reply With Quote

Old   January 30, 2021, 09:28
Default
  #7
Senior Member
 
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,178
Rep Power: 29
olesen will become famous soon enougholesen will become famous soon enough
Note, could also be that you have a large case in binary? In which case you could be hitting a buffer sizing issue (already patched in the vtk master, but didn't make it in time for the 5.9.0 release). If you suspect this, could try with foamFormatConvert to write as ASCII and load that. That particular bug is for binary only.

Could also try with OpenFOAM-v2012.
olesen is offline   Reply With Quote

Reply

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] Instructions to install OpenFOAM-2.4.x on CentOS-6.10 redbullah OpenFOAM Installation 9 September 7, 2019 17:18
[foam-extend.org] Error compiling OpenFOAM-1.6-ext Canesin OpenFOAM Installation 137 January 20, 2016 14:56
ParaView 3.8.0 problem on debian Unseen OpenFOAM Installation 4 August 16, 2010 10:26
Compilation error OF1.5-dev on Suse10.3 darenyang OpenFOAM Installation 0 April 29, 2009 04:55
OpenFOAM with Cygwin kitchener OpenFOAM Installation 6 April 24, 2006 23:09


All times are GMT -4. The time now is 11:49.