CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > OpenFOAM Running, Solving & CFD

bubbleInterTrackFoam in parallel (fluidIndicator)

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

Reply
 
LinkBack Thread Tools Display Modes
Old   January 25, 2011, 10:31
Default bubbleInterTrackFoam in parallel (fluidIndicator)
  #1
Member
 
Patricio Bohorquez
Join Date: Mar 2009
Location: Jaén, Spain
Posts: 94
Rep Power: 8
pbohorquez is on a distinguished road
I tried to run the solver bubbleInterTrackFoam to simulate the rising of a bubble. I am using the recent release of OpenFOAM-1.6-ext, and the tutorial included in it (bubble2D_r0.75mm) worked properly in serial. Other solvers, such as icoFoam, interFoam, etc worked also in parallel. However, when I tried to run bubbleInterTrackFoam in parallel I get the following error:

FOAM parallel run exiting
[0]
[1]
[1] --> FOAM FATAL IO ERROR:
[1] cannot open file
[1]
[1] file:
/home/patricio/OpenFOAM/OpenFOAM-1.6-ext/tutorials/surfaceTracking/bubbleInterTrackFoam/bubble2D_r0.75mm/processor1/0/fluidIndicator
at line 0.
[1]
[1] From function regIOobject::readStream()
[1] in file db/regIOobject/regIOobjectRead.C at line 62.
[1]
FOAM parallel run exiting

I wondered if it is ready to run in parallel. Could you please give me a hint?
pbohorquez is offline   Reply With Quote

Old   January 25, 2011, 12:15
Default
  #2
Senior Member
 
Bernhard
Join Date: Sep 2009
Location: Delft
Posts: 790
Rep Power: 12
Bernhard is on a distinguished road
Maybe this post is helpful?

InterTrackFoam any information
Bernhard is offline   Reply With Quote

Old   January 25, 2011, 13:06
Default
  #3
Member
 
Patricio Bohorquez
Join Date: Mar 2009
Location: Jaén, Spain
Posts: 94
Rep Power: 8
pbohorquez is on a distinguished road
Thanks, I will try some of the recommendations indicated in such thread.

Curiously the field fluidIndicator is created in different ways depending on serial/parallel run. Indeed, createFields.H reads

