|
[Sponsors] |
[OpenFOAM] Problem postprocessing decomposed case with 'paraFoam -builtin' |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
February 17, 2017, 07:13 |
Problem postprocessing decomposed case with 'paraFoam -builtin'
|
#1 | |
New Member
Ben
Join Date: Oct 2016
Posts: 25
Rep Power: 10 |
Hi everyone,
I am new to openfoam (4.1) and currently I'm working on simulations in the field of aerodynamic interactions. I have been using reconstructPar to reconstruct my decomposed case which now takes up a lot of time with a simulation that involves about a thousand timesteps. I have just discovered that I can postprocess my solutions without reconstructing the case by use of the command paraFoam -builtinand then selecting decomposed as the case type and then clicking 'Apply'. At this stage I run into an output error message: Quote:
There must be something that I am doing wrong with my workflow. After setting up the case files (0, constant, system), typically I would run... ...to view my results. My processor* folders do not contain a constant folder. I have been using this workflow for my RANS (simpeFoam) and now URANS (pisoFoam) which is where I have to deal with a large amount of saved timesteps making reconstructPar extremely time consuming hence I stumbled upon the 'paraFoam -builtin' command to work with a decomposed case. Please help! the following are the Dict files which I think may be need to help me solve my problem. Thank you very much! EDIT: also, any feedback regarding my workflow is greatly appreciated! |
||
February 21, 2017, 03:10 |
|
#2 |
New Member
Ben
Join Date: Oct 2016
Posts: 25
Rep Power: 10 |
I seem to have solved the problem. It seems like my workflow was not exactly correct and how I managed the overwriting of files during the snappyHexMesh process.
I followed the workflow in the tutorial: https://www.youtube.com/watch?v=ObsFQUiVi1U and my problem is fixed. Thank you! |
|
February 21, 2017, 04:04 |
|
#3 |
Senior Member
Join Date: Aug 2013
Posts: 407
Rep Power: 16 |
Hi,
Just to add on a bit. You don't need the paraFoam command. In your case folder create a dummy file called, say, case.foam. And open the file with Paraview, and in the Case Type, choose Decomposed. Cheers, Antimony |
|
February 21, 2017, 04:59 |
|
#4 | |
New Member
Ben
Join Date: Oct 2016
Posts: 25
Rep Power: 10 |
Quote:
Just for understanding, is there a difference between the .foam and .openfoam formats? In what way do they differ? I realize this difference in formats since I've adjusted my workflow. Thank you, Ben |
||
February 21, 2017, 05:22 |
|
#5 |
Senior Member
Join Date: Aug 2013
Posts: 407
Rep Power: 16 |
Hi,
Sorry, haven't used much of .OpenFOAM to really comment on it. Typically use .foam and it has always been convenient. If I am not mistaken the built-in OpenFOAMReader needs a .foam extension, but I could be wrong on this. Cheers, Antimony |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[OpenFOAM.com] paraFoam cannot open due to Qt issues - [Solved/Information] | u2berggeist | OpenFOAM Installation | 2 | July 2, 2018 18:03 |
Post-process decomposed case after a simulation | scigowtham | OpenFOAM Post-Processing | 0 | May 7, 2017 04:07 |
Problem running movingCylinders case in parallel with foam-extend-3.1 | mhkenergy | OpenFOAM Running, Solving & CFD | 5 | March 3, 2017 06:20 |
damBreak case parallel run problem | behzad-cfd | OpenFOAM Running, Solving & CFD | 5 | August 2, 2015 18:18 |
successful time step for 2D problem failing for 3D case of same problem. | mandman | Main CFD Forum | 6 | March 10, 2015 20:01 |