how does mpirun read in the processorN directory contents?

LauraSumner · March 14, 2017, 10:06

Hello
I am trying to solve a problem which requires me to know the first set of coordinates located in the "points" file within each processor directory after I decompose my field.

I am trying to find the place where OpenFOAM accesses this information. Does anyone know in which file this occurs when the mpirun is operated in parallel?

I know that polyMesh accesses this information, but I need to be able to distinguish which part of my geometry the solver is working on.

Hope this makes sense!

Laura

deepsterblue · March 14, 2017, 10:21

Hello Laura,

Try this:
const point& procPoint = mesh.points()[0];

Pout << "First point: " << procPoint << endl;

Where "mesh" is the appropriate polyMesh / fvMesh at the top level of your solver. This should give you the processor and first coordinate for each. This also assumes that each processor has at least one point on it, but that's easy to check before-hand.

LauraSumner · March 14, 2017, 10:31

Hi Sandeep,

Thanks! That was exactly what I needed!

Laura

March 14, 2017, 10:06	how does mpirun read in the processorN directory contents?	#1
LauraSumner New Member Laura Sumner Join Date: Mar 2017 Posts: 13 Rep Power: 9	Hello I am trying to solve a problem which requires me to know the first set of coordinates located in the "points" file within each processor directory after I decompose my field. I am trying to find the place where OpenFOAM accesses this information. Does anyone know in which file this occurs when the mpirun is operated in parallel? I know that polyMesh accesses this information, but I need to be able to distinguish which part of my geometry the solver is working on. Hope this makes sense! Laura

March 14, 2017, 10:21		#2
deepsterblue Senior Member Sandeep Menon Join Date: Mar 2009 Location: Amherst, MA Posts: 403 Rep Power: 25	Hello Laura, Try this: const point& procPoint = mesh.points()[0]; Pout << "First point: " << procPoint << endl; Where "mesh" is the appropriate polyMesh / fvMesh at the top level of your solver. This should give you the processor and first coordinate for each. This also assumes that each processor has at least one point on it, but that's easy to check before-hand. __________________ Sandeep Menon University of Massachusetts Amherst https://github.com/smenon

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[snappyHexMesh] jagged, ragged edges...	ziemowitzima	OpenFOAM Meshing & Mesh Conversion	138	July 24, 2012 00:41
Problem in running ICEM grid in Openfoam	Tarak	OpenFOAM	6	September 9, 2011 18:51
How to read a mesh from a directory other than the default tutorial directory	mali28	OpenFOAM	1	July 6, 2011 15:08
Phase locked average in run time	panara	OpenFOAM	2	February 20, 2008 15:37
Initialize and read a file contents	David Baker	FLUENT	0	July 11, 2005 09:26

March 14, 2017, 10:31		#3
LauraSumner New Member Laura Sumner Join Date: Mar 2017 Posts: 13 Rep Power: 9	Hi Sandeep, Thanks! That was exactly what I needed! Laura