if(Pstream:arRun())
{
fluidIndicatorPtr = new volScalarField
(
IOobject
(
"fluidIndicator",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
}
else
{
fluidIndicatorPtr = new volScalarField
(
IOobject
(
"fluidIndicator",
runTime.timeName(),
mesh,
IOobject::NO_READ,
IOobject::AUTO_WRITE
),
interface.fluidIndicator()
);
}

volScalarField& fluidIndicator = *fluidIndicatorPtr;

Consequently, I have added the instruction fluidIndicator.write(); recompiled, and run 1 iteration in serial. Once the fluidIndicator is generated into the directory 0, I have decomposed the case. However, a new difficulty develops:

Free surface curvature: min = 1956.9, max = 2111.06, average = 2000.16
Courant Number mean: 2.57742e-17 max: 0.0280881 velocity magnitude: 0.0275979
DILUPBiCG: Solving for Ux, Initial residual = 1, Final residual = 1.76967e-09, No Iterations 4
DILUPBiCG: Solving for Uy, Initial residual = 1, Final residual = 1.59963e-09, No Iterations 4
DILUPBiCG: Solving for Uz, Initial residual = 1, Final residual = 1.70849e-09, No Iterations 4
GAMG: Solving for p, Initial residual = 1, Final residual = 0.000849471, No Iterations 10
GAMG: Solving for p, Initial residual = 4.82015e-08, Final residual = 8.69966e-09, No Iterations 4
time step continuity errors : sum local = 8.4342e-11, global = 3.7332e-11, cumulative = 3.7332e-11
GAMG: Solving for p, Initial residual = 2.37137e-06, Final residual = 7.3812e-09, No Iterations 8
GAMG: Solving for p, Initial residual = 1.02097e-08, Final residual = 8.29022e-09, No Iterations 1
time step continuity errors : sum local = 7.22052e-11, global = 1.90445e-12, cumulative = 3.92365e-11
[0]
[0]
[0] --> FOAM FATAL ERROR:
[0] edge 23 length does not match neighbour by 0.000130093% -- possible edge ordering problem
[0]
[0] From function processorFvPatch::makeWeights(scalarField& w) const
[0] in file faMesh/faPatches/constraint/processor/processorFaPatch.C at line 208.
[0]
FOAM parallel run exiting

Maybe it is related to the 'InterTrackFoam any information' thread, or not?
pbohorquez is offline   Reply With Quote

Old   January 26, 2011, 14:21
Default
  #4
Member
 
Patricio Bohorquez
Join Date: Mar 2009
Location: Jaén, Spain
Posts: 94
Rep Power: 8
pbohorquez is on a distinguished road
In the end there is a function called setFluidIndicator which creates the requested field. However, I am struggling with the decomposition method...
pbohorquez is offline   Reply With Quote

Old   April 6, 2011, 18:26
Default
  #5
Member
 
Elisabet Mas de les Valls
Join Date: Mar 2009
Location: Barcelona, Spain
Posts: 61
Rep Power: 8
elisabet is on a distinguished road
Hi Patricio and others,

I've found exactly the same error. However, when following instructions from InterTrackFoam any information , after running makeFaMesh at each processor the error vanishes. The bad new is that another error appears:
Code:
[0] --> FOAM FATAL ERROR: 
[0] Patch name for point normals correction does not exist
[0] 
[0]     From function freeSurface::freeSurface(...)
[0]     in file freeSurface.C at line 202.
[0] 
FOAM parallel run aborting
[0]
I'm running the tutorial case tank3D with 2 processors (split in z direction, so freesurface remains entirely in processor 1)

Any idea?


elisabet
elisabet is offline   Reply With Quote

Old   March 29, 2012, 12:00
Default
  #6
New Member
 
Ivar de Hoogt
Join Date: Mar 2012
Posts: 3
Rep Power: 5
Ivho is on a distinguished road
This might be an old thread, but still..

The error message
[0] --> FOAM FATAL ERROR:
[0] Patch name for point normals correction does not exist
[0]
[0] From function freeSurface::freeSurface(...)
[0] in file freeSurface.C at line 202.

means your simulation crashes before even getting to the setIndicatorFluid line.
Your faBoundary.gz (and subsequently faceLabels.gz) doesn't have the required patches specified in pointNormalsCorrectionPatches in the freeSurfaceProperties file.
Ivho is offline   Reply With Quote

Old   January 18, 2015, 22:54
Default
  #7
New Member
 
Jason
Join Date: Dec 2014
Location: Shanghai, China
Posts: 7
Rep Power: 2
zbli is on a distinguished road
Hey, guys, I've been facing a same issue as you guys met. I assume that you must have figured it out. Could you give me a hint on this problem. I feel totally mixed up on the decomposePar things. I guess there should be some tricks to deal with the processor assignment as another thread posting that the freeSurface patch should be calculated by processor0.

Thanks!
zbli is offline   Reply With Quote

Reply

Thread Tools
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 On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Script to Run Parallel Jobs in Rocks Cluster asaha OpenFOAM Running, Solving & CFD 12 July 4, 2012 22:51
parallel performance on BX900 uzawa OpenFOAM Installation on Windows, Mac and other Unsupported Platforms 3 September 5, 2011 15:52
HP MPI warning...Distributed parallel processing Peter CFX 10 May 14, 2011 06:17
IcoFoam parallel woes msrinath80 OpenFOAM Running, Solving & CFD 9 July 22, 2007 02:58
Parallel Computing Classes at San Diego Supercomputer Center Jan. 20-22 Amitava Majumdar Main CFD Forum 0 January 5, 1999 13:00


All times are GMT -4. The time now is 12:00.