|
[Sponsors] |
June 16, 2013, 08:28 |
coupledMatrix and RegionCoupling - urgent
|
#1 |
Senior Member
mahdi abdollahzadeh
Join Date: Mar 2011
Location: Covilha,Portugal
Posts: 153
Rep Power: 15 |
Dear All
I have compiled coupledmatrix and regioncoupling patches from openfoam 1.6ext in openfoam 2.1x successfully. now Im trying t test the conjucatecavity tutorial for it. But there comes a problem Code:
Reading/calculating face flux field phi --> FOAM FATAL ERROR: Unknown patch field type regionCouple Valid patchField types are : 13 ( processor nonuniformTransformCyclic processorCyclic wedge fixedValue empty cyclicAMI cyclicSlip calculated regionCoupling symmetryPlane sliced cyclic ) From function fvsPatchField<Type>::New I appreciate any idea. Best Mahdi |
|
June 16, 2013, 09:16 |
|
#2 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,975
Blog Entries: 45
Rep Power: 128 |
Hi Mahdi,
Quick answer - read the subsection "3.2.6 Linking new user-defined libraries to existing applications" on the OpenFOAM User Guide: http://www.openfoam.org/docs/user/co...plications.php Best regards, Bruno
__________________
|
|
June 16, 2013, 09:24 |
|
#3 |
Senior Member
mahdi abdollahzadeh
Join Date: Mar 2011
Location: Covilha,Portugal
Posts: 153
Rep Power: 15 |
Hi Bruno
Thanks for the link.I have compiled them as a part of openfoam library not user library. just to explain my more my problem the problem is arising from this line of fvsPatchfieldNew.C when creating phi. Code:
typename patchConstructorTable::iterator cstrIter = patchConstructorTablePtr_->find(patchFieldType); if (cstrIter == patchConstructorTablePtr_->end()) { FatalErrorIn ( "fvsPatchField<Type>::New(const word&, const word&, const fvPatch&" ", const Field<Type>&)" ) << "Unknown patchField type " << patchFieldType << nl << nl << "Valid patchField types are :" << endl << patchConstructorTablePtr_->sortedToc() << exit(FatalError); } Mahdi |
|
June 16, 2013, 09:28 |
|
#4 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,975
Blog Entries: 45
Rep Power: 128 |
Hi Mahdi,
I took a better look at the first post... shouldn't the name to be used be "regionCoupling" and not "regionCouple"? Best regards, Bruno
__________________
|
|
June 16, 2013, 09:37 |
|
#5 |
Senior Member
mahdi abdollahzadeh
Join Date: Mar 2011
Location: Covilha,Portugal
Posts: 153
Rep Power: 15 |
Many thanks for your kind answer Bruno
Regioncouple is the name of regioncouplepolypatch and regioncouplefvpatch. regiongcoupling is the name of fieldpatches. regioncouple patches are based on couplefvpatch. as mentioned here by HRv for openfoam extended, http://www.cfd-online.com/Forums/openfoam-solving/57847-coupled-regions.html, there is sth that is forcing that name of the patch and field should be the same. I checked the corresponding code in openfoam 1.6ext and openfoam 2.1x but i didnt understand where I can solve it. just i should mention that regioncoupling in openfoam 1.6ext is working. best Mahdi |
|
June 16, 2013, 11:00 |
|
#6 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,975
Blog Entries: 45
Rep Power: 128 |
Hi Mahdi,
Mmm... I've taken a look into the source code of 1.6-ext and I found that the file "src/finiteVolume/fields/fvsPatchFields/constraint/regionCouple/regionCoupleFvsPatchField.H" has the following code: Code:
public: //- Runtime type information // TypeName(regionCoupleFvPatch::typeName_()); TypeName("regionCoupling"); So, it's no wonder that "regionCouple" doesn't show up in the list And this probably means that Hrv hasn't fixed this yet, at least on these versions... Best regards, Bruno
__________________
|
|
June 16, 2013, 11:04 |
|
#7 |
Senior Member
mahdi abdollahzadeh
Join Date: Mar 2011
Location: Covilha,Portugal
Posts: 153
Rep Power: 15 |
Hi Burono,
Thanks for checking the codes. But if it is not fixed, how i can run the code in openfoam1.6ext?! Best Mahdi |
|
June 16, 2013, 11:11 |
|
#8 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,975
Blog Entries: 45
Rep Power: 128 |
Hi Mahdi,
Probably there is a hack somewhere in 1.6-ext that forces the loading of the correct class? Best regards, Bruno
__________________
|
|
June 16, 2013, 13:14 |
|
#9 |
Senior Member
mahdi abdollahzadeh
Join Date: Mar 2011
Location: Covilha,Portugal
Posts: 153
Rep Power: 15 |
Hi Bruno
I think that should be hard for me to do. I check the patch type, there is a bool attach , if i make it false, it will pass the privious error but it will blows after the first iteration. Best Mahdi |
|
June 16, 2013, 13:29 |
|
#10 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,975
Blog Entries: 45
Rep Power: 128 |
Hi Mahdi,
Have you tried changing: Code:
TypeName("regionCoupling"); Code:
TypeName("regionCouple"); Best regards, Bruno
__________________
|
|
June 16, 2013, 14:21 |
|
#11 |
Senior Member
mahdi abdollahzadeh
Join Date: Mar 2011
Location: Covilha,Portugal
Posts: 153
Rep Power: 15 |
Many thanks Burono,
Yes I have did it. but I got this Code:
Reading field p --> FOAM FATAL IO ERROR: inconsistent patch and patchField types for patch type regionCouple and patchField type zeroGradient file: /home/mahdi/OpenFOAM/mahdi-2.1.x/applications/conjugateCavity/0/p::boundaryField::right from line 35 to line 35. From function fvPatchField<Type>::New(const fvPatch&, const DimensionedField<Type, volMesh>&, const dictionary&) in file /home/mahdi/OpenFOAM/OpenFOAM-2.1.x/src/finiteVolume/lnInclude/fvPatchFieldNew.C at line 164. FOAM exiting Segmentation fault mahdi |
|
|
|