Hello everyone,
I am new user of code saturne and I am performaing some tutorials in order to lern how to use the code.
I found a very good tutorial of mixing turbulent in a T-junction.
However I obtained this following error :
ncoming flow detained for 39 outlet faces on 102
SIGFPE signal (floating point exception) intercepted!
Call stack:
1: 0x7ffe5b2154dd <cs_dot+0xed> (libsaturne.so.0)
2: 0x7ffe5b26a2e9 <prodsc_+0x19> (libsaturne.so.0)
3: 0x7ffe5b04e64d <codits_+0x1109> (libsaturne.so.0)
4: 0x7ffe5b339bf0 <turbke_+0x5e8c> (libsaturne.so.0)
5: 0x7ffe5b1528e7 <tridim_+0x4d17> (libsaturne.so.0)
6: 0x7ffe5b02e834 <caltri_+0x30e0> (libsaturne.so.0)
7: 0x7ffe5b005125 <cs_run+0xa35> (libsaturne.so.0)
8: 0x7ffe5b00460a <main+0x14a> (libsaturne.so.0)
9: 0x7ffe5a9f976d <__libc_start_main+0xed> (libc.so.6)
10: 0x4006c9 <> (cs_solver)
End of stack
I used 1 processor and put The default gradient calculation method at "Iterative method with Least Squares initial-
ization". I had allso the same message when using 2 processors. Moreover, when Ichecked the mesh I did not recieve any error message.
Can someone help me ?
Thnak you very much for your time.
Best regards
turbulence mixing in a T-junction
Forum rules
Please read the forum usage recommendations before posting.
Please read the forum usage recommendations before posting.
-
Yvan Fournier
- Posts: 4220
- Joined: Mon Feb 20, 2012 3:25 pm
Re: turbulence mixing in a T-junction
Hello,
The "Iterative with least squares initialization" gradient is not very useful. Either try "iterative" or "least squares with extended neighborhood".
When checking your mesh, tho only "error messages" you obtain (unless the connectivity is bad) are messages relative to "bad cells". In some cases, some meshes may look good but have "polarization" issues, in which case a solution is to either add relaxation of pressure increase (for steady flows), or add more reconstruction sweeps (slower, but more precise).
Also, you may have your error if your time step is too large.
Could you also please follow the forum usage recommendations relative to the information you provide in your post ?
Regards,
Yvan
The "Iterative with least squares initialization" gradient is not very useful. Either try "iterative" or "least squares with extended neighborhood".
When checking your mesh, tho only "error messages" you obtain (unless the connectivity is bad) are messages relative to "bad cells". In some cases, some meshes may look good but have "polarization" issues, in which case a solution is to either add relaxation of pressure increase (for steady flows), or add more reconstruction sweeps (slower, but more precise).
Also, you may have your error if your time step is too large.
Could you also please follow the forum usage recommendations relative to the information you provide in your post ?
Regards,
Yvan
-
Brian Angel
Re: turbulence mixing in a T-junction
Hello Angelo,
It also seems that you have inflow on the outlet boundary from the error message you sent:
"noming flow detained for 39 outlet faces on 102
SIGFPE signal (floating point exception) intercepted!"
In conjunction with Yvan's advice, you might also try (if you haven't done so already):
- Initialising with a flow velocity such that the flow is going out of the outlet boundary for the first iteration / time step
- Using a first order UD scheme in order to try to get the simulation running and then restart
Also, are you running steady state with a two equation turbulence model or unsteady with the same or a more advanced model, e.g. LES?
Regards,
Brian Angel.
It also seems that you have inflow on the outlet boundary from the error message you sent:
"noming flow detained for 39 outlet faces on 102
SIGFPE signal (floating point exception) intercepted!"
In conjunction with Yvan's advice, you might also try (if you haven't done so already):
- Initialising with a flow velocity such that the flow is going out of the outlet boundary for the first iteration / time step
- Using a first order UD scheme in order to try to get the simulation running and then restart
Also, are you running steady state with a two equation turbulence model or unsteady with the same or a more advanced model, e.g. LES?
Regards,
Brian Angel.
-
OROSHI
Re: turbulence mixing in a T-junction
Hello,
Thank you very much for your reply.
In fact I modified the mesh in SALOME and it is working fine.
Thank you very much for your time.
Best regards
Thank you very much for your reply.
In fact I modified the mesh in SALOME and it is working fine.
Thank you very much for your time.
Best regards
-
OROSHI
Re: turbulence mixing in a T-junction
Dear all,
I am writing to you because i have a error when I launch a parallel calculation (2 CPU).
The caculation works perfectly when the Post_processing format is MED, however when I tried to have an EnSight Gold format and relaunch the calculation I have this message :
[angelo-Precision-WorkStation-T3400:02706] [[53002,1],0] ORTE_ERROR_LOG: Data unpack would read past end of buffer in file ../../../orte/util/nidmap.c at line 398
[angelo-Precision-WorkStation-T3400:02706] [[53002,1],0] ORTE_ERROR_LOG: Data unpack would read past end of buffer in file ../../../../../orte/mca/ess/base/ess_base_nidmap.c at line 62
[angelo-Precision-WorkStation-T3400:02706] [[53002,1],0] ORTE_ERROR_LOG: Data unpack would read past end of buffer in file ../../../../../../orte/mca/ess/env/ess_env_module.c at line 173
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):
orte_ess_base_build_nidmap failed
--> Returned value Data unpack would read past end of buffer (-26) instead of ORTE_SUCCESS
--------------------------------------------------------------------------
[angelo-Precision-WorkStation-T3400:02706] [[53002,1],0] ORTE_ERROR_LOG: Data unpack would read past end of buffer in file ../../../orte/runtime/orte_init.c at line 132
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):
orte_ess_set_name failed
--> Returned value Data unpack would read past end of buffer (-26) instead of ORTE_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems. This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):
ompi_mpi_init: orte_init failed
--> Returned "Data unpack would read past end of buffer" (-26) instead of "Success" (0)
--------------------------------------------------------------------------
*** The MPI_Init() function was called before MPI_INIT was invoked.
*** This is disallowed by the MPI standard.
*** Your MPI job will now abort.
[angelo-Precision-WorkStation-T3400:2706] Abort before MPI_INIT completed successfully; not able to guarantee that all other processes were killed!
****************************
Saving calculation results
****************************
[angelo-Precision-WorkStation-T3400:02705] [[53002,0],0]-[[53002,1],1] mca_oob_tcp_msg_recv: readv failed: Connection reset by peer (104)
--------------------------------------------------------------------------
mpiexec has exited due to process rank 0 with PID 2706 on
node angelo-Precision-WorkStation-T3400 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 mpiexec (as reported here).
--------------------------------------------------------------------------
solver script exited with status 1.
Error running the calculation.
Check code_saturne log (listing) and error* files for details.
Error in calculation stage.
It seems working with 1 processor.
Is someone alredy encountered such error.
Best regards
I am writing to you because i have a error when I launch a parallel calculation (2 CPU).
The caculation works perfectly when the Post_processing format is MED, however when I tried to have an EnSight Gold format and relaunch the calculation I have this message :
[angelo-Precision-WorkStation-T3400:02706] [[53002,1],0] ORTE_ERROR_LOG: Data unpack would read past end of buffer in file ../../../orte/util/nidmap.c at line 398
[angelo-Precision-WorkStation-T3400:02706] [[53002,1],0] ORTE_ERROR_LOG: Data unpack would read past end of buffer in file ../../../../../orte/mca/ess/base/ess_base_nidmap.c at line 62
[angelo-Precision-WorkStation-T3400:02706] [[53002,1],0] ORTE_ERROR_LOG: Data unpack would read past end of buffer in file ../../../../../../orte/mca/ess/env/ess_env_module.c at line 173
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):
orte_ess_base_build_nidmap failed
--> Returned value Data unpack would read past end of buffer (-26) instead of ORTE_SUCCESS
--------------------------------------------------------------------------
[angelo-Precision-WorkStation-T3400:02706] [[53002,1],0] ORTE_ERROR_LOG: Data unpack would read past end of buffer in file ../../../orte/runtime/orte_init.c at line 132
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):
orte_ess_set_name failed
--> Returned value Data unpack would read past end of buffer (-26) instead of ORTE_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems. This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):
ompi_mpi_init: orte_init failed
--> Returned "Data unpack would read past end of buffer" (-26) instead of "Success" (0)
--------------------------------------------------------------------------
*** The MPI_Init() function was called before MPI_INIT was invoked.
*** This is disallowed by the MPI standard.
*** Your MPI job will now abort.
[angelo-Precision-WorkStation-T3400:2706] Abort before MPI_INIT completed successfully; not able to guarantee that all other processes were killed!
****************************
Saving calculation results
****************************
[angelo-Precision-WorkStation-T3400:02705] [[53002,0],0]-[[53002,1],1] mca_oob_tcp_msg_recv: readv failed: Connection reset by peer (104)
--------------------------------------------------------------------------
mpiexec has exited due to process rank 0 with PID 2706 on
node angelo-Precision-WorkStation-T3400 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 mpiexec (as reported here).
--------------------------------------------------------------------------
solver script exited with status 1.
Error running the calculation.
Check code_saturne log (listing) and error* files for details.
Error in calculation stage.
It seems working with 1 processor.
Is someone alredy encountered such error.
Best regards
-
Yvan Fournier
- Posts: 4220
- Joined: Mon Feb 20, 2012 3:25 pm
Re: turbulence mixing in a T-junction
Hello,
Do you have user subroutines or only a setup with the GUI? Could you provide additional details or the setup as recommended in the Forum usage guidelines ?
Best regards,
Yvan
Do you have user subroutines or only a setup with the GUI? Could you provide additional details or the setup as recommended in the Forum usage guidelines ?
Best regards,
Yvan