CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   Main CFD Forum (https://www.cfd-online.com/Forums/main/)
-   -   Capillary empty: works but if intially set to fill: crashes (https://www.cfd-online.com/Forums/main/220905-capillary-empty-works-but-if-intially-set-fill-crashes.html)

mcfdma September 26, 2019 09:28

Capillary empty: works but if intially set to fill: crashes
 
Hello.

I am working on electrospray (electrohydrodynamic).

Solver - modified interFoam (which includes electric equations)
OF 2.3.1
Processor - 24
2D axisymmetric model

I inject fluid into the capillary (with a given electric potential/voltage) and further downstream, a ground plate to generate electric field.

Since the experimental flow rate of the fluid flow is extremely slow, I am trying to fill the capillary with the fluid using setFields. However, the simulation does not run and crashes (after several hours and the residual is decreasing but not a single timestep created). This is not the case when the capillary is empty - works perfectly fine.

I have even tried changing my writeFormat from binary to ascii since I got a similar error.
https://www.cfd-online.com/Forums/op...lel-error.html

Error message
Code:

[14] #0  Foam::error::printStack(Foam::Ostream&)--------------------------------------------------------------------------
A process has executed an operation involving a call to the
"fork()" system call to create a child process.  Open MPI is currently
operating in a condition that could result in memory corruption or
other system errors; your job may hang, crash, or produce silent
data corruption.  The use of fork() (or system() or other calls that
create child processes) is strongly discouraged.

The process that invoked fork was: **************************

If you are *absolutely sure* that your application will successfully
and correctly survive a call to fork(), you may disable this warning
by setting the mpi_warn_on_fork MCA parameter to 0.
--------------------------------------------------------------------------
 at ??:?
[14] #1  Foam::sigFpe::sigHandler(int) at ??:?
[14] #2  in "/lib64/libc.so.6"
[14] #3  Foam::GAMGSolver::scale(Foam::Field<double>&, Foam::Field<double>&, Foam::lduMatrix const&, Foam::FieldField<Foam::Field, double> const&, Foam::UPtrList<Foam::lduInterfaceField const> const&, Foam::Field<double> const&, unsigned char) const at ??:?
[14] #4  Foam::GAMGSolver::Vcycle(Foam::PtrList<Foam::lduMatrix::smoother> const&, Foam::Field<double>&, Foam::Field<double> const&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::PtrList<Foam::Field<double> >&, Foam::PtrList<Foam::Field<double> >&, unsigned char) const at ??:?
[14] #5  Foam::GAMGSolver::solve(Foam::Field<double>&, Foam::Field<double> const&, unsigned char) const at ??:?
[14] #6  Foam::fvMatrix<double>::solveSegregated(Foam::dictionary const&) at ??:?
[14] #7  Foam::fvMatrix<double>::solve(Foam::dictionary const&) at ??:?
[14] #8 
[14]  at ??:?
[14] #9  __libc_start_main in "/lib64/libc.so.6"
[14] #10 
[14]  at ??:?
[node734:104299:0:104299] Caught signal 8 (Floating point exception: tkill(2) or tgkill(2))
==== backtrace ====
    0  /opt/apps/libs/ucx/1.5.0/lib/libucs.so.0(+0x1b960) [0x2ab3dbfb6960]
    1  /opt/apps/libs/ucx/1.5.0/lib/libucs.so.0(+0x1bcd3) [0x2ab3dbfb6cd3]
    2  /lib64/libc.so.6(+0x35270) [0x2ab3c2aed270]
    3  /lib64/libc.so.6(gsignal+0x37) [0x2ab3c2aed1f7]
    4  /lib64/libc.so.6(+0x35270) [0x2ab3c2aed270]
    5  /opt/apps/apps/gcc/openfoam/2.3.1/OpenFOAM-2.3.1/platforms/linux64GccDPOpt/lib/libOpenFOAM.so(_ZNK4Foam10GAMGSolver5scaleERNS_5FieldIdEES3_RKNS_9lduMatrixERKNS_10FieldFieldIS1_dEERKNS_8UPtrListIKNS_17lduInterfaceFieldEEERKS2_h+0x99) [0x2ab3c1a580f9]
    6  /opt/apps/apps/gcc/openfoam/2.3.1/OpenFOAM-2.3.1/platforms/linux64GccDPOpt/lib/libOpenFOAM.so(_ZNK4Foam10GAMGSolver6VcycleERKNS_7PtrListINS_9lduMatrix8smootherEEERNS_5FieldIdEERKS8_S9_S9_S9_S9_S9_RNS1_IS8_EESD_h+0x20ba) [0x2ab3c1a5c74a]
    7  /opt/apps/apps/gcc/openfoam/2.3.1/OpenFOAM-2.3.1/platforms/linux64GccDPOpt/lib/libOpenFOAM.so(_ZNK4Foam10GAMGSolver5solveERNS_5FieldIdEERKS2_h+0x656) [0x2ab3c1a5da06]
    8  /opt/apps/apps/gcc/openfoam/2.3.1/OpenFOAM-2.3.1/platforms/linux64GccDPOpt/lib/libfiniteVolume.so(_ZN4Foam8fvMatrixIdE15solveSegregatedERKNS_10dictionaryE+0x15d) [0x2ab3bfdbd46d]
    9  new1interFoam(_ZN4Foam8fvMatrixIdE5solveERKNS_10dictionaryE+0x12c) [0x4a75cc]
  10  new1interFoam() [0x43a1b9]
  11  /lib64/libc.so.6(__libc_start_main+0xf5) [0x2ab3c2ad9c05]
  12  new1interFoam() [0x43efb1]
===================
--------------------------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun noticed that process rank 14 with PID 0 on node node734 exited on signal 8 (Floating point exception).
--------------------------------------------------------------------------


mcfdma September 26, 2019 09:44

2 Attachment(s)
Empty capillary
Attachment 72419

Filled capillary
Attachment 72420

arjun September 27, 2019 07:15

On this site openfoam has the maximum number of fourms.


Why it is so hard to post the openfoam related questions in one of them?

mcfdma September 27, 2019 07:43

Quote:

Originally Posted by arjun (Post 745655)
On this site openfoam has the maximum number of fourms.


Why it is so hard to post the openfoam related questions in one of them?

I tried posting on the OpenFOAM thread but got an error
FORBIDDEN

"You dont have permission to access /Forums/newthread.php on this server", which is why I posted it here.

aadil April 10, 2021 04:21

How are you applying the electric field forces? Are you accounting for charge distribution is only on the free-surface of the liquid?


All times are GMT -4. The time now is 08:14.