VOF model error:Cortex received a fatal signal (SEGMENTATION VIOLATION)
 

Hello all. I am having some on going issues with my VOF model. Whenever i solve a problem a new error occurs.

Currently my model stops running after only 3.4 seconds of a total 40 second run time with the error: Cortex Received a fatal signal (SEGMENTATION VIOLATION).

The model in simple terms is a 120m long by 5x5m conduit with a mass flow inlet at one end and a pressure outlet at the other. There is 1m high step before the pressure outlet to maintain water levels in the conduit. I use a UDF to raise the volume of water flowing into the model after 10 seconds and then lower it again. Shortly before this some particles are released and tracked from a point array surface in the middle of the tank. The model is meshed at 0.25m res, and the mesh is completely uniform.

I have two systems i am running the model on. One is a linux with 4 cores and plenty of RAM (i access this machine remotely so i don't know precisely how much ram, but i think it is at least 32gb). I use an academic license. The second system is a win 7 pc with only 4gb ram and a core2duo. I'm replacing this machine as it doesn't have the memory capability.

I have tried running the model in both serial and parallel, with both the UDF on, and it replaced with a constant input, and with a shorter (60m rather than 120m) geometry and I still get this error.

Prior to the error the Courant Number is 1.02, all my relaxation factors are set to 0.3. There is a spike in the residuals immediately at the point of error wit z-velocity going rapidly down and everything else up.

Any ideas on what is causing this? Any suggestions on what to try?

any luck solving that problem?
I am receiving the exact same error when importing the grid

i have the same problem with you. if you have know the answer please help me. thank you..

It is ANSYS Developer issue
 

Guys,
Just to let you know..i talked to ANSYS recently and they said it is a developmental issue and there is nothing that you are doing incorrectly.
They said they have worked on Version 16 to get that fixed.
Hold on till then i suppose.
AJS

still having the same issue on Ansys v16.0
 

I am currently using Ansys v16.0...and I am still receiving this error haha...Any suggestions?