[Son_Goku]

Hello,

i am trying to run a simulation in FineOpen. The taskmanager starts but after a time it aborts an the message "Flow Solver: Run time error" appears to me.

Can anybody help me?
Where is the problem?

Thanks in advance

[colinda1]

Did the computation start to iterate?
You can see this by opening the .res file in the monitor. If so, then you'll need to analyse the reason for divergence e.g. by saving the solution just before divergence. If it did not start to iterate probably the information at the end of the .std file will tell you more about the cause.

[T_RAZZO]

Hi all,

I'm an engineer student and for my Master Thesis I have to simulate a turbine rotor with NUMECA Fine 6.2. I'm saying about a 75 milion cells mesh done with Hexpress.

I think I have the same problem.



The calculation is steady (for now, but the goal is an NLH calculation) with multigrid setting. The problem is that the software doesn't start to iterate, and after multigrid division passages, the message "RUN TIME ERROR" appears!

Mesh is ok!

I searched some others similar discussions in the forum without solutions for my case.

I copy and paste last part of the std file message, hoping someone can help me to understand what is the problem (this is my first experience with this software).

" hexaFileMng::_importagglo, numbering of elements is assumed compact !
/software/alternate/commercial/numeca/fineopen/6.2/exec/fineopen62/COMMON/numeca_start_version: line 2747: 98430 Killed /software/alternate/commercial/numeca/fineopen/6.2/exec/fineopen62/LINUX/hexa/hexstreamdpx86_64_ompi /nobackup/st/tortorelli/palcus_case_full_rotor/analysis_full_turbine_6pt_steady_M_1_WF_full_annul us_6pt/analysis_full_turbine_6pt_steady_M_1_WF_full_annul us_6pt.run -taskmanager -steering /nobackup/st/tortorelli/palcus_case_full_rotor/analysis_full_turbine_6pt_steady_M_1_WF_full_annul us_6pt/analysis_full_turbine_6pt_steady_M_1_WF_full_annul us_6pt.steering -niversion open62 -parendId 262193 -display :50 -par
--------------------------------------------------------------------------
mpirun has exited due to process rank 0 with PID 64424 on
node aglin23.private.vki.eu 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). "