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

a run time problem

Register Blogs Community New Posts Updated Threads Search

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   August 17, 2016, 07:59
Default a run time problem
  #1
Member
 
Fatemeh
Join Date: Dec 2015
Location: Isfahan,Iran
Posts: 39
Rep Power: 11
fatemehfarshi62 is on a distinguished road
Dear Foamers!
I have run a case with LTSinterFoam. and then wanted to continue it with interDymFoam, after mpirun I face the following error: would any one please help me with that?
[4] --> FOAM FATAL ERROR:
[4]
request for volScalarField rDeltaT from objectRegistry region0 failed
available objects of type volScalarField are

16
(
alpha.water_0
interfaceProperties:K
nut
alpha.water
rho
rAU
k
p_rgh
nu
gh
nu1
p
rho_0
nu2
alpha.air
epsilon
)
[4]
[4]
[4] From function objectRegistry::lookupObject<Type>(const word&) const
[4] in file /home/openfoam/OpenFOAM/OpenFOAM-2.4.0/src/OpenFOAM/lnInclude/objectRegistryTemplates.C at line 198.
[4]
FOAM parallel run aborting
[4]
[4] #0 Foam::error:rintStack(Foam::Ostream&)[3] #0 Foam::error:rintStack(Foam::Ostream&) at ??:?
[0] #1 Foam::error::abort() at ??:?
[1] #1 Foam::error::abort() at ??:?
at ??:?
[3] #1 Foam::error::abort()[5] #1 Foam::error::abort() at ??:?
[4] #1 Foam::error::abort() at ??:?
[2] #1 Foam::error::abort() at ??:?
[0] #2 Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const& Foam:bjectRegistry::lookupObject<Foam::Geometric Field<double, Foam::fvPatchField, Foam::volMesh> >(Foam::word const&) const at ??:?
[1] #2 Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const& Foam:bjectRegistry::lookupObject<Foam::Geometric Field<double, Foam::fvPatchField, Foam::volMesh> >(Foam::word const&) const at ??:?
[5] #2 Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const& Foam:bjectRegistry::lookupObject<Foam::Geometric Field<double, Foam::fvPatchField, Foam::volMesh> >(Foam::word const&) const at ??:?
[3] #2 Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const& Foam:bjectRegistry::lookupObject<Foam::Geometric Field<double, Foam::fvPatchField, Foam::volMesh> >(Foam::word const&) const at ??:?
[4] #2 Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const& Foam:bjectRegistry::lookupObject<Foam::Geometric Field<double, Foam::fvPatchField, Foam::volMesh> >(Foam::word const&) const at ??:?
[0] #3 Foam::fv::localEulerDdtScheme<Foam::Vector<double> >::fvmDdt(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh> const&) at ??:?
at ??:?
[1] #3 Foam::fv::localEulerDdtScheme<Foam::Vector<double> >::fvmDdt(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh> const&)[5] #3 Foam::fv::localEulerDdtScheme<Foam::Vector<double> >::fvmDdt(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh> const&) at ??:?
at ??:?
[2] #2 Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const& Foam:bjectRegistry::lookupObject<Foam::Geometric Field<double, Foam::fvPatchField, Foam::volMesh> >(Foam::word const&) const[3] #3 Foam::fv::localEulerDdtScheme<Foam::Vector<double> >::fvmDdt(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh> const&) at ??:?
[4] #3 Foam::fv::localEulerDdtScheme<Foam::Vector<double> >::fvmDdt(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh> const&) at ??:?
[0] #4 at ??:?
[2] #3 Foam::fv::localEulerDdtScheme<Foam::Vector<double> >::fvmDdt(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh> const&)? at ??:?
[3] #4 at ??:?
[4] #4 at ??:?
[1] #4 at ??:?
[5] #4 ? at ??:?
[0] #5 ?? at ??:?
[2] #4 ? at ??:?
?[3] #5 at ??:?
[1] #5 ? at ??:?
[5] #5 ?? at ??:?
[0] #6 __libc_start_main at ??:?
[4] #5 at ??:?
[2] #5 ?? in "/lib/x86_64-linux-gnu/libc.so.6"
[0] #7 at ??:?
[1] #6 __libc_start_main? at ??:?
[3] #6 __libc_start_main at ??:?
[5] #6 __libc_start_main at ??:?
[4] #6 __libc_start_main? in "/lib/ at ??:?
[2] #6 __libc_start_mainx86_64-linux-gnu/libc.so.6"
[1] #7 in "/lib/x86_64-linux-gnu/libc.so.6"
[5] #7 in "/lib/x86_64-linux-gnu/libc.so.6"
[3] #7 in "/lib/x86_64-linux-gnu/libc.so.6"
[4] #7 at ??:?
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--------------------------------------------------------------------------
??? in "/lib/x86_64-linux-gnu/libc.so.6"
[2] #7 ?? at ??:?
at ??:?
at ??:?
at ??:?
at ??:?
--------------------------------------------------------------------------
mpirun has exited due to process rank 0 with PID 3357 on
node fatemeh-Lenovo-IdeaPad-P400-Touch exiting improperly. There are two reasons this could occur:

1. this process did not call "init" before exiting, but others in
the job did. This can cause a job to hang indefinitely while it waits
for all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.

2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"

This may have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--------------------------------------------------------------------------
[fatemeh-Lenovo-IdeaPad-P400-Touch:03356] 5 more processes have sent help message help-mpi-api.txt / mpi-abort
[fatemeh-Lenovo-IdeaPad-P400-Touch:03356] Set MCA parameter "orte_base_help_aggregate" to 0 to see all help / error messages
fatemehfarshi62 is offline   Reply With Quote

Reply


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


Similar Threads
Thread Thread Starter Forum Replies Last Post
How to export time series of variables for one point? mary mor OpenFOAM Post-Processing 8 July 19, 2017 11:54
Moving mesh Niklas Wikstrom (Wikstrom) OpenFOAM Running, Solving & CFD 122 June 15, 2014 07:20
Unstabil Simulation with chtMultiRegionFoam mbay101 OpenFOAM Running, Solving & CFD 13 December 28, 2013 14:12
mixerVesselAMI2D's mass is not balancing sharonyue OpenFOAM Running, Solving & CFD 6 June 10, 2013 10:34
IcoFoam parallel woes msrinath80 OpenFOAM Running, Solving & CFD 9 July 22, 2007 03:58


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