CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > OpenFOAM Programming & Development

Is there a way to access fvMesh of neighbor region from coupled pointPatch?

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

Reply
 
LinkBack Thread Tools Display Modes
Old   December 16, 2012, 22:55
Default Is there a way to access fvMesh of neighbor region from coupled pointPatch?
  #1
Member
 
yijin Mao
Join Date: May 2010
Location: Columbia, MO
Posts: 45
Rep Power: 7
alundilong is on a distinguished road
Hi,
I'm trying to couple interface points by moving the points at the interface which is shared by two regions simultaneously. (Actually, the shared nodes are two group of nodes, just share the locations)

since I'm moving the nodes, start from the pointPatch will be easier. Now my problems is I cannot access the neighbor region's fvMesh from pointPatch.

turbulentTemperatureCoupledBaffleFvPatchScalarFiel d.H is a good example of doing similar work, but it is on fvPatch level.
alundilong is offline   Reply With Quote

Old   December 16, 2012, 23:15
Default
  #2
Senior Member
 
Sandeep Menon
Join Date: Mar 2009
Location: Amherst, MA
Posts: 386
Rep Power: 15
deepsterblue will become famous soon enough
Its probably better to do this at a higher level, so that fluxes, etc are calculated correctly. You can do that via the mesh.movePoints member. Look at patchToPatchInterpolation to see how it can be done.
__________________
Sandeep Menon
University of Massachusetts Amherst
https://github.com/smenon
deepsterblue is offline   Reply With Quote

Old   December 17, 2012, 14:47
Default
  #3
Member
 
yijin Mao
Join Date: May 2010
Location: Columbia, MO
Posts: 45
Rep Power: 7
alundilong is on a distinguished road
Quote:
Originally Posted by deepsterblue View Post
Its probably better to do this at a higher level, so that fluxes, etc are calculated correctly. You can do that via the mesh.movePoints member. Look at patchToPatchInterpolation to see how it can be done.
Thanks for your suggestion.

I make it happen by giving the regions names through boundary conditions which will be used to find out meshes in neighbour regions as
const dynamicFvMesh & locMesh = mesh.objectRegistry:: parent().lookupObject<dynamicFvMesh>(locRegionName _);
const dynamicFvMesh & nbrMesh = mesh.objectRegistry:: parent().lookupObject<dynamicFvMesh>(nbrRegionName _);

// update boundary patches

vectorField:: operator=(sd);//locPatch

const_cast<dynamicMultiRegionPointPatchCoupled&>
(
nbrField
).vectorField:: operator=(sd);//nbrPatch

// sd is the moving distance of those shared nodes

the test shows it works nice, and the local region's node locations are updated, but I found the node's location is not updated at all in the neighbour region.
alundilong 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
Getting access to mesh (fvMesh) via object registry Chris Lucas OpenFOAM Programming & Development 14 June 4, 2014 05:52
Coupled 1D/3D STAR-CD Training CD adapco Group Marketing CD-adapco 1 November 13, 2002 16:48


All times are GMT -4. The time now is 13:51.