<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Unable to Run Delft3D-FM with Sigma Layers in Parallel on Linux Cluster</title>
  <link rel="self" href="https://dlt-acc.firelay.cloud/en/c/message_boards/find_thread?p_l_id=4041874&amp;threadId=4473820" />
  <subtitle>Unable to Run Delft3D-FM with Sigma Layers in Parallel on Linux Cluster</subtitle>
  <id>https://dlt-acc.firelay.cloud/en/c/message_boards/find_thread?p_l_id=4041874&amp;threadId=4473820</id>
  <updated>2026-05-12T16:53:11Z</updated>
  <dc:date>2026-05-12T16:53:11Z</dc:date>
  <entry>
    <title>RE: Unable to Run Delft3D-FM with Sigma Layers in Parallel on Linux Cluster</title>
    <link rel="alternate" href="https://dlt-acc.firelay.cloud/en/c/message_boards/find_message?p_l_id=4041874&amp;messageId=4506902" />
    <author>
      <name>Erik de Goede</name>
    </author>
    <id>https://dlt-acc.firelay.cloud/en/c/message_boards/find_message?p_l_id=4041874&amp;messageId=4506902</id>
    <updated>2021-09-22T06:25:27Z</updated>
    <published>2021-09-22T06:25:27Z</published>
    <summary type="html">Dear Matthew,&lt;br /&gt;&lt;br /&gt;Since your model is running on your personal deskop, this is not a model input problem but  its eems to be related to the software installation on your cliuster.&lt;br /&gt;&lt;br /&gt;Could you run the successful simulation on your own desktop on your cluster as well? Thus, with the same (DIMR)startscript and with the same number of partitions. &lt;br /&gt;This will prove whether or not this is related to the installatiion of the software.&lt;br /&gt;&lt;br /&gt;With kind regards,&lt;br /&gt;Erik de Goede </summary>
    <dc:creator>Erik de Goede</dc:creator>
    <dc:date>2021-09-22T06:25:27Z</dc:date>
  </entry>
  <entry>
    <title>RE: Unable to Run Delft3D-FM with Sigma Layers in Parallel on Linux Cluster</title>
    <link rel="alternate" href="https://dlt-acc.firelay.cloud/en/c/message_boards/find_message?p_l_id=4041874&amp;messageId=4475487" />
    <author>
      <name>Matthew Brand</name>
    </author>
    <id>https://dlt-acc.firelay.cloud/en/c/message_boards/find_message?p_l_id=4041874&amp;messageId=4475487</id>
    <updated>2021-09-09T17:35:45Z</updated>
    <published>2021-09-09T17:32:14Z</published>
    <summary type="html">I wanted to provide a brief update based on my recent testing. I was able to partition the model into a contiguous domain using a smaller number of partitions (n=2), but unfortunately that did not solve the problem either. So, the hypothesis I brought forward on the previous post is incorrect and I have no further explanations for why the model will not work now.</summary>
    <dc:creator>Matthew Brand</dc:creator>
    <dc:date>2021-09-09T17:32:14Z</dc:date>
  </entry>
  <entry>
    <title>Unable to Run Delft3D-FM with Sigma Layers in Parallel on Linux Cluster</title>
    <link rel="alternate" href="https://dlt-acc.firelay.cloud/en/c/message_boards/find_message?p_l_id=4041874&amp;messageId=4473819" />
    <author>
      <name>Matthew Brand</name>
    </author>
    <id>https://dlt-acc.firelay.cloud/en/c/message_boards/find_message?p_l_id=4041874&amp;messageId=4473819</id>
    <updated>2021-09-09T01:13:05Z</updated>
    <published>2021-09-09T01:12:13Z</published>
    <summary type="html">Hi all,&lt;br /&gt;&lt;br /&gt;I&amp;#39;m currently trying to run a 3D Delft3D-FM (Version 2021.03) salinity simulation of an estuary using 10 sigma layers and struggling to get the simulation working on my Linux cluster. What&amp;#39;s strange is that I&amp;#39;m able to get the simulation running in 2D on the same cluster and in full 3D on my person desktop (6 core machine) without any issues, but when I try and run it via DIMR on my 64 core cluster it doesn&amp;#39;t work. I&amp;#39;m running it with 48 cores, and I get the following error:&lt;div class="quote"&gt;&lt;div class="quote-content"&gt;=============================================================================&lt;br /&gt;=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES&lt;br /&gt;=   PID 72679 RUNNING AT dc011&lt;br /&gt;=   EXIT CODE: 11&lt;br /&gt;=   CLEANING UP REMAINING PROCESSES&lt;br /&gt;=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES&lt;br /&gt;===================================================================================&lt;br /&gt;YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11)&lt;br /&gt;This typically refers to a problem with your application.&lt;br /&gt;Please see the FAQ page for debugging suggestions&lt;/div&gt;&lt;/div&gt;Unfortunately my .dia file isn&amp;#39;t very informative either. I&amp;#39;m partitioning the model using the automatic partition exporter (METIS, PETSC algorithm) in the GUI. I&amp;#39;ve tried other partitioning methods to no success. I&amp;#39;ve attached the full error code and .dia files to this thread.&lt;br /&gt;&lt;br /&gt;One thing I noticed is that my GUI does not contain the &amp;#34;contiguous domains&amp;#34; option which is present in the manual (see images below). Indeed, when I check my partition I see that there are some portions of the model which are discontinuous - is that what could be causing the issue?&lt;br /&gt;&lt;br /&gt;My Delft3D-FM Partition Exporter Options:&lt;br /&gt;&lt;img src="" /&gt;&lt;img src="https://dlt-acc.firelay.cloud/documents/portlet_file_entry/4041089/image--tempRandomSuffix--BtWFuJeF.png/1ab58d9e-9d4b-4406-0788-f2c44bc0d050" /&gt;&lt;br /&gt;Manual Delft3D-FM Partition Exporter Options: &lt;br /&gt;&lt;img src="" /&gt;&lt;img src="https://dlt-acc.firelay.cloud/documents/portlet_file_entry/4041089/image--tempRandomSuffix--ATREKGxT.png/e833d31d-b3bd-c3ce-0d92-a7efb297ddc4" /&gt;&lt;br /&gt;&lt;br /&gt;Example of my discontinuous mesh:&lt;br /&gt;&lt;img src="" /&gt;&lt;img src="https://dlt-acc.firelay.cloud/documents/portlet_file_entry/4041089/image--tempRandomSuffix--C0T4hFjC.png/87645488-2076-5306-db5c-1b71d9f4afe9" /&gt;</summary>
    <dc:creator>Matthew Brand</dc:creator>
    <dc:date>2021-09-09T01:12:13Z</dc:date>
  </entry>
</feed>
