General

General

I have a dynamic mesh case with a sliding interface. The case runs fine without errors or warnings when autosave is disabled (that is, when no .cas/.dat-files are written during the run) independently of the number of processors used. When the case is run with autosave turned on in parallel, I get a number of error messages and then Fluent crashes with a segmentation fault. What is the reason for this error and how can I avoid it?

    • FAQFAQ
      Participant

      The error messages that you get might look like the following ones: Corner nodes should already be created. Corner nodes should already be created. 0: Error: node 0 already marked as 1! 0: Error: node 0 already marked as 1! 0: Error: node 0 already marked as 2! 0: Error: node 0 already marked as 2! … This is a bug in a non-conformal interface optimization code. You can turn this optimization off to prevent the crash by setting the following RP-variable (type the scheme command into the TUI and hit enter): (rpsetvar ‘parallel/si-cleanup-interval 1)