You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have this model with ASPECT 9.6.0 pre on dealii 9.5.0. It runs a 2d visco-platic model of a subduction zone, using the "single Advection, iterated defect correction Stokes".
This issue interrupts the modeling process, during which the nonlinear solver scheme is being processed at a certain timestep. In some cases, it gives out an error: ---------------------------------------------------- Exception within ConsensusAlgorithm on rank 19 on processing: no read access: iostream error Aborting!
In other cases, no error message is given and the model just hangs.
When this happens, the nonlinear solver behaves well and should continue to solve. On the other hand, if I restart the case, it typically continues to run and pass the previous hanging point.
I have a sense that this might be a server-related issue. I have run similar cases on Frontera and never once had this interruption issue. It would be helpful if someone could help me debug this issue.
The text was updated successfully, but these errors were encountered:
As mentioned today, I think it would be useful to see whether there are other parts to the error message. To me this looks like either a file system or a memory issue.
That said, could you try and see whether #6099 makes any difference?
Hi all
I have this model with ASPECT 9.6.0 pre on dealii 9.5.0. It runs a 2d visco-platic model of a subduction zone, using the "single Advection, iterated defect correction Stokes".
This issue interrupts the modeling process, during which the nonlinear solver scheme is being processed at a certain timestep. In some cases, it gives out an error:
---------------------------------------------------- Exception within ConsensusAlgorithm on rank 19 on processing: no read access: iostream error Aborting!
In other cases, no error message is given and the model just hangs.
When this happens, the nonlinear solver behaves well and should continue to solve. On the other hand, if I restart the case, it typically continues to run and pass the previous hanging point.
I have a sense that this might be a server-related issue. I have run similar cases on Frontera and never once had this interruption issue. It would be helpful if someone could help me debug this issue.
The text was updated successfully, but these errors were encountered: