Lithosphere removal (delamination) following continental collision: shape and complexity of observables predicted from 3D numerical models

Upload contains most essential data files from the manuscript. The raw data amount to several TB and cannot be uploaded. <strong>1 Model data</strong> <em>1.1 Models covered</em> Relatively frequent output is available for the reference model (<em>R</em> in paper, see Table S2), prefixed <em>dp10</em>. Limited output is uploaded for models with geometric variations (<em>OSM -&gt; dp19, TSM-&gt;dp26</em>). <em>1.2 Types of data</em> Most files are visualisation files (ending *.<em>vtr</em>). These are intended for loading into the visualisation software Paraview. Files starting with <em>comp_</em> contain the lithological composition field; other visualisation files hold the fields of selected physical parameters. Note that as of the design of the study, the maximum file size allowed for loading into Paraview is ca. 2 GB. This limits the number of fields available according to model size - larger models (geometrical variations) hold therefore less fields. Binary files with ending *.<em>prn</em> are saved model states, from which programs can be rerun. Time information mapping step numbers to years is provided in <em>times...txt</em>. <strong>2 Software for reproduction</strong> The numerical code is not in the public domain, and its use is restricted. A pre-compiled binary is provided and allows reproduction of the main/reference model. We present the input files; however, these cannot be changed freely (equivalent to software distribution), and changes will lead to termination of the program. <em>2.1 Requirements, preparation and use</em> The code is compiled on CentOS with gcc 4.8.2. There is no library dependency, apart from the intrinsic OpenMP and glibc (&gt;= 2.17). The following requirements <em>must</em> be satisfied in order to run it: Linux OS (tested on CentOS and Fedora) &gt; 160 GB shared memory The following provisions are recommended: 16 cores high bandwidth storage storage space <em>O</em>(TB) To prepare, simply unzip the provided snapshot <em>clsd_reproduce_gcc_CentOS.zip</em> in an appropriate directory (cluster). The input file <em>init.t3c</em> sets the initial conditions; the input file <em>mode.t3c </em>controls solver and file output. <em>file.t3c</em> is the pointer to the last output step; if a model snapshot is available as binary dump (*.prn file), setting the pointer to its number allows restarting. For normal usage, create initial condition with executable <em>in3mg</em>, and subsequently run <em>i3mg</em>. This will create snapshots and *.vtr visualisation files. High-performance computing facilities, runtime (months), proper software environment, and training in use of the code, or in the use of the visualisation software, are not provided.