Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QUESTION] Multi-phase implementation #305

Open
CallumG-Ed opened this issue Apr 21, 2020 · 5 comments
Open

[QUESTION] Multi-phase implementation #305

CallumG-Ed opened this issue Apr 21, 2020 · 5 comments

Comments

@CallumG-Ed
Copy link

CallumG-Ed commented Apr 21, 2020

Hi,

I'm looking to embed the horizonal axis model into a multi-phase solver (olaFlow) and I think I have made all the necesssary arrangement of files etc but I am getting an error:

--> FOAM FATAL IO ERROR: 
Entry 'nu' not found in dictionary "/home/callum/OpenFOAM/callum-v1906/run/currentWaveFlume_3D_Turbine/constant/transportProperties"

I know nu/rho are specified for both phases in the transportProperties file and was wondering if there is an issue with it not being distinguishable by some bit of code? The case setup can be found here. Must add I'm using OFv1906. Any help would be appreciated.

Cheers
Callum

@petebachant
Copy link
Collaborator

I think you've found a bug here. I was looking through my old case setup and it looks like I put another entry for nu outside each of the fluid subdictionaries: https://github.com/petebachant/UNH-RVAT-turbinesFoam/blob/interFoamNearSurface/constant/transportProperties

That's fine in the case where only one fluid interacts with the turbine, but the solver should look up nu in the fluid of interest. However, I do believe rho is looked up properly, and nu is only used to look up Reynolds number if you have Re-dependent foil data.

@CallumG-Ed
Copy link
Author

Hi Pete,

thanks for the quick responce. That was my first thought also as the turbine is only interacting with one fluid I pulled nu outside the subdictionaries. However it resulted in the error:

#0  Foam::error::printStack(Foam::Ostream&) at ??:?
#1  Foam::error::abort() at ??:?
#2  Foam::fv::actuatorLineElement::calculateInflowVelocity(Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh> const&) at ??:?
#3  Foam::fv::actuatorLineElement::calculateForce(Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh> const&) at ??:?
#4  Foam::fv::actuatorLineElement::addSup(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::fvMatrix<Foam::Vector<double> >&, Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh>&) at ??:?
#5  Foam::fv::actuatorLineSource::addSup(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::fvMatrix<Foam::Vector<double> >&, long) at ??:?
#6  Foam::fv::axialFlowTurbineALSource::addSup(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::fvMatrix<Foam::Vector<double> >&, long) at ??:?
#7  ? in ~/OpenFOAM/callum-v1906/platforms/linux64GccDPInt64Opt/bin/olaFlow
#8  ? in ~/OpenFOAM/callum-v1906/platforms/linux64GccDPInt64Opt/bin/olaFlow
#9  __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6
#10  ? in ~/OpenFOAM/callum-v1906/platforms/linux64GccDPInt64Opt/bin/olaFlow

I assumed it was something to do with the nu issue, however I am now wondering if it isn't related. Would you have any additional thoughts on the error above?

All the best,
Callum

@CallumG-Ed
Copy link
Author

All solved now; the issues weren't linked. But nu is definately required as you say outside the subdictionaries.

@petebachant
Copy link
Collaborator

Glad to hear you solved it. That error message wasn't very descriptive!

@chandukec
Copy link

Hi,
I am also trying to include the interPhaseChangeFoam (essentially multiphase) for the turbinesFoam, although it's not giving any error, but it is not at all simulating any thing, the log file corresponding to it is attached herewith. Any suggestion/comment will be a great help.
log_interPhaseChangeFoam.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants