UMaine SECS Numerical Modeling Laboratory - User contributions [en]

DualSPHysics Guidelines for Earth Scientists

2019-03-29T16:44:18Z

Nick:

''[[User:Nick | Nick Richmond]], University of Maine''
<h2>History</h2>

<p>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.
</p>

<h2>Structure of DualSPHysics</h2>

<p>The DualSPHysics project represents a collection of codes which can be broken up into three sections:
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing Pre-processing]</h3><strong>GenCase</strong> is the program used to set up the geometry and physics of a DualSPHysics model.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/10.-Processing Processing]</h3><strong>DualSPHysics</strong> is the program used to calculate the motions, etc. of particles within the model domain. This program takes in information from GenCase and outputs binary (.bi4) files. You can't read the binary files directly; they are the inputs for the post-processing codes.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing Post-processing]</h3>There are a litany of post-processing codes in the DualSPHysics project. This allows you to take a modular approach to data generation. Some of them, such as <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#111-visualization-of-particle-output-data-partvtk PartVTK]</strong>, you will use in almost every use case imaginable. Others are more specialized. For example, if you want to calculate the forces exerted on a solid object in your domain, you can use <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#114-force-computation-computeforces ComputeForces4]</strong>.</li>
</ol>

Any given model typically employs GenCase, DualSPHysics, PartVTK, and a handful of other post-processing tools depending on the desired outcome.
</p>

<h2>Resources</h2>

<p>First things first, let's establish where you ought to look for answers to your DualSPHysics questions.
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki The DualSPHysics Wiki on GitHub]</h3>
In 2018, the DualSPHysics project was moved to a [https://github.com/DualSPHysics/DualSPHysics/ GitHub repository]. The [https://github.com/DualSPHysics/DualSPHysics/wiki Wiki section] of the repository should be your go-to resource for all aspects of DualSPHysics, with the exception of model design. At the time of writing (March 2019), the [https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing preprocessing] section of the Wiki lacks the detail of the XML_v4.0_GUIDE.</li>
<li><h3>[[DualSPHysics XML v4.0 GUIDE.pdf|XML_v4.0_GUIDE]]</h3>
In addition to being made available on this wiki (click the heading link), this PDF is included in the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package], and it provides many (but not all) details of the functionality of GenCase, the program used to set up the geometry and physics of a DualSPHysics model.
</li>
<li><h3>[https://dual.sphysics.org/index.php/faq/ DualSPHysics FAQ]</h3>
The DualSPHysics website has a very helpful FAQ section which is updated regularly and addresses a broad range of common questions. Reading through these early on in your DualSPHysics experience will save you time and angst.</li>
<li><h3>doc > xml_format</h3>
Within the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package] there is a <strong>doc</strong> directory containing all sorts of useful documentation. For a deep dive into the full functionality of GenCase, refer to the XML documents in the <strong>xml_format</strong> directory.</li>
</ol>
</p>

<h2>General Pointers</h2>

<p>The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models which faithfully represent the systems you want to model, with minimal frustration.
<ul>
<li>It's wise to familiarize yourself with the example models which ship with the DualSPHysics package. The <strong>examples</strong> directory contains a litany of example models which are categorized in terms of the features they highlight. If you want a high-level overview of these examples without exploring the model results first-hand, you may refer to the [https://github.com/DualSPHysics/DualSPHysics/wiki/12.-Testcases Testcases] section of the DualSPHysics wiki.</li>
<li>Once you're familiar with the example models, you're ready to start experimenting with your own model design. Start by considering which physics (e.g., fluid + fixed structure, fluid + fixed structure + floating objects, fluid + sediment, etc.) and which boundary conditions (e.g., closed system, periodic boundary conditions, open boundary conditions, etc.) will be necessary for your model. From there you can copy an example model which is closest to the system you want to model and adapt it to your needs.</li>
<li>In the early stages of model design, it's best to start with a simple design which is fast to generate. Often the fastest route to a working model is by first running only GenCase, visualizing the outputs in ParaView, and then modifying your case design (XML) file until the geometry is as you would like it to be. From there, you can run DualSPHysics and shift your focus to the quality of the physics simulation. It's usually fastest to run the model at coarse resolution (higher inter-particle distance, or <em>dp</em>), increasing resolution only when the simulation is producing reasonable results.</li>
<li>If working with complex geometries or geospatial data derived from LiDAR, Structure from Motion, or similar, it's best to import the geometry as an [https://en.wikipedia.org/wiki/STL_(file_format) STL] file. The process for this depends entirely on the type of data you're working with, but there are some established routes for distinct use cases:
<ul>
<li> [https://www.blender.org/ Blender] is an excellent program for creating simple or complex surfaces and objects. If I want to create a realistic boulder or a synthetic landscape such as an idealized knickpoint, I would reach for Blender.
</li>
<li> [https://github.com/anoved/phstl phstl] is a Python utility which produces an STL from raster files (GeoTIFFs).
</li>
<li> [https://github.com/NWRichmond/xyz2stl xyz2stl] is a standalone MATLAB app (you don't need MATLAB to run it) that I wrote in 2017 which produces an STL from x,y,z coordinates (such as in a CSV file).
</li>
<li> [https://www.bluemarblegeo.com/products/global-mapper.php Global Mapper] is commercial GIS software which can produce an STL from raster files (GeoTIFFs) using a graphical user interface. This is a good option if you aren't comfortable with something like phstl. Global Mapper is installed on all of the machines in the Computer Cluster on the 2<sup>nd</sup> floor of Bryand Global Sciences Center.
</li>
</ul>
There are many more open source and commercial options for producing the same results. I can personally attest to the utility of the tools listed here, but you might find that software such as [https://www.goldensoftware.com/products/surfer Surfer] or [http://www.meshlab.net/ MeshLab] might best fit your needs.
</li>
</ul>
</p>

<h2>Customizing DualSPHysics</h2>

<p>At the 4th Annual DualSPHysics Users Workshop in Lisbon, Portugal, Orlando García-Feal of University of Vigo delivered an outstanding presentation in which he described the process of customizing DualSPHysics with clarity and detail. You can find the PDF version of his presentation on our wiki: [[Customizing DualSPHysics]].</p>

I think of Orlando's presentation as the definitive template for adding functionality to DualSPHysics, and the code he produced is an official branch of the DualSPHysics repository. This now allows for temperature to be a physical property held by moving fluid particles, with the added benefit of thermal boundary conditions.

<h2>References Cited</h2>

<p><sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.
</p>

DualSPHysics Guidelines for Earth Scientists

2019-03-28T17:08:36Z

Nick:

Smoothed Particle Hydrodynamics

2019-03-28T15:59:29Z

Nick:

== Want to use Smoothed Particle Hydrodynamics (SPH) for your Earth Science Investigation? ==

Please refer to: [[DualSPHysics Guidelines for Earth Scientists]]

== Exploring the Dynamics and Kinematics of Rivers with Smoothed Particle Hydrodynamics (SPH) ==

''[[User:Nick | Nick Richmond]], University of Maine''

Smoothed Particle Hydrodynamics (SPH) provides a meshless solution for fluid mechanics in three dimensions. Unlike traditional computational fluid dynamics methods, SPH is capable of handling violent flows with complex surface dynamics, which makes SPH a useful tool for investigating the motions and forces associated with flow in Earth Systems. So far, I've used SPH for two main projects:
* [[Bedrock Channel Evolution | '''3D bedrock channel evolution with Smoothed Particle Hydrodynamics coupled to a Finite Element Earth''']]
* [[Penobscot River Hydraulics | '''Post-dam removal river hydraulics and the influence of derelict industrial logging infrastructure on modern aquatic habitat''']]

{| class="wikitable"
|-
! style="width:330px" | Click on the animated gif to learn more about how we use SPH and Finite Element Analysis to study bedrock channel evolution.
! style="width:330px" | Click on the animated gif to learn more about how we use SPH to study the effects of relict logging structures on aquatic habitat in Maine's Penobscot River.
|-
| [[File:KnickpointMeanderVel01.gif|link=Bedrock Channel Evolution|700px]]
| [[File:BoomIsland01.gif|link=Penobscot River Hydraulics|700px]]
|-
| style="width:330px" | Here, water flows through an eroded knickpoint with several upstream meanders which develop as a result of preferential erosion of weak material.
| style="width:330px" | Here, water flows around an idealized version of a relict logging structure known as a "boom island."
|}

== Exploring the method of smoothed particle hydrodynamics (SPH) and its application to iceberg capsize dynamics ==

''Lynn Kaluzienski, 9/20/2015, University of Maine''

Analytical solutions for problems in fluid dynamics are unavailable for most real world flows. The method of Smoothed Particle Hydrodynamics (SPH) was initially developed for astrophysical problems and has since been used to formulate approximate solutions for equations in fluid dynamics, chiefly the Navier Stokes solution for a weakly compressible fluid. SPH takes the innovative approach of replacing a fluid with an array of particles and solving the Navier Stokes equation on a particle by particle basis. A smoothing function is applied to each individual particle to determine the influence of its neighbors within a certain radius giving more weight to nearby particles. SPH is naturally a meshfree Lagrangian method, providing several benefits over former gridbased techniques in capturing surface accelerations and removing the need of tracking fluid boundaries. One difficulty with the SPH method is the need for a large quantity of particles to achieve the same precision as a gridbased approach. However, recent improvements in computational power such as the widespread use of graphic processing units (GPUs) have made SPH implementation feasible and computationally inexpensive. Several open source codes, such as DualSPHysics, make high resolution SPH simulations easily achievable on computers with multiple GPU processing units. Depending on complexity, several hundred thousand particle simulations can be achieved on the order of minutes to hours on a desktop computer. Largerscale models with millions to even billions of particles can be efficiently computed on supercomputers. The University of Maine SECS Numerical Laboratory currently has SPH simulations running on multiple GPUs. In addition, our collaboration with the Advanced Computing Group at Umaine will allow us to run increasingly complex and higher resolution simulations on one of their supercomputers in the near future.

'''Supporting Literature: Crespo et al 2015, Monaghan 2012'''

{| class="wikitable"
|-
! style="width:500px" | In this model a fluid is initially held in a square configuration along a sloped ramp with open boundaries on both sides. At the the first time step the fluid is allow to flow outward due to the force of gravity and begins to flow down the ramp. Once the fluid particles meet the boundary edge on the right they cross over to the left side of the ramp. During the first few time steps the fluid quickly moves to fill the void on the upper left hand side and crashes with slower moving particles creating a significant splashing effect and the formation of a standing wave. Throughout the simulation this standing wave begins to die out as the flow approaches a state of equilibrium.

Credits: [http://www.dual.sphysics.org DualSPHysics]

'''[[SPH Supporting Animations|Supporting Animations]]'''

'''[[Introductory SPH Iceberg-capsize Simulations]]'''
! {{#ev:youtube|CT239kMKBag}}
|-
|}

'''For DualSPHysics users operating in the UMaine SECS Numerical Modeling Laboratory:'''

Please see the [http://130.111.222.81/mediawiki-1.19.23/images/b/ba/DualSPH_User_Guide.pdf DualSPHysics User Guide] for a basic program tutorial.

DualSPHysics Guidelines for Earth Scientists

2019-03-27T14:44:54Z

Nick:

Smoothed Particle Hydrodynamics

2019-03-27T14:44:21Z

Nick: /* Want to use Smooted Particle Hydrodynamics (SPH) for your Earth Sciences Investigation? */

== Want to use Smooted Particle Hydrodynamics (SPH) for your Earth Science Investigation? ==

Please refer to: [[DualSPHysics Guidelines for Earth Scientists]]

== Exploring the Dynamics and Kinematics of Rivers with Smoothed Particle Hydrodynamics (SPH) ==

''[[User:Nick | Nick Richmond]], University of Maine''

Smoothed Particle Hydrodynamics (SPH) provides a meshless solution for fluid mechanics in three dimensions. Unlike traditional computational fluid dynamics methods, SPH is capable of handling violent flows with complex surface dynamics, which makes SPH a useful tool for investigating the motions and forces associated with flow in Earth Systems. So far, I've used SPH for two main projects:
* [[Bedrock Channel Evolution | '''3D bedrock channel evolution with Smoothed Particle Hydrodynamics coupled to a Finite Element Earth''']]
* [[Penobscot River Hydraulics | '''Post-dam removal river hydraulics and the influence of derelict industrial logging infrastructure on modern aquatic habitat''']]

{| class="wikitable"
|-
! style="width:330px" | Click on the animated gif to learn more about how we use SPH and Finite Element Analysis to study bedrock channel evolution.
! style="width:330px" | Click on the animated gif to learn more about how we use SPH to study the effects of relict logging structures on aquatic habitat in Maine's Penobscot River.
|-
| [[File:KnickpointMeanderVel01.gif|link=Bedrock Channel Evolution|700px]]
| [[File:BoomIsland01.gif|link=Penobscot River Hydraulics|700px]]
|-
| style="width:330px" | Here, water flows through an eroded knickpoint with several upstream meanders which develop as a result of preferential erosion of weak material.
| style="width:330px" | Here, water flows around an idealized version of a relict logging structure known as a "boom island."
|}

== Exploring the method of smoothed particle hydrodynamics (SPH) and its application to iceberg capsize dynamics ==

''Lynn Kaluzienski, 9/20/2015, University of Maine''

Analytical solutions for problems in fluid dynamics are unavailable for most real world flows. The method of Smoothed Particle Hydrodynamics (SPH) was initially developed for astrophysical problems and has since been used to formulate approximate solutions for equations in fluid dynamics, chiefly the Navier Stokes solution for a weakly compressible fluid. SPH takes the innovative approach of replacing a fluid with an array of particles and solving the Navier Stokes equation on a particle by particle basis. A smoothing function is applied to each individual particle to determine the influence of its neighbors within a certain radius giving more weight to nearby particles. SPH is naturally a meshfree Lagrangian method, providing several benefits over former gridbased techniques in capturing surface accelerations and removing the need of tracking fluid boundaries. One difficulty with the SPH method is the need for a large quantity of particles to achieve the same precision as a gridbased approach. However, recent improvements in computational power such as the widespread use of graphic processing units (GPUs) have made SPH implementation feasible and computationally inexpensive. Several open source codes, such as DualSPHysics, make high resolution SPH simulations easily achievable on computers with multiple GPU processing units. Depending on complexity, several hundred thousand particle simulations can be achieved on the order of minutes to hours on a desktop computer. Largerscale models with millions to even billions of particles can be efficiently computed on supercomputers. The University of Maine SECS Numerical Laboratory currently has SPH simulations running on multiple GPUs. In addition, our collaboration with the Advanced Computing Group at Umaine will allow us to run increasingly complex and higher resolution simulations on one of their supercomputers in the near future.

'''Supporting Literature: Crespo et al 2015, Monaghan 2012'''

{| class="wikitable"
|-
! style="width:500px" | In this model a fluid is initially held in a square configuration along a sloped ramp with open boundaries on both sides. At the the first time step the fluid is allow to flow outward due to the force of gravity and begins to flow down the ramp. Once the fluid particles meet the boundary edge on the right they cross over to the left side of the ramp. During the first few time steps the fluid quickly moves to fill the void on the upper left hand side and crashes with slower moving particles creating a significant splashing effect and the formation of a standing wave. Throughout the simulation this standing wave begins to die out as the flow approaches a state of equilibrium.

Credits: [http://www.dual.sphysics.org DualSPHysics]

'''[[SPH Supporting Animations|Supporting Animations]]'''

'''[[Introductory SPH Iceberg-capsize Simulations]]'''
! {{#ev:youtube|CT239kMKBag}}
|-
|}

'''For DualSPHysics users operating in the UMaine SECS Numerical Modeling Laboratory:'''

Please see the [http://130.111.222.81/mediawiki-1.19.23/images/b/ba/DualSPH_User_Guide.pdf DualSPHysics User Guide] for a basic program tutorial.

Smoothed Particle Hydrodynamics

2019-03-27T14:44:11Z

Nick:

== Want to use Smooted Particle Hydrodynamics (SPH) for your Earth Sciences Investigation? ==

Please refer to: [[DualSPHysics Guidelines for Earth Scientists]]

== Exploring the Dynamics and Kinematics of Rivers with Smoothed Particle Hydrodynamics (SPH) ==

''[[User:Nick | Nick Richmond]], University of Maine''

Smoothed Particle Hydrodynamics (SPH) provides a meshless solution for fluid mechanics in three dimensions. Unlike traditional computational fluid dynamics methods, SPH is capable of handling violent flows with complex surface dynamics, which makes SPH a useful tool for investigating the motions and forces associated with flow in Earth Systems. So far, I've used SPH for two main projects:
* [[Bedrock Channel Evolution | '''3D bedrock channel evolution with Smoothed Particle Hydrodynamics coupled to a Finite Element Earth''']]
* [[Penobscot River Hydraulics | '''Post-dam removal river hydraulics and the influence of derelict industrial logging infrastructure on modern aquatic habitat''']]

{| class="wikitable"
|-
! style="width:330px" | Click on the animated gif to learn more about how we use SPH and Finite Element Analysis to study bedrock channel evolution.
! style="width:330px" | Click on the animated gif to learn more about how we use SPH to study the effects of relict logging structures on aquatic habitat in Maine's Penobscot River.
|-
| [[File:KnickpointMeanderVel01.gif|link=Bedrock Channel Evolution|700px]]
| [[File:BoomIsland01.gif|link=Penobscot River Hydraulics|700px]]
|-
| style="width:330px" | Here, water flows through an eroded knickpoint with several upstream meanders which develop as a result of preferential erosion of weak material.
| style="width:330px" | Here, water flows around an idealized version of a relict logging structure known as a "boom island."
|}

== Exploring the method of smoothed particle hydrodynamics (SPH) and its application to iceberg capsize dynamics ==

''Lynn Kaluzienski, 9/20/2015, University of Maine''

Analytical solutions for problems in fluid dynamics are unavailable for most real world flows. The method of Smoothed Particle Hydrodynamics (SPH) was initially developed for astrophysical problems and has since been used to formulate approximate solutions for equations in fluid dynamics, chiefly the Navier Stokes solution for a weakly compressible fluid. SPH takes the innovative approach of replacing a fluid with an array of particles and solving the Navier Stokes equation on a particle by particle basis. A smoothing function is applied to each individual particle to determine the influence of its neighbors within a certain radius giving more weight to nearby particles. SPH is naturally a meshfree Lagrangian method, providing several benefits over former gridbased techniques in capturing surface accelerations and removing the need of tracking fluid boundaries. One difficulty with the SPH method is the need for a large quantity of particles to achieve the same precision as a gridbased approach. However, recent improvements in computational power such as the widespread use of graphic processing units (GPUs) have made SPH implementation feasible and computationally inexpensive. Several open source codes, such as DualSPHysics, make high resolution SPH simulations easily achievable on computers with multiple GPU processing units. Depending on complexity, several hundred thousand particle simulations can be achieved on the order of minutes to hours on a desktop computer. Largerscale models with millions to even billions of particles can be efficiently computed on supercomputers. The University of Maine SECS Numerical Laboratory currently has SPH simulations running on multiple GPUs. In addition, our collaboration with the Advanced Computing Group at Umaine will allow us to run increasingly complex and higher resolution simulations on one of their supercomputers in the near future.

'''Supporting Literature: Crespo et al 2015, Monaghan 2012'''

{| class="wikitable"
|-
! style="width:500px" | In this model a fluid is initially held in a square configuration along a sloped ramp with open boundaries on both sides. At the the first time step the fluid is allow to flow outward due to the force of gravity and begins to flow down the ramp. Once the fluid particles meet the boundary edge on the right they cross over to the left side of the ramp. During the first few time steps the fluid quickly moves to fill the void on the upper left hand side and crashes with slower moving particles creating a significant splashing effect and the formation of a standing wave. Throughout the simulation this standing wave begins to die out as the flow approaches a state of equilibrium.

Credits: [http://www.dual.sphysics.org DualSPHysics]

'''[[SPH Supporting Animations|Supporting Animations]]'''

'''[[Introductory SPH Iceberg-capsize Simulations]]'''
! {{#ev:youtube|CT239kMKBag}}
|-
|}

'''For DualSPHysics users operating in the UMaine SECS Numerical Modeling Laboratory:'''

Please see the [http://130.111.222.81/mediawiki-1.19.23/images/b/ba/DualSPH_User_Guide.pdf DualSPHysics User Guide] for a basic program tutorial.

DualSPHysics Guidelines for Earth Scientists

2019-03-27T14:42:54Z

Nick:

<h2>History</h2>

<p>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.
</p>

<h2>Structure of DualSPHysics</h2>

<p>The DualSPHysics project represents a collection of codes which can be broken up into three sections:
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing Pre-processing]</h3><strong>GenCase</strong> is the program used to set up the geometry and physics of a DualSPHysics model.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/10.-Processing Processing]</h3><strong>DualSPHysics</strong> is the program used to calculate the motions, etc. of particles within the model domain. This program takes in information from GenCase and outputs binary (.bi4) files. You can't read the binary files directly; they are the inputs for the post-processing codes.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing Post-processing]</h3>There are a litany of post-processing codes in the DualSPHysics project. This allows you to take a modular approach to data generation. Some of them, such as <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#111-visualization-of-particle-output-data-partvtk PartVTK]</strong>, you will use in almost every use case imaginable. Others are more specialized. For example, if you want to calculate the forces exerted on a solid object in your domain, you can use <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#114-force-computation-computeforces ComputeForces4]</strong>.</li>
</ol>

Any given model typically employs GenCase, DualSPHysics, PartVTK, and a handful of other post-processing tools depending on the desired outcome.
</p>

<h2>Resources</h2>

<p>First things first, let's establish where you ought to look for answers to your DualSPHysics questions.
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki The DualSPHysics Wiki on GitHub]</h3>
In 2018, the DualSPHysics project was moved to a [https://github.com/DualSPHysics/DualSPHysics/ GitHub repository]. The [https://github.com/DualSPHysics/DualSPHysics/wiki Wiki section] of the repository should be your go-to resource for all aspects of DualSPHysics, with the exception of model design. At the time of writing (March 2019), the [https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing preprocessing] section of the Wiki lacks the detail of the XML_v4.0_GUIDE.</li>
<li><h3>[[DualSPHysics XML v4.0 GUIDE.pdf|XML_v4.0_GUIDE]]</h3>
In addition to being made available on this wiki (click the heading link), this PDF is included in the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package], and it provides many (but not all) details of the functionality of GenCase, the program used to set up the geometry and physics of a DualSPHysics model.
</li>
<li><h3>[https://dual.sphysics.org/index.php/faq/ DualSPHysics FAQ]</h3>
The DualSPHysics website has a very helpful FAQ section which is updated regularly and addresses a broad range of common questions. Reading through these early on in your DualSPHysics experience will save you time and angst.</li>
<li><h3>doc > xml_format</h3>
Within the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package] there is a <strong>doc</strong> directory containing all sorts of useful documentation. For a deep dive into the full functionality of GenCase, refer to the XML documents in the <strong>xml_format</strong> directory.</li>
</ol>
</p>

<h2>General Pointers</h2>

<p>The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models which faithfully represent the systems you want to model, with minimal frustration.
<ul>
<li>It's wise to familiarize yourself with the example models which ship with the DualSPHysics package. The <strong>examples</strong> directory contains a litany of example models which are categorized in terms of the features they highlight. If you want a high-level overview of these examples without exploring the model results first-hand, you may refer to the [https://github.com/DualSPHysics/DualSPHysics/wiki/12.-Testcases Testcases] section of the DualSPHysics wiki.</li>
<li>Once you're familiar with the example models, you're ready to start experimenting with your own model design. Start by considering which physics (e.g., fluid + fixed structure, fluid + fixed structure + floating objects, fluid + sediment, etc.) and which boundary conditions (e.g., closed system, periodic boundary conditions, open boundary conditions, etc.) will be necessary for your model. From there you can copy an example model which is closest to the system you want to model and adapt it to your needs.</li>
<li>In the early stages of model design, it's best to start with a simple design which is fast to generate. Often the fastest route to a working model is by first running only GenCase, visualizing the outputs in ParaView, and then modifying your case design (XML) file until the geometry is as you would like it to be. From there, you can run DualSPHysics and shift your focus to the quality of the physics simulation. It's usually fastest to run the model at coarse resolution (higher inter-particle distance, or <em>dp</em>), increasing resolution only when the simulation is producing reasonable results.</li>
<li>If working with complex geometries or geospatial data derived from LiDAR, Structure from Motion, or similar, it's best to import the geometry as an [https://en.wikipedia.org/wiki/STL_(file_format) STL] file. The process for this depends entirely on the type of data you're working with, but there are some established routes for distinct use cases:
<ul>
<li> [https://www.blender.org/ Blender] is an excellent program for creating simple or complex surfaces and objects. If I want to create a realistic boulder or a synthetic landscape such as an idealized knickpoint, I would reach for Blender.
</li>
<li> [https://github.com/anoved/phstl phstl] is a Python utility which produces an STL from raster files (GeoTIFFs).
</li>
<li> [https://github.com/NWRichmond/xyz2stl xyz2stl] is a standalone MATLAB app (you don't need MATLAB to run it) that I wrote in 2017 which produces an STL from x,y,z coordinates (such as in a CSV file).
</li>
<li> [https://www.bluemarblegeo.com/products/global-mapper.php Global Mapper] is commercial GIS software which can produce an STL from raster files (GeoTIFFs) using a graphical user interface. This is a good option if you aren't comfortable with something like phstl. Global Mapper is installed on all of the machines in the Computer Cluster on the 2<sup>nd</sup> floor of Bryand Global Sciences Center.
</li>
</ul>
There are many more open source and commercial options for producing the same results. I can personally attest to the utility of the tools listed here, but you might find that software such as [https://www.goldensoftware.com/products/surfer Surfer] or [http://www.meshlab.net/ MeshLab] might best fit your needs.
</li>
</ul>
</p>

<h2>Customizing DualSPHysics</h2>

<p>At the 4th Annual DualSPHysics Users Workshop in Lisbon, Portugal, Orlando García-Feal of University of Vigo delivered an outstanding presentation in which he described the process of customizing DualSPHysics with clarity and detail. You can find the PDF version of his presentation on our wiki: [[Customizing DualSPHysics]].</p>

I think of Orlando's presentation as the definitive template for adding functionality to DualSPHysics, and the code he produced is an official branch of the DualSPHysics repository. This now allows for temperature to be a physical property held by moving fluid particles, with the added benefit of thermal boundary conditions.

<h2>References Cited</h2>

<p><sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.
</p>

DualSPHysics Guidelines for Earth Scientists

2019-03-27T14:27:09Z

Nick:

<h2>History</h2>

<p>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.
</p>

<h2>Structure of DualSPHysics</h2>

<p>The DualSPHysics project represents a collection of codes which can be broken up into three sections:
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing Pre-processing]</h3><strong>GenCase</strong> is the program used to set up the geometry and physics of a DualSPHysics model.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/10.-Processing Processing]</h3><strong>DualSPHysics</strong> is the program used to calculate the motions, etc. of particles within the model domain. This program takes in information from GenCase and outputs binary (.bi4) files. You can't read the binary files directly; they are the inputs for the post-processing codes.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing Post-processing]</h3>There are a litany of post-processing codes in the DualSPHysics project. This allows you to take a modular approach to data generation. Some of them, such as <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#111-visualization-of-particle-output-data-partvtk PartVTK]</strong>, you will use in almost every use case imaginable. Others are more specialized. For example, if you want to calculate the forces exerted on a solid object in your domain, you can use <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#114-force-computation-computeforces ComputeForces4]</strong>.</li>
</ol>

Any given model typically employs GenCase, DualSPHysics, PartVTK, and a handful of other post-processing tools depending on the desired outcome.
</p>

<h2>Resources</h2>

<p>First things first, let's establish where you ought to look for answers to your DualSPHysics questions.
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki The DualSPHysics Wiki on GitHub]</h3>
In 2018, the DualSPHysics project was moved to a [https://github.com/DualSPHysics/DualSPHysics/ GitHub repository]. The [https://github.com/DualSPHysics/DualSPHysics/wiki Wiki section] of the repository should be your go-to resource for all aspects of DualSPHysics, with the exception of model design. At the time of writing (March 2019), the [https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing preprocessing] section of the Wiki lacks the detail of the XML_v4.0_GUIDE.</li>
<li><h3>[[DualSPHysics XML v4.0 GUIDE.pdf|XML_v4.0_GUIDE]]</h3>
In addition to being made available on this wiki (click the heading link), this PDF is included in the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package], and it provides many (but not all) details of the functionality of GenCase, the program used to set up the geometry and physics of a DualSPHysics model.
</li>
<li><h3>[https://dual.sphysics.org/index.php/faq/ DualSPHysics FAQ]</h3>
The DualSPHysics website has a very helpful FAQ section which is updated regularly and addresses a broad range of common questions. Reading through these early on in your DualSPHysics experience will save you time and angst.</li>
<li><h3>doc > xml_format</h3>
Within the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package] there is a <strong>doc</strong> directory containing all sorts of useful documentation. For a deep dive into the full functionality of GenCase, refer to the XML documents in the <strong>xml_format</strong> directory.</li>
</ol>
</p>

<h2>General Pointers</h2>

<p>The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models which faithfully represent the systems you want to model, with minimal frustration.
<ul>
<li>It's wise to familiarize yourself with the example models which ship with the DualSPHysics package. The <strong>examples</strong> directory contains a litany of example models which are categorized in terms of the features they highlight. If you want a high-level overview of these examples without exploring the model results first-hand, you may refer to the [https://github.com/DualSPHysics/DualSPHysics/wiki/12.-Testcases Testcases] section of the DualSPHysics wiki.</li>
<li>Once you're familiar with the example models, you're ready to start experimenting with your own model design. Start by considering which physics (e.g., fluid + fixed structure, fluid + fixed structure + floating objects, fluid + sediment, etc.) and which boundary conditions (e.g., closed system, periodic boundary conditions, open boundary conditions, etc.) will be necessary for your model. From there you can copy an example model which is closest to the system you want to model and adapt it to your needs.</li>
<li>In the early stages of model design, it's best to start with a simple design which is fast to generate. Often the fastest route to a working model is by first running only GenCase, visualizing the outputs in ParaView, and then modifying your case design (XML) file until the geometry is as you would like it to be. From there, you can run DualSPHysics and shift your focus to the quality of the physics simulation. It's usually fastest to run the model at coarse resolution (higher inter-particle distance, or <em>dp</em>), increasing resolution only when the simulation is producing reasonable results.</li>
<li>If working with complex geometries or geospatial data derived from LiDAR, Structure from Motion, or similar, it's best to import the geometry as an [https://en.wikipedia.org/wiki/STL_(file_format) STL] file. The process for this depends entirely on the type of data you're working with, but there are some established routes for distinct use cases:
<ul>
<li> [https://www.blender.org/ Blender] is an excellent program for creating simple or complex surfaces and objects. If I want to create a realistic boulder or a synthetic landscape such as an idealized knickpoint, I would reach for Blender.
</li>
<li> [https://github.com/anoved/phstl phstl] is a Python utility which produces an STL from raster files (GeoTIFFs).
</li>
<li> [https://github.com/NWRichmond/xyz2stl xyz2stl] is a standalone MATLAB app (you don't need MATLAB to run it) that I wrote in 2017 which produces an STL from x,y,z coordinates (such as in a CSV file).
</li>
<li> [https://www.bluemarblegeo.com/products/global-mapper.php Global Mapper] is commercial GIS software which can produce an STL from raster files (GeoTIFFs) using a graphical user interface. This is a good option if you aren't comfortable with something like phstl. Global Mapper is installed on all of the machines in the Computer Cluster on the 2<sup>nd</sup> floor of Bryand Global Sciences Center.
</li>
</ul>
There are many more open source and commercial options for producing the same results. I can personally attest to the utility of the tools listed here, but you might find that software such as [https://www.goldensoftware.com/products/surfer Surfer] or [http://www.meshlab.net/ MeshLab] might best fit your needs.
</li>
</ul>
</p>

<h2>Customizing DualSPHysics</h2>

<p>At the 4th Annual DualSPHysics Users Workshop in Lisbon, Portugal, Orlando García-Feal of University of Vigo delivered an outstanding presentation in which he described the process of customizing DualSPHysics with clarity and detail. You can find the PDF version of his presentation on our wiki: [[Customizing DualSPHysics]].</p>

<h2>References Cited</h2>

<p><sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.
</p>

Customizing DualSPHysics

2019-03-27T14:14:46Z

Nick: Created page with "The following was presented on October 23, 2018 by Orlando García-Feal of University of Vigo at the 4th Annual DualSPHysics Users Workshop in Lisbon, Portugal. <pdf>File:Dev..."

The following was presented on October 23, 2018 by Orlando García-Feal of University of Vigo at the 4th Annual DualSPHysics Users Workshop in Lisbon, Portugal.

<pdf>File:Developing on DualSPHysics.pdf</pdf>

File:Developing on DualSPHysics.pdf

2019-03-27T14:13:00Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T04:40:01Z

Nick:

<h2>History</h2>

<p>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.
</p>

<h2>Structure of DualSPHysics</h2>

<p>The DualSPHysics project represents a collection of codes which can be broken up into three sections:
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing Pre-processing]</h3><strong>GenCase</strong> is the program used to set up the geometry and physics of a DualSPHysics model.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/10.-Processing Processing]</h3><strong>DualSPHysics</strong> is the program used to calculate the motions, etc. of particles within the model domain. This program takes in information from GenCase and outputs binary (.bi4) files. You can't read the binary files directly; they are the inputs for the post-processing codes.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing Post-processing]</h3>There are a litany of post-processing codes in the DualSPHysics project. This allows you to take a modular approach to data generation. Some of them, such as <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#111-visualization-of-particle-output-data-partvtk PartVTK]</strong>, you will use in almost every use case imaginable. Others are more specialized. For example, if you want to calculate the forces exerted on a solid object in your domain, you can use <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#114-force-computation-computeforces ComputeForces4]</strong>.</li>
</ol>

Any given model typically employs GenCase, DualSPHysics, PartVTK, and a handful of other post-processing tools depending on the desired outcome.
</p>

<h2>Resources</h2>

<p>First things first, let's establish where you ought to look for answers to your DualSPHysics questions.
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki The DualSPHysics Wiki on GitHub]</h3>
In 2018, the DualSPHysics project was moved to a [https://github.com/DualSPHysics/DualSPHysics/ GitHub repository]. The [https://github.com/DualSPHysics/DualSPHysics/wiki Wiki section] of the repository should be your go-to resource for all aspects of DualSPHysics, with the exception of model design. At the time of writing (March 2019), the [https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing preprocessing] section of the Wiki lacks the detail of the XML_v4.0_GUIDE.</li>
<li><h3>[[DualSPHysics XML v4.0 GUIDE.pdf|XML_v4.0_GUIDE]]</h3>
In addition to being made available on this wiki (click the heading link), this PDF is included in the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package], and it provides many (but not all) details of the functionality of GenCase, the program used to set up the geometry and physics of a DualSPHysics model.
</li>
<li><h3>[https://dual.sphysics.org/index.php/faq/ DualSPHysics FAQ]</h3>
The DualSPHysics website has a very helpful FAQ section which is updated regularly and addresses a broad range of common questions. Reading through these early on in your DualSPHysics experience will save you time and angst.</li>
<li><h3>doc > xml_format</h3>
Within the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package] there is a <strong>doc</strong> directory containing all sorts of useful documentation. For a deep dive into the full functionality of GenCase, refer to the XML documents in the <strong>xml_format</strong> directory.</li>
</ol>
</p>

<h2>General Pointers</h2>

<p>The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models which faithfully represent the systems you want to model, with minimal frustration.
<ul>
<li>It's wise to familiarize yourself with the example models which ship with the DualSPHysics package. The <strong>examples</strong> directory contains a litany of example models which are categorized in terms of the features they highlight. If you want a high-level overview of these examples without exploring the model results first-hand, you may refer to the [https://github.com/DualSPHysics/DualSPHysics/wiki/12.-Testcases Testcases] section of the DualSPHysics wiki.</li>
<li>Once you're familiar with the example models, you're ready to start experimenting with your own model design. Start by considering which physics (e.g., fluid + fixed structure, fluid + fixed structure + floating objects, fluid + sediment, etc.) and which boundary conditions (e.g., closed system, periodic boundary conditions, open boundary conditions, etc.) will be necessary for your model. From there you can copy an example model which is closest to the system you want to model and adapt it to your needs.</li>
<li>In the early stages of model design, it's best to start with a simple design which is fast to generate. Often the fastest route to a working model is by first running only GenCase, visualizing the outputs in ParaView, and then modifying your case design (XML) file until the geometry is as you would like it to be. From there, you can run DualSPHysics and shift your focus to the quality of the physics simulation. It's usually fastest to run the model at coarse resolution (higher inter-particle distance, or <em>dp</em>), increasing resolution only when the simulation is producing reasonable results.</li>
<li>If working with complex geometries or geospatial data derived from LiDAR, Structure from Motion, or similar, it's best to import the geometry as an [https://en.wikipedia.org/wiki/STL_(file_format) STL] file. The process for this depends entirely on the type of data you're working with, but there are some established routes for distinct use cases:
<ul>
<li> [https://www.blender.org/ Blender] is an excellent program for creating simple or complex surfaces and objects. If I want to create a realistic boulder or a synthetic landscape such as an idealized knickpoint, I would reach for Blender.
</li>
<li> [https://github.com/anoved/phstl phstl] is a Python utility which produces an STL from raster files (GeoTIFFs).
</li>
<li> [https://github.com/NWRichmond/xyz2stl xyz2stl] is a standalone MATLAB app (you don't need MATLAB to run it) that I wrote in 2017 which produces an STL from x,y,z coordinates (such as in a CSV file).
</li>
<li> [https://www.bluemarblegeo.com/products/global-mapper.php Global Mapper] is commercial GIS software which can produce an STL from raster files (GeoTIFFs) using a graphical user interface. This is a good option if you aren't comfortable with something like phstl. Global Mapper is installed on all of the machines in the Computer Cluster on the 2<sup>nd</sup> floor of Bryand Global Sciences Center.
</li>
</ul>
There are many more open source and commercial options for producing the same results. I can personally attest to the utility of the tools listed here, but you might find that software such as [https://www.goldensoftware.com/products/surfer Surfer] or [http://www.meshlab.net/ MeshLab] might best fit your needs.
</li>
</ul>
</p>

<h2>References Cited</h2>

<p><sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.
</p>

DualSPHysics Guidelines for Earth Scientists

2019-03-27T04:38:53Z

Nick:

<h2>History</h2>

<p>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.
</p>

<h2>Structure of DualSPHysics</h2>

<p>The DualSPHysics project represents a collection of codes which can be broken up into three sections:
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing Pre-processing]</h3><strong>GenCase</strong> is the program used to set up the geometry and physics of a DualSPHysics model.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/10.-Processing Processing]</h3><strong>DualSPHysics</strong> is the program used to calculate the motions, etc. of particles within the model domain. This program takes in information from GenCase and outputs binary (.bi4) files. You can't read the binary files directly; they are the inputs for the post-processing codes.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing Post-processing]</h3>There are a litany of post-processing codes in the DualSPHysics project. This allows you to take a modular approach to data generation. Some of them, such as <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#111-visualization-of-particle-output-data-partvtk PartVTK]</strong>, you will use in almost every use case imaginable. Others are more specialized. For example, if you want to calculate the forces exerted on a solid object in your domain, you can use <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#114-force-computation-computeforces ComputeForces4]</strong>.</li>
</ol>

Any given model typically employs GenCase, DualSPHysics, PartVTK, and a handful of other post-processing tools depending on the desired outcome.
</p>

<h2>Resources</h2>

<p>First things first, let's establish where you ought to look for answers to your DualSPHysics questions.
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki The DualSPHysics Wiki on GitHub]</h3>
In 2018, the DualSPHysics project was moved to a [https://github.com/DualSPHysics/DualSPHysics/ GitHub repository]. The [https://github.com/DualSPHysics/DualSPHysics/wiki Wiki section] of the repository should be your go-to resource for all aspects of DualSPHysics, with the exception of model design. At the time of writing (March 2019), the [https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing preprocessing] section of the Wiki lacks the detail of the XML_v4.0_GUIDE.</li>
<li><h3>[[DualSPHysics XML v4.0 GUIDE.pdf|XML_v4.0_GUIDE]]</h3>
In addition to being made available on this wiki (click the heading link), this PDF is included in the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package], and it provides many (but not all) details of the functionality of GenCase, the program used to set up the geometry and physics of a DualSPHysics model.
</li>
<li><h3>[https://dual.sphysics.org/index.php/faq/ DualSPHysics FAQ]</h3>
The DualSPHysics website has a very helpful FAQ section which is updated regularly and addresses a broad range of common questions. Reading through these early on in your DualSPHysics experience will save you time and angst.</li>
<li><h3>doc > xml_format</h3>
Within the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package] there is a <strong>doc</strong> directory containing all sorts of useful documentation. For a deep dive into the full functionality of GenCase, refer to the XML documents in the <strong>xml_format</strong> directory.</li>
</ol>
</p>

<h2>General Pointers</h2>

<p>The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models which faithfully represent the systems you want to model, with minimal frustration.
<ul>
<li>It's wise to familiarize yourself with the example models which ship with the DualSPHysics package. The <strong>examples</strong> directory contains a litany of example models which are categorized in terms of the features they highlight. If you want a high-level overview of these examples without exploring the model results first-hand, you may refer to the [https://github.com/DualSPHysics/DualSPHysics/wiki/12.-Testcases Testcases] section of the DualSPHysics wiki.</li>
<li>Once you're familiar with the example models, you're ready to start experimenting with your own model design. Start by considering which physics (e.g., fluid + fixed structure, fluid + fixed structure + floating objects, fluid + sediment, etc.) and which boundary conditions (e.g., closed system, periodic boundary conditions, open boundary conditions, etc.) will be necessary for your model. From there you can copy an example model which is closest to the system you want to model and adapt it to your needs.</li>
<li>In the early stages of model design, it's best to start with a simple design which is fast to generate. Often the fastest route to a working model is by first running only GenCase, visualizing the outputs in ParaView, and then modifying your case design (XML) file until the geometry is as you would like it to be. From there, you can run DualSPHysics and shift your focus to the quality of the physics simulation. It's usually fastest to run the model at coarse resolution (higher inter-particle distance, or <em>dp</em>), increasing resolution only when the simulation is producing reasonable results.</li>
<li>If working with complex geometries or geospatial data derived from LiDAR, Structure from Motion, or similar, it's best to import the geometry as an [https://en.wikipedia.org/wiki/STL_(file_format) STL] file. The process for this depends entirely on the type of data you're working with, but there are some established routes for distinct use cases:
<ul>
<li> [https://www.blender.org/ Blender] is an excellent program for creating simple or complex surfaces and objects. If I want to create a realistic boulder or a synthetic landscape such as an idealized knickpoint, I would reach for Blender.
</li>
<li> [https://github.com/anoved/phstl phstl] is a Python utility which produces an STL from raster files (GeoTIFFs).
</li>
<li> [https://github.com/NWRichmond/xyz2stl xyz2stl] is a standalone MATLAB app (you don't need MATLAB to run it) that I wrote in 2017 which produces an STL from x,y,z coordinates (such as in a CSV file).
</li>
<li> [https://www.bluemarblegeo.com/products/global-mapper.php Global Mapper] is commercial GIS software which can produce an STL from raster files (GeoTIFFs) using a graphical user interface. This is a good option if you aren't comfortable with something like phstl. Global Mapper is installed on all of the machines in the Computer Cluster on the 2<sup>nd</sup> floor of Bryand Global Sciences Center.
</li>
</ul>
There are many more open source and commercial options for producing the same results, but I can personally attest to the utility of the tools listed here. You might find that software such as [https://www.goldensoftware.com/products/surfer Surfer] or [http://www.meshlab.net/ MeshLab] might best fit your needs.
</li>
</ul>
</p>

<h2>References Cited</h2>

<p><sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.
</p>

DualSPHysics Guidelines for Earth Scientists

2019-03-27T04:38:00Z

Nick:

<h2>History</h2>

<p>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.
</p>

<h2>Structure of DualSPHysics</h2>

<p>The DualSPHysics project represents a collection of codes which can be broken up into three sections:
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing Pre-processing]</h3><strong>GenCase</strong> is the program used to set up the geometry and physics of a DualSPHysics model.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/10.-Processing Processing]</h3><strong>DualSPHysics</strong> is the program used to calculate the motions, etc. of particles within the model domain. This program takes in information from GenCase and outputs binary (.bi4) files. You can't read the binary files directly; they are the inputs for the post-processing codes.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing Post-processing]</h3>There are a litany of post-processing codes in the DualSPHysics project. This allows you to take a modular approach to data generation. Some of them, such as <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#111-visualization-of-particle-output-data-partvtk PartVTK]</strong>, you will use in almost every use case imaginable. Others are more specialized. For example, if you want to calculate the forces exerted on a solid object in your domain, you can use <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#114-force-computation-computeforces ComputeForces4]</strong>.</li>
</ol>

Any given model typically employs GenCase, DualSPHysics, PartVTK, and a handful of other post-processing tools depending on the desired outcome.
</p>

<h2>Resources</h2>

<p>First things first, let's establish where you ought to look for answers to your DualSPHysics questions.
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki The DualSPHysics Wiki on GitHub]</h3>
In 2018, the DualSPHysics project was moved to a [https://github.com/DualSPHysics/DualSPHysics/ GitHub repository]. The [https://github.com/DualSPHysics/DualSPHysics/wiki Wiki section] of the repository should be your go-to resource for all aspects of DualSPHysics, with the exception of model design. At the time of writing (March 2019), the [https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing preprocessing] section of the Wiki lacks the detail of the XML_v4.0_GUIDE.</li>
<li><h3>[[DualSPHysics XML v4.0 GUIDE.pdf|XML_v4.0_GUIDE]]</h3>
In addition to being made available on this wiki (click the heading link), this PDF is included in the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package], and it provides many (but not all) details of the functionality of GenCase, the program used to set up the geometry and physics of a DualSPHysics model.
</li>
<li><h3>[https://dual.sphysics.org/index.php/faq/ DualSPHysics FAQ]</h3>
The DualSPHysics website has a very helpful FAQ section which is updated regularly and addresses a broad range of common questions. Reading through these early on in your DualSPHysics experience will save you time and angst.</li>
<li><h3>doc > xml_format</h3>
Within the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package] there is a <strong>doc</strong> directory containing all sorts of useful documentation. For a deep dive into the full functionality of GenCase, refer to the XML documents in the <strong>xml_format</strong> directory.</li>
</ol>
</p>

<h2>General Pointers</h2>

<p>The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models which faithfully represent the systems you want to model, with minimal frustration.
<ul>
<li>It's wise to familiarize yourself with the example models which ship with the DualSPHysics package. The <strong>examples</strong> directory contains a litany of example models which are categorized in terms of the features they highlight. If you want a high-level overview of these examples without exploring the model results first-hand, you may refer to the [https://github.com/DualSPHysics/DualSPHysics/wiki/12.-Testcases Testcases] section of the DualSPHysics wiki.</li>
<li>Once you're familiar with the example models, you're ready to start experimenting with your own model design. Start by considering which physics (e.g., fluid + fixed structure, fluid + fixed structure + floating objects, fluid + sediment, etc.) and which boundary conditions (e.g., closed system, periodic boundary conditions, open boundary conditions, etc.) will be necessary for your model. From there you can copy an example model which is closest to the system you want to model and adapt it to your needs.</li>
<li>In the early stages of model design, it's best to start with a simple design which is fast to generate. Often the fastest route to a working model is by first running only GenCase, visualizing the outputs in ParaView, and then modifying your case design (XML) file until the geometry is as you would like it to be. From there, you can run DualSPHysics and shift your focus to the quality of the physics simulation. It's usually fastest to run the model at coarse resolution (higher inter-particle distance, or <em>dp</em>), increasing resolution only when the simulation is producing reasonable results.</li>
<li>If working with complex geometries or geospatial data derived from LiDAR, Structure from Motion, or similar, it's best to import the geometry as an [https://en.wikipedia.org/wiki/STL_(file_format) STL] file. The process for this depends entirely on the type of data you're working with, but there are some established routes for distinct use cases:
<ul>
<li> [https://www.blender.org/ Blender] is an excellent program for creating simple or complex surfaces and objects. If I want to create a realistic boulder or a synthetic landscape such as an idealized knickpoint, I would reach for Blender.
</li>
<li> [https://github.com/anoved/phstl phstl] is a Python utility which produces an STL from raster files (GeoTIFFs).
</li>
<li> [https://github.com/NWRichmond/xyz2stl xyz2stl] is a standalone MATLAB app (you don't need MATLAB to run it) that I wrote in 2017 which produces an STL from x,y,z coordinates (such as in a CSV file).
</li>
<li> [https://www.bluemarblegeo.com/products/global-mapper.php Global Mapper] is commercial GIS software which can produce an STL from raster files (GeoTIFFs) using a graphical user interface. This is a good option if you aren't comfortable with something like phstl. Global Mapper is installed on all of the machines in the Computer Cluster on the 2<sup>nd</sup> floor of Bryand Global Sciences Center.
</li>
There are many more open source and commercial options for producing the same results, but I can personally attest to the utility of the tools listed here. You might find that software such as [https://www.goldensoftware.com/products/surfer Surfer] or [http://www.meshlab.net/ MeshLab] might best fit your needs.
</ul>
</li>
</ul>
</p>

<h2>References Cited</h2>

<p><sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.
</p>

DualSPHysics Guidelines for Earth Scientists

2019-03-27T04:34:10Z

Nick:

<h2>History</h2>

<p>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.
</p>

<h2>Structure of DualSPHysics</h2>

<p>The DualSPHysics project represents a collection of codes which can be broken up into three sections:
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing Pre-processing]</h3><strong>GenCase</strong> is the program used to set up the geometry and physics of a DualSPHysics model.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/10.-Processing Processing]</h3><strong>DualSPHysics</strong> is the program used to calculate the motions, etc. of particles within the model domain. This program takes in information from GenCase and outputs binary (.bi4) files. You can't read the binary files directly; they are the inputs for the post-processing codes.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing Post-processing]</h3>There are a litany of post-processing codes in the DualSPHysics project. This allows you to take a modular approach to data generation. Some of them, such as <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#111-visualization-of-particle-output-data-partvtk PartVTK]</strong>, you will use in almost every use case imaginable. Others are more specialized. For example, if you want to calculate the forces exerted on a solid object in your domain, you can use <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#114-force-computation-computeforces ComputeForces4]</strong>.</li>
</ol>

Any given model typically employs GenCase, DualSPHysics, PartVTK, and a handful of other post-processing tools depending on the desired outcome.
</p>

<h2>Resources</h2>

<p>First things first, let's establish where you ought to look for answers to your DualSPHysics questions.
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki The DualSPHysics Wiki on GitHub]</h3>
In 2018, the DualSPHysics project was moved to a [https://github.com/DualSPHysics/DualSPHysics/ GitHub repository]. The [https://github.com/DualSPHysics/DualSPHysics/wiki Wiki section] of the repository should be your go-to resource for all aspects of DualSPHysics, with the exception of model design. At the time of writing (March 2019), the [https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing preprocessing] section of the Wiki lacks the detail of the XML_v4.0_GUIDE.</li>
<li><h3>[[DualSPHysics XML v4.0 GUIDE.pdf|XML_v4.0_GUIDE]]</h3>
In addition to being made available on this wiki (click the heading link), this PDF is included in the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package], and it provides many (but not all) details of the functionality of GenCase, the program used to set up the geometry and physics of a DualSPHysics model.
</li>
<li><h3>[https://dual.sphysics.org/index.php/faq/ DualSPHysics FAQ]</h3>
The DualSPHysics website has a very helpful FAQ section which is updated regularly and addresses a broad range of common questions. Reading through these early on in your DualSPHysics experience will save you time and angst.</li>
<li><h3>doc > xml_format</h3>
Within the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package] there is a <strong>doc</strong> directory containing all sorts of useful documentation. For a deep dive into the full functionality of GenCase, refer to the XML documents in the <strong>xml_format</strong> directory.</li>
</ol>
</p>

<h2>General Pointers</h2>

<p>The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models which faithfully represent the systems you want to model, with minimal frustration.
<ul>
<li>It's wise to familiarize yourself with the example models which ship with the DualSPHysics package. The <strong>examples</strong> directory contains a litany of example models which are categorized in terms of the features they highlight. If you want a high-level overview of these examples without exploring the model results first-hand, you may refer to the [https://github.com/DualSPHysics/DualSPHysics/wiki/12.-Testcases Testcases] section of the DualSPHysics wiki.</li>
<li>Once you're familiar with the example models, you're ready to start experimenting with your own model design. Start by considering which physics (e.g., fluid + fixed structure, fluid + fixed structure + floating objects, fluid + sediment, etc.) and which boundary conditions (e.g., closed system, periodic boundary conditions, open boundary conditions, etc.) will be necessary for your model. From there you can copy an example model which is closest to the system you want to model and adapt it to your needs.</li>
<li>In the early stages of model design, it's best to start with a simple design which is fast to generate. Often the fastest route to a working model is by first running only GenCase, visualizing the outputs in ParaView, and then modifying your case design (XML) file until the geometry is as you would like it to be. From there, you can run DualSPHysics and shift your focus to the quality of the physics simulation. It's usually fastest to run the model at coarse resolution (higher inter-particle distance, or <em>dp</em>), increasing resolution only when the simulation is producing reasonable results.</li>
<li>If working with complex geometries or geospatial data derived from LiDAR, Structure from Motion, or similar, it's best to import the geometry as an [https://en.wikipedia.org/wiki/STL_(file_format) STL] file. The process for this depends entirely on the type of data you're working with, but there are some established routes for distinct use cases:
<ul>
<li> [https://www.blender.org/ Blender] is an excellent program for creating simple or complex surfaces and objects. If I want to create a realistic boulder or a synthetic landscape such as an idealized knickpoint, I would reach for Blender.
</li>
<li> [https://github.com/anoved/phstl phstl] is a Python utility which produces an STL from raster files (GeoTIFFs).
</li>
<li> [https://github.com/NWRichmond/xyz2stl xyz2stl] is a standalone MATLAB app (you don't need MATLAB to run it) that I wrote in 2017 which produces an STL from x,y,z coordinates (such as in a CSV file).
</li>
<li> [https://www.bluemarblegeo.com/products/global-mapper.php Global Mapper] is commercial GIS software which can produce an STL from raster files (GeoTIFFs) using a graphical user interface. This is a good option if you aren't comfortable with something like phstl. Global Mapper is installed on all of the machines in the Computer Cluster on the 2<sup>nd</sup> floor of Bryand Global Sciences Center.
</li>
</ul>
</li>
</ul>
</p>

<h2>References Cited</h2>

<p><sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.
</p>

DualSPHysics Guidelines for Earth Scientists

2019-03-27T04:31:03Z

Nick:

<h2>History</h2>

<p>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.
</p>

<h2>Structure of DualSPHysics</h2>

<p>The DualSPHysics project represents a collection of codes which can be broken up into three sections:
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing Pre-processing]</h3><strong>GenCase</strong> is the program used to set up the geometry and physics of a DualSPHysics model.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/10.-Processing Processing]</h3><strong>DualSPHysics</strong> is the program used to calculate the motions, etc. of particles within the model domain. This program takes in information from GenCase and outputs binary (.bi4) files. You can't read the binary files directly; they are the inputs for the post-processing codes.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing Post-processing]</h3>There are a litany of post-processing codes in the DualSPHysics project. This allows you to take a modular approach to data generation. Some of them, such as <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#111-visualization-of-particle-output-data-partvtk PartVTK]</strong>, you will use in almost every use case imaginable. Others are more specialized. For example, if you want to calculate the forces exerted on a solid object in your domain, you can use <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#114-force-computation-computeforces ComputeForces4]</strong>.</li>
</ol>

Any given model typically employs GenCase, DualSPHysics, PartVTK, and a handful of other post-processing tools depending on the desired outcome.
</p>

<h2>Resources</h2>

<p>First things first, let's establish where you ought to look for answers to your DualSPHysics questions.
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki The DualSPHysics Wiki on GitHub]</h3>
In 2018, the DualSPHysics project was moved to a [https://github.com/DualSPHysics/DualSPHysics/ GitHub repository]. The [https://github.com/DualSPHysics/DualSPHysics/wiki Wiki section] of the repository should be your go-to resource for all aspects of DualSPHysics, with the exception of model design. At the time of writing (March 2019), the [https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing preprocessing] section of the Wiki lacks the detail of the XML_v4.0_GUIDE.</li>
<li><h3>[[DualSPHysics XML v4.0 GUIDE.pdf|XML_v4.0_GUIDE]]</h3>
In addition to being made available on this wiki (click the heading link), this PDF is included in the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package], and it provides many (but not all) details of the functionality of GenCase, the program used to set up the geometry and physics of a DualSPHysics model.
</li>
<li><h3>[https://dual.sphysics.org/index.php/faq/ DualSPHysics FAQ]</h3>
The DualSPHysics website has a very helpful FAQ section which is updated regularly and addresses a broad range of common questions. Reading through these early on in your DualSPHysics experience will save you time and angst.</li>
<li><h3>doc > xml_format</h3>
Within the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package] there is a <strong>doc</strong> directory containing all sorts of useful documentation. For a deep dive into the full functionality of GenCase, refer to the XML documents in the <strong>xml_format</strong> directory.</li>
</ol>
</p>

<h2>General Pointers</h2>

<p>The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models which faithfully represent the systems you want to model, with minimal frustration.
<ul>
<li>It's wise to familiarize yourself with the example models which ship with the DualSPHysics package. The <strong>examples</strong> directory contains a litany of example models which are categorized in terms of the features they highlight. If you want a high-level overview of these examples without exploring the model results first-hand, you may refer to the [https://github.com/DualSPHysics/DualSPHysics/wiki/12.-Testcases Testcases] section of the DualSPHysics wiki.</li>
<li>Once you're familiar with the example models, you're ready to start experimenting with your own model design. Start by considering which physics (e.g., fluid + fixed structure, fluid + fixed structure + floating objects, fluid + sediment, etc.) and which boundary conditions (e.g., closed system, periodic boundary conditions, open boundary conditions, etc.) will be necessary for your model. From there you can copy an example model which is closest to the system you want to model and adapt it to your needs.</li>
<li>In the early stages of model design, it's best to start with a simple design which is fast to generate. Often the fastest route to a working model is by first running only GenCase, visualizing the outputs in ParaView, and then modifying your case design (XML) file until the geometry is as you would like it to be. From there, you can run DualSPHysics and shift your focus to the quality of the physics simulation. It's usually fastest to run the model at coarse resolution (higher inter-particle distance, or <em>dp</em>), increasing resolution only when the simulation is producing reasonable results.</li>
<li>If working with complex geometries or geospatial data derived from LiDAR, Structure from Motion, or similar, it's best to import the geometry as an [https://en.wikipedia.org/wiki/STL_(file_format) STL] file. The process for this depends entirely on the type of data you're working with, but there are some established routes for distinct use cases:
<ul>
<li> [https://www.blender.org/ Blender] is an excellent program for creating simple or complex surfaces and objects. If I want to create a realistic boulder or a synthetic landscape such as an idealized knickpoint, I would reach for Blender.
</li>
<li> [https://github.com/anoved/phstl phstl] is a Python utility which produces an STL from raster files (GeoTIFFs).
</li>
<li> [https://github.com/NWRichmond/xyz2stl xyz2stl] is a standalone MATLAB app (you don't need MATLAB to run it) that I wrote in 2017 which produces an STL from x,y,z coordinates (such as in a CSV file).
</li>
</ul>
</li>
</ul>
</p>

<h2>References Cited</h2>

<p><sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.
</p>

DualSPHysics Guidelines for Earth Scientists

2019-03-27T04:17:44Z

Nick:

<h2>History</h2>

<p>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.
</p>

<h2>Structure of DualSPHysics</h2>

<p>The DualSPHysics project represents a collection of codes which can be broken up into three sections:
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing Pre-processing]</h3><strong>GenCase</strong> is the program used to set up the geometry and physics of a DualSPHysics model.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/10.-Processing Processing]</h3><strong>DualSPHysics</strong> is the program used to calculate the motions, etc. of particles within the model domain. This program takes in information from GenCase and outputs binary (.bi4) files. You can't read the binary files directly; they are the inputs for the post-processing codes.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing Post-processing]</h3>There are a litany of post-processing codes in the DualSPHysics project. This allows you to take a modular approach to data generation. Some of them, such as <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#111-visualization-of-particle-output-data-partvtk PartVTK]</strong>, you will use in almost every use case imaginable. Others are more specialized. For example, if you want to calculate the forces exerted on a solid object in your domain, you can use <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#114-force-computation-computeforces ComputeForces4]</strong>.</li>
</ol>

Any given model typically employs GenCase, DualSPHysics, PartVTK, and a handful of other post-processing tools depending on the desired outcome.
</p>

<h2>Resources</h2>

<p>First things first, let's establish where you ought to look for answers to your DualSPHysics questions.
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki The DualSPHysics Wiki on GitHub]</h3>
In 2018, the DualSPHysics project was moved to a [https://github.com/DualSPHysics/DualSPHysics/ GitHub repository]. The [https://github.com/DualSPHysics/DualSPHysics/wiki Wiki section] of the repository should be your go-to resource for all aspects of DualSPHysics, with the exception of model design. At the time of writing (March 2019), the [https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing preprocessing] section of the Wiki lacks the detail of the XML_v4.0_GUIDE.</li>
<li><h3>[[DualSPHysics XML v4.0 GUIDE.pdf|XML_v4.0_GUIDE]]</h3>
In addition to being made available on this wiki (click the heading link), this PDF is included in the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package], and it provides many (but not all) details of the functionality of GenCase, the program used to set up the geometry and physics of a DualSPHysics model.
</li>
<li><h3>[https://dual.sphysics.org/index.php/faq/ DualSPHysics FAQ]</h3>
The DualSPHysics website has a very helpful FAQ section which is updated regularly and addresses a broad range of common questions. Reading through these early on in your DualSPHysics experience will save you time and angst.</li>
<li><h3>doc > xml_format</h3>
Within the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package] there is a <strong>doc</strong> directory containing all sorts of useful documentation. For a deep dive into the full functionality of GenCase, refer to the XML documents in the <strong>xml_format</strong> directory.</li>
</ol>
</p>

<h2>General Pointers</h2>

<p>The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models which faithfully represent the systems you want to model, with minimal frustration.
<ul>
<li>It's wise to familiarize yourself with the example models which ship with the DualSPHysics package. The <strong>examples</strong> directory contains a litany of example models which are categorized in terms of the features they highlight. If you want a high-level overview of these examples without exploring the model results first-hand, you may refer to the [https://github.com/DualSPHysics/DualSPHysics/wiki/12.-Testcases Testcases] section of the DualSPHysics wiki.</li>
<li>Once you're familiar with the example models, you're ready to start experimenting with your own model design. Start by considering which physics (e.g., fluid + fixed structure, fluid + fixed structure + floating objects, fluid + sediment, etc.) and which boundary conditions (e.g., closed system, periodic boundary conditions, open boundary conditions, etc.) will be necessary for your model. From there you can copy an example model which is closest to the system you want to model and adapt it to your needs.</li>
<li>In the early stages of model design, it's best to start with a simple design which is fast to generate. Often the fastest route to a working model is by first running only GenCase, visualizing the outputs in ParaView, and then modifying your case design (XML) file until the geometry is as you would like it to be. From there, you can run DualSPHysics and shift your focus to the quality of the physics simulation. It's usually fastest to run the model at coarse resolution (higher inter-particle distance, or <em>dp</em>), increasing resolution only when the simulation is producing reasonable results.</li>
</ul>
</p>

<h2>References Cited</h2>

<p><sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.
</p>

DualSPHysics Guidelines for Earth Scientists

2019-03-27T04:16:54Z

Nick:

<h2>History</h2>

<p>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.
</p>

<h2>Structure of DualSPHysics</h2>

<p>The DualSPHysics project represents a collection of codes which can be broken up into three sections:
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing Pre-processing]</h3><strong>GenCase</strong> is the program used to set up the geometry and physics of a DualSPHysics model.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/10.-Processing Processing]</h3><strong>DualSPHysics</strong> is the program used to calculate the motions, etc. of particles within the model domain. This program takes in information from GenCase and outputs binary (.bi4) files. You can't read the binary files directly; they are the inputs for the post-processing codes.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing Post-processing]</h3>There are a litany of post-processing codes in the DualSPHysics project. This allows you to take a modular approach to data generation. Some of them, such as <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#111-visualization-of-particle-output-data-partvtk PartVTK]</strong>, you will use in almost every use case imaginable. Others are more specialized. For example, if you want to calculate the forces exerted on a solid object in your domain, you can use <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#114-force-computation-computeforces ComputeForces4]</strong>.</li>
</ol>

Any given model typically employs GenCase, DualSPHysics, PartVTK, and a handful of other post-processing tools depending on the desired outcome.
</p>

<h2>Resources</h2>

<p>First things first, let's establish where you ought to look for answers to your DualSPHysics questions.
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki The DualSPHysics Wiki on GitHub]</h3>
In 2018, the DualSPHysics project was moved to a [https://github.com/DualSPHysics/DualSPHysics/ GitHub repository]. The [https://github.com/DualSPHysics/DualSPHysics/wiki Wiki section] of the repository should be your go-to resource for all aspects of DualSPHysics, with the exception of model design. At the time of writing (March 2019), the [https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing preprocessing] section of the Wiki lacks the detail of the XML_v4.0_GUIDE.</li>
<li><h3>[[DualSPHysics XML v4.0 GUIDE.pdf|XML_v4.0_GUIDE]]</h3>
In addition to being made available on this wiki (click the heading link), this PDF is included in the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package], and it provides many (but not all) details of the functionality of GenCase, the program used to set up the geometry and physics of a DualSPHysics model.
</li>
<li><h3>[https://dual.sphysics.org/index.php/faq/ DualSPHysics FAQ]</h3>
The DualSPHysics website has a very helpful FAQ section which is updated regularly and addresses a broad range of common questions. Reading through these early on in your DualSPHysics experience will save you time and angst.</li>
<li><h3>doc > xml_format</h3>
Within the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package] there is a <strong>doc</strong> directory containing all sorts of useful documentation. For a deep dive into the full functionality of GenCase, refer to the XML documents in the <strong>xml_format</strong> directory.</li>
</ol>
</p>

<h2>General Pointers</h2>

<p>The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models which faithfully represent the systems you want to model, with minimal frustration.
<ul>
<li>It's wise to familiarize yourself with the example models which ship with the DualSPHysics package. The <strong>examples</strong> directory contains a litany of example models which are categorized in terms of the features they highlight. If you want a high-level overview of these examples without exploring the model results first-hand, you may refer to the [https://github.com/DualSPHysics/DualSPHysics/wiki/12.-Testcases Testcases] section of the DualSPHysics wiki.</li>
<li>Once you're familiar with the example models, you're ready to start experimenting with your own model design. Start by considering which physics (e.g., fluid + fixed structure, fluid + fixed structure + floating objects, fluid + sediment, etc.) and which boundary conditions (e.g., closed system, periodic boundary conditions, open boundary conditions, etc.) will be necessary for your model. From there you can copy an example model which is closest to the system you want to model and adapt it to your needs.</li>
<li>In the early stages of model design, it's best to start with a simple design which is fast to generate. Often the fastest route to a working model is by first running only GenCase, visualizing the outputs in ParaView, and then modifying your case design (XML) file until the geometry is as you would like it to be. From there, you can run DualSPHysics and shift your focus to the quality of the physics simulation. It's usually fastest to run the model at coarse resolution (higher inter-particle distance, or <em>dp</em>), increasing resolution only when the outputs are producing reasonable results.</li>
</ul>
</p>

<h2>References Cited</h2>

<p><sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.
</p>

DualSPHysics Guidelines for Earth Scientists

2019-03-27T04:11:24Z

Nick:

<h2>History</h2>

<p>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.
</p>

<h2>Structure of DualSPHysics</h2>

<p>The DualSPHysics project represents a collection of codes which can be broken up into three sections:
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing Pre-processing]</h3><strong>GenCase</strong> is the program used to set up the geometry and physics of a DualSPHysics model.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/10.-Processing Processing]</h3><strong>DualSPHysics</strong> is the program used to calculate the motions, etc. of particles within the model domain. This program takes in information from GenCase and outputs binary (.bi4) files. You can't read the binary files directly; they are the inputs for the post-processing codes.</li>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing Post-processing]</h3>There are a litany of post-processing codes in the DualSPHysics project. This allows you to take a modular approach to data generation. Some of them, such as <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#111-visualization-of-particle-output-data-partvtk PartVTK]</strong>, you will use in almost every use case imaginable. Others are more specialized. For example, if you want to calculate the forces exerted on a solid object in your domain, you can use <strong>[https://github.com/DualSPHysics/DualSPHysics/wiki/11.-Post%E2%80%90processing#114-force-computation-computeforces ComputeForces4]</strong>.</li>
</ol>

Any given model typically employs GenCase, DualSPHysics, PartVTK, and a handful of other post-processing tools depending on the desired outcome.
</p>

<h2>Resources</h2>

<p>First things first, let's establish where you ought to look for answers to your DualSPHysics questions.
<ol>
<li><h3>[https://github.com/DualSPHysics/DualSPHysics/wiki The DualSPHysics Wiki on GitHub]</h3>
In 2018, the DualSPHysics project was moved to a [https://github.com/DualSPHysics/DualSPHysics/ GitHub repository]. The [https://github.com/DualSPHysics/DualSPHysics/wiki Wiki section] of the repository should be your go-to resource for all aspects of DualSPHysics, with the exception of model design. At the time of writing (March 2019), the [https://github.com/DualSPHysics/DualSPHysics/wiki/9.-Pre%E2%80%90processing preprocessing] section of the Wiki lacks the detail of the XML_v4.0_GUIDE.</li>
<li><h3>[[DualSPHysics XML v4.0 GUIDE.pdf|XML_v4.0_GUIDE]]</h3>
In addition to being made available on this wiki (click the heading link), this PDF is included in the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package], and it provides many (but not all) details of the functionality of GenCase, the program used to set up the geometry and physics of a DualSPHysics model.
</li>
<li><h3>[https://dual.sphysics.org/index.php/faq/ DualSPHysics FAQ]</h3>
The DualSPHysics website has a very helpful FAQ section which is updated regularly and addresses a broad range of common questions. Reading through these early on in your DualSPHysics experience will save you time and angst.</li>
<li><h3>doc > xml_format</h3>
Within the [https://dual.sphysics.org/index.php/downloads/ DualSPHysics package] there is a <strong>doc</strong> directory containing all sorts of useful documentation. For a deep dive into the full functionality of GenCase, refer to the XML documents in the <strong>xml_format</strong> directory.</li>
</ol>
</p>

<h2>General Pointers</h2>

<p>The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models which faithfully represent the systems you want to model, with minimal frustration.
<ul>
<li>It's wise to familiarize yourself with the example models which ship with the DualSPHysics package. The <strong>examples</strong> directory contains a litany of example models which are categorized in terms of the features they highlight. If you want a high-level overview of these examples without exploring the model results first-hand, you may refer to the [https://github.com/DualSPHysics/DualSPHysics/wiki/12.-Testcases Testcases] section of the DualSPHysics wiki.</li>
<li>Once you're familiar with the example models, you're ready to start experimenting with your own model design. Start by considering which physics (e.g., fluid + fixed structure, fluid + fixed structure + floating objects, fluid + sediment, etc.) and which boundary conditions (e.g., closed system, periodic boundary conditions, open boundary conditions, etc.) will be necessary for your model. From there you can copy an example model which is closest to the system you want to model and adapt it to your needs.</li>
<li>In the early stages of model design, it's best to start with a simple design which is fast to generate. Often the fastest route to a working model is by first running only GenCase, visualizing the outputs in ParaView, and then modifying your case design (XML) file until the geometry is as you would like it to be. From there, you can run DualSPHysics and shift your focus to the quality of the physics simulation. It's usually fastest to run the model at coarse resolution (higher inter-particle distance, or <em>dp</em></li>), increasing resolution only when the outputs are producing reasonable results.
</ul>
</p>

<h2>References Cited</h2>

<p><sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.
</p>

DualSPHysics Guidelines for Earth Scientists

2019-03-27T04:01:19Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T03:56:27Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T03:54:59Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T03:50:25Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T03:46:07Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T03:44:53Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T03:43:20Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T03:42:34Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T03:41:13Z

Nick:

DualSPHysics XML v4.0 GUIDE.pdf

2019-03-27T03:39:24Z

Nick:

<pdf>File:DualSPHysics XML v4.0 GUIDE.pdf</pdf>

DualSPHysics XML v4.0 GUIDE.pdf

2019-03-27T03:38:18Z

Nick: Created page with "File:DualSPHysics XML v4.0 GUIDE.pdf"

[[File:DualSPHysics XML v4.0 GUIDE.pdf]]

File:DualSPHysics XML v4.0 GUIDE.pdf

2019-03-27T03:36:54Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T03:35:44Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T03:31:11Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-27T03:29:56Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-26T23:13:32Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-26T22:41:43Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-26T21:51:21Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-26T21:40:46Z

Nick:

MediaWiki:Common.css

2019-03-26T21:36:49Z

Nick:

/* CSS placed here will affect users of the Vector skin */

@import url('https://fonts.googleapis.com/css?family=Nunito+Sans|PT+Serif');

$nunito: 'Nunito Sans', sans-serif;
$ptserif: 'PT Serif', serif;

body {font-family: $ptserif}
/* changes the default font used for MediaWiki to PT Serif (does not include headings or monospaced text) */

div#content h1, div#content h2, div#content h3, div#content h4 {font-family: $nunito}
/* changes the default font used for MediaWiki headings to Nunito */

#p-logo a {
display: block;
height: 170px;
width: 170px;
background-repeat: no-repeat;
background-position: 35% 50% !important;
text-decoration: none;
}

/* Change background colors */

#mw-head-base {
margin-top: -5em;
margin-left: 11em;
height: 5em;
background-image: url(http://wiki.geodynamics.umaine.edu/images/9/90/HimalayaPano.png);
background-position: bottom left;
background-repeat: repeat-x;
}

body {
background-color: #ffffff;
}

#mw-head-base {
background-color: #ffffff;
}

#mw-panel {
background-color: #ffffff;
}

#p-navigation {
background-color: #ffffff;
}

#footer {
background-color: #ffffff;
}

#headertabs.round .ui-state-default, .ui-widget-content .ui-state-default, .ui-widget-header .ui-state-default {
border: 1px solid #DDD;
font-weight: normal;
color: #2779AA;
}

/* Reset italic styling set by user agent */
cite, dfn {
font-style: inherit;
}

/* Straight quote marks for <q> */
q {
quotes: '"' '"' "'" "'";
}

/* Avoid collision of blockquote with floating elements by swapping margin and padding */
blockquote {
overflow: hidden;
margin: 1em 0;
padding: 0 40px;
}

/* Prevent the 'double bold' bug in Firefox when using DirectWrite */
strong.selflink {
font-weight: 700;
}

/* Consistent size for <small>, <sub> and <sup> */
small {
font-size: 85%;
}
.mw-body-content sub,
.mw-body-content sup,
span.reference /* for Parsoid */ {
font-size: 80%;
}

/* Same spacing for indented and unidented paragraphs on talk pages */
.ns-talk .mw-body-content dd {
margin-top: 0.4em;
margin-bottom: 0.4em;
}

/* Main page fixes */
#interwiki-completelist {
font-weight: bold;
}

/* Reduce page jumps by hiding collapsed/dismissed content */
.client-js .mw-special-Watchlist #watchlist-message,
.client-js .NavFrame.collapsed .NavContent,
.client-js .collapsible.collapsed > tbody > tr:not(:first-child) {
display: none;
}

/* Tone down 'Changed since last visit' colors */
span.updatedmarker {
background-color: transparent;
color: #006400;
}

/* Edit window toolbar */
#toolbar {
margin-bottom: 6px;
}

/* Hide charinsert base for those not using the gadget */
#editpage-specialchars {
display: none;
}

/* Highlight linked elements (such as clicked references) in blue */
body.action-info .mw-body-content :target,
.citation:target {
background-color: #DEF; /* Fallback */
background-color: rgba(0, 127, 255, 0.133);
}

/* Styling for citations. Breaks long urls, etc., rather than overflowing box */
.citation {
word-wrap: break-word;
}

/* For linked citation numbers and document IDs, where the number need not be shown
on a screen or a handheld, but should be included in the printed version */
@media screen, handheld {
.citation .printonly {
display: none;
}
}

/* Make the list of references smaller */
ol.references,
div.reflist,
div.refbegin {
font-size: 90%; /* Default font-size */
margin-bottom: 0.5em;
}
div.refbegin-100 {
font-size: 100%; /* Option for normal fontsize in {{refbegin}} */
}
div.reflist ol.references {
font-size: 100%; /* Reset font-size when nested in div.reflist */
margin-bottom: 0; /* Avoid double margin when nested in div.reflist */
list-style-type: inherit; /* Enable custom list style types */
}

/* Ensure refs in table headers and the like aren't bold or italic */
sup.reference {
font-weight: normal;
font-style: normal;
}

/* Allow hidden ref errors to be shown by user CSS */
span.brokenref {
display: none;
}

/* Hanging indentation for Template:Refbegin */
.refbegin-hanging-indents > ul {
list-style-type: none;
margin-left: 0;
}
.refbegin-hanging-indents > ul > li,
.refbegin-hanging-indents > dl > dd {
margin-left: 0;
padding-left: 3.2em;
text-indent: -3.2em;
list-style: none;
}

/* Reset top margin for lists embedded in columns */
div.columns {
margin-top: 0.3em;
}
div.columns dl,
div.columns ol,
div.columns ul {
margin-top: 0;
}

/* Avoid elements from breaking between columns */
.nocolbreak,
div.columns li,
div.columns dd dd {
-webkit-column-break-inside: avoid;
page-break-inside: avoid;
break-inside: avoid-column;
}

/* Style for [[Template:Flowlist]] that Lets lists flow around floating objecs */
.flowlist ul {
overflow-x: hidden;
margin-left: 0;
padding-left: 1.6em;
}
.flowlist ol {
overflow-x: hidden;
margin-left: 0;
padding-left: 3.2em;
}
.flowlist dl {
overflow-x: hidden;
}

/* Style for horizontal lists (separator following item).
@source mediawiki.org/wiki/Snippets/Horizontal_lists
@revision 8 (2016-05-21)
@author [[User:Edokter]]
*/
.hlist dl,
.hlist ol,
.hlist ul {
margin: 0;
padding: 0;
}
/* Display list items inline */
.hlist dd,
.hlist dt,
.hlist li {
margin: 0;
display: inline;
}
/* Display nested lists inline */
.hlist.inline,
.hlist.inline dl,
.hlist.inline ol,
.hlist.inline ul,
.hlist dl dl, .hlist dl ol, .hlist dl ul,
.hlist ol dl, .hlist ol ol, .hlist ol ul,
.hlist ul dl, .hlist ul ol, .hlist ul ul {
display: inline;
}
/* Hide empty list items */
.hlist .mw-empty-li {
display: none;
}
/* Generate interpuncts */
.hlist dt:after {
content: ": ";
}
.hlist dd:after,
.hlist li:after {
content: " · ";
font-weight: bold;
}
.hlist dd:last-child:after,
.hlist dt:last-child:after,
.hlist li:last-child:after {
content: none;
}
/* Add parentheses around nested lists */
.hlist dd dd:first-child:before, .hlist dd dt:first-child:before, .hlist dd li:first-child:before,
.hlist dt dd:first-child:before, .hlist dt dt:first-child:before, .hlist dt li:first-child:before,
.hlist li dd:first-child:before, .hlist li dt:first-child:before, .hlist li li:first-child:before {
content: " (";
font-weight: normal;
}
.hlist dd dd:last-child:after, .hlist dd dt:last-child:after, .hlist dd li:last-child:after,
.hlist dt dd:last-child:after, .hlist dt dt:last-child:after, .hlist dt li:last-child:after,
.hlist li dd:last-child:after, .hlist li dt:last-child:after, .hlist li li:last-child:after {
content: ")";
font-weight: normal;
}
/* Put ordinals in front of ordered list items */
.hlist ol {
counter-reset: listitem;
}
.hlist ol > li {
counter-increment: listitem;
}
.hlist ol > li:before {
content: " " counter(listitem) "\a0";
}
.hlist dd ol > li:first-child:before,
.hlist dt ol > li:first-child:before,
.hlist li ol > li:first-child:before {
content: " (" counter(listitem) "\a0";
}

/* Unbulleted lists */
.plainlist ol,
.plainlist ul {
line-height: inherit;
list-style: none none;
margin: 0;
}
.plainlist ol li,
.plainlist ul li {
margin-bottom: 0;
}

/* Default style for navigation boxes */
.navbox { /* Navbox container style */
box-sizing: border-box;
border: 1px solid #a2a9b1;
width: 100%;
clear: both;
font-size: 88%;
text-align: center;
padding: 1px;
margin: 1em auto 0; /* Prevent preceding content from clinging to navboxes */
}
.navbox .navbox {
margin-top: 0; /* No top margin for nested navboxes */
}
.navbox + .navbox {
margin-top: -1px; /* Single pixel border between adjacent navboxes */
}
.navbox-inner,
.navbox-subgroup {
width: 100%;
}
.navbox-group,
.navbox-title,
.navbox-abovebelow {
padding: 0.25em 1em; /* Title, group and above/below styles */
line-height: 1.5em;
text-align: center;
}
th.navbox-group { /* Group style */
white-space: nowrap;
/* @noflip */
text-align: right;
}
.navbox,
.navbox-subgroup {
background: #fdfdfd; /* Background color */
}
.navbox-list {
line-height: 1.5em;
border-color: #fdfdfd; /* Must match background color */
}
/* cell spacing for navbox cells */
tr + tr > .navbox-abovebelow,
tr + tr > .navbox-group,
tr + tr > .navbox-image,
tr + tr > .navbox-list { /* Borders above 2nd, 3rd, etc. rows */
border-top: 2px solid #fdfdfd; /* Must match background color */
}
.navbox th,
.navbox-title {
background: #ccccff; /* Level 1 color */
}
.navbox-abovebelow,
th.navbox-group,
.navbox-subgroup .navbox-title {
background: #ddddff; /* Level 2 color */
}
.navbox-subgroup .navbox-group,
.navbox-subgroup .navbox-abovebelow {
background: #e6e6ff; /* Level 3 color */
}
.navbox-even {
background: #f7f7f7; /* Even row striping */
}
.navbox-odd {
background: transparent; /* Odd row striping */
}
.navbox .hlist td dl,
.navbox .hlist td ol,
.navbox .hlist td ul,
.navbox td.hlist dl,
.navbox td.hlist ol,
.navbox td.hlist ul {
padding: 0.125em 0; /* Adjust hlist padding in navboxes */
}

/* Default styling for Navbar template */
.navbar {
display: inline;
font-size: 88%;
font-weight: normal;
}
.navbar ul {
display: inline;
white-space: nowrap;
}
.mw-body-content .navbar ul {
line-height: inherit;
}
.navbar li {
word-spacing: -0.125em;
}
.navbar.mini li abbr[title] {
font-variant: small-caps;
border-bottom: none;
text-decoration: none;
cursor: inherit;
}
/* Navbar styling when nested in infobox and navbox */
.infobox .navbar {
font-size: 100%;
}
.navbox .navbar {
display: block;
font-size: 100%;
}
.navbox-title .navbar {
/* @noflip */
float: left;
/* @noflip */
text-align: left;
/* @noflip */
margin-right: 0.5em;
}

/* 'show'/'hide' buttons created dynamically by the CollapsibleTables javascript
in [[MediaWiki:Common.js]] are styled here so they can be customised. */
.collapseButton {
/* @noflip */
float: right;
font-weight: normal;
/* @noflip */
margin-left: 0.5em;
/* @noflip */
text-align: right;
width: auto;
}

/* Styling for JQuery makeCollapsible, matching that of collapseButton */
.mw-parser-output .mw-collapsible-toggle {
font-weight: normal;
/* @noflip */
text-align: right;
padding-right: 0.2em;
padding-left: 0.2em;
}
.mw-collapsible-leftside-toggle .mw-collapsible-toggle {
/* @noflip */
float: left;
/* @noflip */
text-align: left;
}

/* Infobox template style */
.infobox {
border: 1px solid #a2a9b1;
border-spacing: 3px;
background-color: #f8f9fa;
color: black;
/* @noflip */
margin: 0.5em 0 0.5em 1em;
padding: 0.2em;
/* @noflip */
float: right;
/* @noflip */
clear: right;
font-size: 88%;
line-height: 1.5em;
}
.infobox caption {
font-size: 125%;
font-weight: bold;
padding: 0.2em;
text-align: center;
}
.infobox td,
.infobox th {
vertical-align: top;
/* @noflip */
text-align: left;
}
.infobox.bordered {
border-collapse: collapse;
}
.infobox.bordered td,
.infobox.bordered th {
border: 1px solid #a2a9b1;
}
.infobox.bordered .borderless td,
.infobox.bordered .borderless th {
border: 0;
}

.infobox.sisterproject {
width: 20em;
font-size: 90%;
}

.infobox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
}
.infobox.standard-talk.bordered td,
.infobox.standard-talk.bordered th {
border: 1px solid #c0c090;
}

/* styles for bordered infobox with merged rows */
.infobox.bordered .mergedtoprow td,
.infobox.bordered .mergedtoprow th {
border: 0;
border-top: 1px solid #a2a9b1;
/* @noflip */
border-right: 1px solid #a2a9b1;
}

.infobox.bordered .mergedrow td,
.infobox.bordered .mergedrow th {
border: 0;
/* @noflip */
border-right: 1px solid #a2a9b1;
}

/* Styles for geography infoboxes, eg countries,
country subdivisions, cities, etc. */
.infobox.geography {
border-collapse: collapse;
line-height: 1.2em;
font-size: 90%;
}

.infobox.geography td,
.infobox.geography th {
border-top: 1px solid #a2a9b1;
padding: 0.4em 0.6em 0.4em 0.6em;
}
.infobox.geography .mergedtoprow td,
.infobox.geography .mergedtoprow th {
border-top: 1px solid #a2a9b1;
padding: 0.4em 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedrow td,
.infobox.geography .mergedrow th {
border: 0;
padding: 0 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedbottomrow td,
.infobox.geography .mergedbottomrow th {
border-top: 0;
border-bottom: 1px solid #a2a9b1;
padding: 0 0.6em 0.4em 0.6em;
}

.infobox.geography .maptable td,
.infobox.geography .maptable th {
border: 0;
padding: 0;
}

/* Normal font styling for table row headers with scope="row" tag */
.wikitable.plainrowheaders th[scope=row] {
font-weight: normal;
/* @noflip */
text-align: left;
}

/* Lists in data cells are always left-aligned */
.wikitable td ul,
.wikitable td ol,
.wikitable td dl {
/* @noflip */
text-align: left;
}
/* ...unless they also use the hlist class */
.toc.hlist ul,
#toc.hlist ul,
.wikitable.hlist td ul,
.wikitable.hlist td ol,
.wikitable.hlist td dl {
text-align: inherit;
}

/* Icons for medialist templates [[Template:Listen]],
[[Template:Multi-listen_start]], [[Template:Video]],
[[Template:Multi-video_start]] */
div.listenlist {
background: url("//upload.wikimedia.org/wikipedia/commons/4/47/Sound-icon.svg") no-repeat scroll 0 0 transparent;
background-size: 30px;
padding-left: 40px;
}

/* Fix for hieroglyphs specificality issue in infoboxes ([[Phabricator:43869]]) */
table.mw-hiero-table td {
vertical-align: middle;
}

/* Style rules for media list templates */
div.medialist {
min-height: 50px;
margin: 1em;
/* @noflip */
background-position: top left;
background-repeat: no-repeat;
}
div.medialist ul {
list-style-type: none;
list-style-image: none;
margin: 0;
}
div.medialist ul li {
padding-bottom: 0.5em;
}
div.medialist ul li li {
font-size: 91%;
padding-bottom: 0;
}

/* Change the external link icon to an Adobe icon for all PDF files
in browsers that support these CSS selectors, like Mozilla and Opera */
div#content a[href$=".pdf"].external,
div#content a[href*=".pdf?"].external,
div#content a[href*=".pdf#"].external,
div#content a[href$=".PDF"].external,
div#content a[href*=".PDF?"].external,
div#content a[href*=".PDF#"].external,
div#mw_content a[href$=".pdf"].external,
div#mw_content a[href*=".pdf?"].external,
div#mw_content a[href*=".pdf#"].external,
div#mw_content a[href$=".PDF"].external,
div#mw_content a[href*=".PDF?"].external,
div#mw_content a[href*=".PDF#"].external {
background: url("//upload.wikimedia.org/wikipedia/commons/2/23/Icons-mini-file_acrobat.gif") no-repeat right;
/* @noflip */
padding-right: 18px;
}

/* Content in columns with CSS instead of tables ([[Template:Columns]]) */
div.columns-2 div.column {
/* @noflip */
float: left;
width: 50%;
min-width: 300px;
}
div.columns-3 div.column {
/* @noflip */
float: left;
width: 33.3%;
min-width: 200px;
}
div.columns-4 div.column {
/* @noflip */
float: left;
width: 25%;
min-width: 150px;
}
div.columns-5 div.column {
/* @noflip */
float: left;
width: 20%;
min-width: 120px;
}

/* Messagebox templates */
.messagebox {
border: 1px solid #a2a9b1;
background-color: #f8f9fa;
width: 80%;
margin: 0 auto 1em auto;
padding: .2em;
}
.messagebox.merge {
border: 1px solid #c0b8cc;
background-color: #f0e5ff;
text-align: center;
}
.messagebox.cleanup {
border: 1px solid #9f9fff;
background-color: #efefff;
text-align: center;
}
.messagebox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
margin: 4px auto;
}
/* For old WikiProject banners inside banner shells. */
.mbox-inside .standard-talk,
.messagebox.nested-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
width: 100%;
margin: 2px 0;
padding: 2px;
}
.messagebox.small {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
}
.messagebox.small-talk {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
background: #F8EABA;
}

/* Cell sizes for ambox/tmbox/imbox/cmbox/ombox/fmbox/dmbox message boxes */
th.mbox-text, td.mbox-text { /* The message body cell(s) */
border: none;
/* @noflip */
padding: 0.25em 0.9em; /* 0.9em left/right */
width: 100%; /* Make all mboxes the same width regardless of text length */
}
td.mbox-image { /* The left image cell */
border: none;
/* @noflip */
padding: 2px 0 2px 0.9em; /* 0.9em left, 0px right */
text-align: center;
}
td.mbox-imageright { /* The right image cell */
border: none;
/* @noflip */
padding: 2px 0.9em 2px 0; /* 0px left, 0.9em right */
text-align: center;
}
td.mbox-empty-cell { /* An empty narrow cell */
border: none;
padding: 0;
width: 1px;
}

/* Article message box styles */
table.ambox {
margin: 0 10%; /* 10% = Will not overlap with other elements */
border: 1px solid #a2a9b1;
/* @noflip */
border-left: 10px solid #36c; /* Default "notice" blue */
background: #fbfbfb;
}
table.ambox + table.ambox { /* Single border between stacked boxes. */
margin-top: -1px;
}
.ambox th.mbox-text,
.ambox td.mbox-text { /* The message body cell(s) */
padding: 0.25em 0.5em; /* 0.5em left/right */
}
.ambox td.mbox-image { /* The left image cell */
/* @noflip */
padding: 2px 0 2px 0.5em; /* 0.5em left, 0px right */
}
.ambox td.mbox-imageright { /* The right image cell */
/* @noflip */
padding: 2px 0.5em 2px 0; /* 0px left, 0.5em right */
}

table.ambox-notice {
/* @noflip */
border-left: 10px solid #36c; /* Blue */
}
table.ambox-speedy {
/* @noflip */
border-left: 10px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.ambox-delete {
/* @noflip */
border-left: 10px solid #b32424; /* Red */
}
table.ambox-content {
/* @noflip */
border-left: 10px solid #f28500; /* Orange */
}
table.ambox-style {
/* @noflip */
border-left: 10px solid #fc3; /* Yellow */
}
table.ambox-move {
/* @noflip */
border-left: 10px solid #9932cc; /* Purple */
}
table.ambox-protection {
/* @noflip */
border-left: 10px solid #a2a9b1; /* Gray-gold */
}

/* Image message box styles */
table.imbox {
margin: 4px 10%;
border-collapse: collapse;
border: 3px solid #36c; /* Default "notice" blue */
background: #fbfbfb;
}
.imbox .mbox-text .imbox { /* For imboxes inside imbox-text cells. */
margin: 0 -0.5em; /* 0.9 - 0.5 = 0.4em left/right. */
display: block; /* Fix for webkit to force 100% width. */
}
.mbox-inside .imbox { /* For imboxes inside other templates. */
margin: 4px;
}

table.imbox-notice {
border: 3px solid #36c; /* Blue */
}
table.imbox-speedy {
border: 3px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.imbox-delete {
border: 3px solid #b32424; /* Red */
}
table.imbox-content {
border: 3px solid #f28500; /* Orange */
}
table.imbox-style {
border: 3px solid #fc3; /* Yellow */
}
table.imbox-move {
border: 3px solid #9932cc; /* Purple */
}
table.imbox-protection {
border: 3px solid #a2a9b1; /* Gray-gold */
}
table.imbox-license {
border: 3px solid #88a; /* Dark gray */
background: #f7f8ff; /* Light gray */
}
table.imbox-featured {
border: 3px solid #cba135; /* Brown-gold */
}

/* Category message box styles */
table.cmbox {
margin: 3px 10%;
border-collapse: collapse;
border: 1px solid #a2a9b1;
background: #DFE8FF; /* Default "notice" blue */
}

table.cmbox-notice {
background: #D8E8FF; /* Blue */
}
table.cmbox-speedy {
margin-top: 4px;
margin-bottom: 4px;
border: 4px solid #b32424; /* Red */
background: #FFDBDB; /* Pink */
}
table.cmbox-delete {
background: #FFDBDB; /* Red */
}
table.cmbox-content {
background: #FFE7CE; /* Orange */
}
table.cmbox-style {
background: #FFF9DB; /* Yellow */
}
table.cmbox-move {
background: #E4D8FF; /* Purple */
}
table.cmbox-protection {
background: #EFEFE1; /* Gray-gold */
}

/* Other pages message box styles */
table.ombox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #a2a9b1; /* Default "notice" gray */
background: #f8f9fa;
}

table.ombox-notice {
border: 1px solid #a2a9b1; /* Gray */
}
table.ombox-speedy {
border: 2px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.ombox-delete {
border: 2px solid #b32424; /* Red */
}
table.ombox-content {
border: 1px solid #f28500; /* Orange */
}
table.ombox-style {
border: 1px solid #fc3; /* Yellow */
}
table.ombox-move {
border: 1px solid #9932cc; /* Purple */
}
table.ombox-protection {
border: 2px solid #a2a9b1; /* Gray-gold */
}

/* Talk page message box styles */
table.tmbox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #c0c090; /* Default "notice" gray-brown */
background: #f8eaba;
}
.mediawiki .mbox-inside .tmbox { /* For tmboxes inside other templates. The "mediawiki" class ensures that */
margin: 2px 0; /* this declaration overrides other styles (including mbox-small above) */
width: 100%; /* For Safari and Opera */
}
.mbox-inside .tmbox.mbox-small { /* "small" tmboxes should not be small when */
line-height: 1.5em; /* also "nested", so reset styles that are */
font-size: 100%; /* set in "mbox-small" above. */
}

table.tmbox-speedy {
border: 2px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.tmbox-delete {
border: 2px solid #b32424; /* Red */
}
table.tmbox-content {
border: 2px solid #f28500; /* Orange */
}
table.tmbox-style {
border: 2px solid #fc3; /* Yellow */
}
table.tmbox-move {
border: 2px solid #9932cc; /* Purple */
}
table.tmbox-protection,
table.tmbox-notice {
border: 1px solid #c0c090; /* Gray-brown */
}

/* Disambig and set index box styles */
table.dmbox {
clear: both;
margin: 0.9em 1em;
border-top: 1px solid #ccc;
border-bottom: 1px solid #ccc;
background: transparent;
}

/* Footer and header message box styles */
table.fmbox {
clear: both;
margin: 0.2em 0;
width: 100%;
border: 1px solid #a2a9b1;
background: #f8f9fa; /* Default "system" gray */
}
table.fmbox-system {
background: #f8f9fa;
}
table.fmbox-warning {
border: 1px solid #bb7070; /* Dark pink */
background: #ffdbdb; /* Pink */
}
table.fmbox-editnotice {
background: transparent;
}
/* Div based "warning" style fmbox messages. */
div.mw-warning-with-logexcerpt,
div.mw-lag-warn-high,
div.mw-cascadeprotectedwarning,
div#mw-protect-cascadeon,
div.titleblacklist-warning,
div.locked-warning {
clear: both;
margin: 0.2em 0;
border: 1px solid #bb7070;
background: #ffdbdb;
padding: 0.25em 0.9em;
}
/* Div based "system" style fmbox messages.
Used in [[MediaWiki:Readonly lag]]. */
div.mw-lag-warn-normal,
div.fmbox-system {
clear: both;
margin: 0.2em 0;
border: 1px solid #a2a9b1;
background: #f8f9fa;
padding: 0.25em 0.9em;
}

/* These mbox-small classes must be placed after all other
ambox/tmbox/ombox etc classes. "html body.mediawiki" is so
they override "table.ambox + table.ambox" above. */
html body.mediawiki .mbox-small { /* For the "small=yes" option. */
/* @noflip */
clear: right;
/* @noflip */
float: right;
/* @noflip */
margin: 4px 0 4px 1em;
box-sizing: border-box;
width: 238px;
font-size: 88%;
line-height: 1.25em;
}
html body.mediawiki .mbox-small-left { /* For the "small=left" option. */
/* @noflip */
margin: 4px 1em 4px 0;
box-sizing: border-box;
overflow: hidden;
width: 238px;
border-collapse: collapse;
font-size: 88%;
line-height: 1.25em;
}

/* Style for compact ambox */
/* Hide the images */
.compact-ambox table .mbox-image,
.compact-ambox table .mbox-imageright,
.compact-ambox table .mbox-empty-cell {
display: none;
}
/* Remove borders, backgrounds, padding, etc. */
.compact-ambox table.ambox {
border: none;
border-collapse: collapse;
background: transparent;
margin: 0 0 0 1.6em !important;
padding: 0 !important;
width: auto;
display: block;
}
body.mediawiki .compact-ambox table.mbox-small-left {
font-size: 100%;
width: auto;
margin: 0;
}
/* Style the text cell as a list item and remove its padding */
.compact-ambox table .mbox-text {
padding: 0 !important;
margin: 0 !important;
}
.compact-ambox table .mbox-text-span {
display: list-item;
line-height: 1.5em;
list-style-type: square;
list-style-image: url(/w/skins/MonoBook/bullet.gif);
}
.skin-vector .compact-ambox table .mbox-text-span {
list-style-type: disc;
list-style-image: url(/w/skins/Vector/images/bullet-icon.svg);
list-style-image: url(/w/skins/Vector/images/bullet-icon.png)\9;
}
/* Allow for hiding text in compact form */
.compact-ambox .hide-when-compact {
display: none;
}

/* Remove default styles for [[MediaWiki:Noarticletext]]. */
div.noarticletext {
border: none;
background: transparent;
padding: 0;
}

/* Hide (formatting) elements from screen, but not from screenreaders */
.visualhide {
position: absolute;
left: -10000px;
top: auto;
width: 1px;
height: 1px;
overflow: hidden;
}

/* suppress missing interwiki image links where #ifexist cannot
be used due to high number of requests see .hidden-redlink on
[[m:MediaWiki:Common.css]] */
.check-icon a.new {
display: none;
speak: none;
}

/* Removes underlines from certain links */
.nounderlines a,
.IPA a:link, .IPA a:visited {
text-decoration: none !important;
}

/* Standard Navigationsleisten, aka box hiding thingy
from .de. Documentation at [[Wikipedia:NavFrame]]. */
div.NavFrame {
margin: 0;
padding: 4px;
border: 1px solid #a2a9b1;
text-align: center;
border-collapse: collapse;
font-size: 95%;
}
div.NavFrame + div.NavFrame {
border-top-style: none;
border-top-style: hidden;
}
div.NavPic {
background-color: #fff;
margin: 0;
padding: 2px;
/* @noflip */
float: left;
}
div.NavFrame div.NavHead {
line-height: 1.6em;
font-weight: bold;
background-color: #ccf;
position: relative;
}
div.NavFrame p,
div.NavFrame div.NavContent,
div.NavFrame div.NavContent p {
font-size: 100%;
}
div.NavEnd {
margin: 0;
padding: 0;
line-height: 1px;
clear: both;
}
a.NavToggle {
position: absolute;
top: 0;
/* @noflip */
right: 3px;
font-weight: normal;
font-size: 90%;
}

/* Hatnotes and disambiguation notices */
.hatnote {
font-style: italic;
}
.hatnote i {
font-style: normal;
}
div.hatnote {
/* @noflip */
padding-left: 1.6em;
margin-bottom: 0.5em;
}
div.hatnote + div.hatnote {
margin-top: -0.5em;
}

/* Allow transcluded pages to display in lists rather than a table. */
.listify td { display: list-item; }
.listify tr { display: block; }
.listify table { display: block; }

/* Geographical coordinates defaults. See [[Template:Coord/link]]
for how these are used. The classes "geo", "longitude", and
"latitude" are used by the [[Geo microformat]]. */
.geo-default, .geo-dms, .geo-dec { display: inline; }
.geo-nondefault, .geo-multi-punct { display: none; }
.longitude, .latitude { white-space: nowrap; }

/* Temporary(!) fix for horizontal TOC in Blink (Chrone/Opera) */
.hlist .tocnumber,
.hlist .toctext {
display: inline;
}
/* When <div class="nonumtoc"> is used on the table of contents,
the ToC will display without numbers */
.nonumtoc .tocnumber {
display: none;
}
.nonumtoc #toc ul,
.nonumtoc .toc ul {
line-height: 1.5em;
list-style: none none;
margin: .3em 0 0;
padding: 0;
}
.hlist.nonumtoc #toc ul ul,
.hlist.nonumtoc .toc ul ul {
/* @noflip */
margin: 0;
}

/* Allow limiting of which header levels are shown in a TOC;
<div class="toclimit-3">, for instance, will limit to
showing ==headings== and ===headings=== but no further
(as long as there are no =headings= on the page, which
there shouldn't be according to the MoS). */
.toclimit-2 .toclevel-1 ul,
.toclimit-3 .toclevel-2 ul,
.toclimit-4 .toclevel-3 ul,
.toclimit-5 .toclevel-4 ul,
.toclimit-6 .toclevel-5 ul,
.toclimit-7 .toclevel-6 ul {
display: none;
}

/* Styling for Template:Quote */
blockquote.templatequote div.templatequotecite {
line-height: 1.5em;
/* @noflip */
text-align: left;
/* @noflip */
padding-left: 1.6em;
margin-top: 0;
}

/* User block messages */
div.user-block {
padding: 5px;
margin-bottom: 0.5em;
border: 1px solid #A9A9A9;
background-color: #FFEFD5;
}

/* Prevent line breaks in silly places:
1) Where desired
2) Links when we don't want them to
3) Bold "links" to the page itself */
.nowrap,
.nowraplinks a,
.nowraplinks .selflink {
white-space: nowrap;
}
.nowrap pre {
white-space: pre;
}
/* But allow wrapping where desired: */
.wrap,
.wraplinks a {
white-space: normal;
}

/* For template documentation */
.template-documentation {
clear: both;
margin: 1em 0 0 0;
border: 1px solid #a2a9b1;
background-color: #ecfcf4;
padding: 1em;
}

/* Increase the height of the image upload box */
#wpUploadDescription {
height: 13em;
}

/* Minimum thumb width */
.thumbinner {
min-width: 100px;
}

/* Prevent floating boxes from overlapping any category listings,
file histories, edit previews, and edit [Show changes] views. */
#mw-subcategories, #mw-pages, #mw-category-media,
#filehistory, #wikiPreview, #wikiDiff {
clear: both;
}

/* Selectively hide headers in WikiProject banners */
.wpb .wpb-header { display: none; }
.wpbs-inner .wpb .wpb-header { display: block; } /* for IE */
.wpbs-inner .wpb .wpb-header { display: table-row; } /* for real browsers */
.wpbs-inner .wpb-outside { display: none; } /* hide things that should only display outside shells */

/* Styling for Abuse Filter tags */
.mw-tag-markers {
font-style:italic;
font-size:90%;
}

/* Hide stuff meant for accounts with special permissions. Made visible again in
[[MediaWiki:Group-sysop.css]], [[MediaWiki:Group-patroller.css]],
[[MediaWiki:Group-templateeditor.css]], [[MediaWiki:Group-extendedmover.css]] and [[Mediawiki:Group-autoconfirmed.css]]. */
.sysop-show,
.templateeditor-show,
.extendedmover-show,
.patroller-show,
.autoconfirmed-show,
.user-show {
display: none;
}

/**
* Hide the redlink generated by {{Editnotice}},
* this overrides the ".sysop-show { display: none; }" above that applies
* to the same link as well. See [[phab:T45013]]
*
* Hide the images in editnotices to keep them readable in VE view.
* Long term, editnotices should become a core feature so that they can be designed responsive.
*/
.ve-ui-mwNoticesPopupTool-item .editnotice-redlink,
.ve-ui-mwNoticesPopupTool-item .mbox-image,
.ve-ui-mwNoticesPopupTool-item .mbox-imageright {
display: none !important;
}

/* Remove bullets when there are multiple edit page warnings */
ul.permissions-errors > li {
list-style: none none;
}
ul.permissions-errors {
margin: 0;
}

/* Pie chart: transparent borders */
.transborder {
border: solid transparent;
}

/* Generic class for Times-based serif, texhtml class for inline math */
.times-serif,
span.texhtml {
font-family: "Nimbus Roman No9 L", "Times New Roman", Times, serif;
font-size: 118%;
line-height: 1;
}
span.texhtml {
white-space: nowrap;
}
span.texhtml span.texhtml {
font-size: 100%;
}
span.mwe-math-mathml-inline {
font-size: 118%;
}

/* Force tabular and lining display for digits and texhtml */
.digits,
.texhtml {
-moz-font-feature-settings: "lnum", "tnum", "kern" 0;
-webkit-font-feature-settings: "lnum", "tnum", "kern" 0;
font-feature-settings: "lnum", "tnum", "kern" 0;
font-variant-numeric: lining-nums tabular-nums;
font-kerning: none;
}

/* Make <math display="block"> be left aligned with one space indent for compatibility with style conventions */
.mwe-math-fallback-image-display,
.mwe-math-mathml-display {
margin-left: 1.6em !important;
margin-top: 0.6em;
margin-bottom: 0.6em;
}
.mwe-math-mathml-display math {
display: inline;
}

/* Fix styling of transcluded prefindex tables */
table#mw-prefixindex-list-table,
table#mw-prefixindex-nav-table {
width: 98%;
}

/* For portals, added 2011-12-07 -bv
On wide screens, show these as two columns
On narrow and mobile screens, let them collapse into a single column */
.portal-column-left {
float: left;
width: 50%;
}
.portal-column-right {
float: right;
width: 49%;
}
.portal-column-left-wide {
float: left;
width: 60%;
}
.portal-column-right-narrow {
float: right;
width: 39%;
}
.portal-column-left-extra-wide {
float: left;
width: 70%;
}
.portal-column-right-extra-narrow {
float: right;
width: 29%;
}
@media only screen and (max-width: 800px) {
/* Decouple the columns on narrow screens */
.portal-column-left,
.portal-column-right,
.portal-column-left-wide,
.portal-column-right-narrow,
.portal-column-left-extra-wide,
.portal-column-right-extra-narrow {
float: inherit;
width: inherit;
}
}

/* Formerly for announcements, now used intermittently */
#bodyContent .letterhead {
background-image:url('//upload.wikimedia.org/wikipedia/commons/e/e0/Tan-page-corner.png');
background-repeat:no-repeat;
padding: 2em;
background-color: #faf9f2;
}

/* Tree style lists */
.treeview ul {
padding: 0;
margin: 0;
}
.treeview li {
padding: 0;
margin: 0;
list-style-type: none;
list-style-image: none;
}
.treeview li li {
background: url("//upload.wikimedia.org/wikipedia/commons/f/f2/Treeview-grey-line.png") no-repeat 0 -2981px;
/* @noflip */
padding-left: 20px;
text-indent: 0.3em;
}
.treeview li li.lastline {
background-position: 0 -5971px
}
.treeview li.emptyline > ul {
/* @noflip */
margin-left: -1px;
}
/* first line here deals with new situation after RemexHTML switch,
* where emptyline cause the first child to become the 2nd child. Such a mess
*/
.mw-parsermigration-right .treeview li.emptyline > ul > .mw-empty-elt:first-child + .emptyline,
.treeview li.emptyline > ul > li:first-child {
background-position: 0 9px
}

/* hidden sortkey for tablesorter */
td .sortkey,
th .sortkey {
display: none;
speak: none;
}

/* Make it possible to hide checkboxes in <inputbox> */
.inputbox-hidecheckboxes form .inputbox-element,
.inputbox-hidecheckboxes .mw-ui-checkbox {
display: none !important;
}

/* Work-around for [[Phabricator:25965]] (Kaltura advertisement) */
.k-player .k-attribution {
visibility: hidden;
}

/* Move 'play' button of video player to bottom left corner */
.PopUpMediaTransform a .play-btn-large {
margin: 0;
top: auto;
right: auto;
bottom: 0;
left: 0;
}

/* Hide FlaggedRevs notice UI when there are no pending changes */
.flaggedrevs_draft_synced,
.flaggedrevs_stable_synced {
display: none;
}

/* Gallery styles background changes are restricted to screen view. In printing we should avoid applying backgrounds. */
@media screen {
/* The backgrounds for galleries. */
#content .gallerybox div.thumb {
/* Light gray padding */
background-color: #f8f9fa;
}

/* Put a chequered background behind images, only visible if they have transparency.
'.filehistory a img' and '#file img:hover' are handled by MediaWiki core (as of 1.19) */
.gallerybox .thumb img {
background: #fff url(//upload.wikimedia.org/wikipedia/commons/5/5d/Checker-16x16.png) repeat;
}
/* But not on articles, user pages, portals or with opt-out. */
.ns-0 .gallerybox .thumb img,
.ns-2 .gallerybox .thumb img,
.ns-100 .gallerybox .thumb img,
.nochecker .gallerybox .thumb img {
background: #fff;
}

/* T178626 */
#contentSub:empty,
#contentSub2:empty {
display: block !important;
}

#contentSub:empty ~ #jump-to-nav,
#contentSub2:empty ~ #jump-to-nav {
margin-top: -1.4em !important;
margin-bottom: 1.4em !important;
}

}

#toc {
position: fixed;
right: 0;
top: 7em; /* 5em is height of header, 6em brings just under */
/* bottom: 5em; /* 5em puts us above the footer; not bad but too low when TOC is collapsed */

z-index: 10000; /* Ensure we float above the header, etc. */

/* Add opacity (translucency) */
background-color: rgb(249, 249, 249);
background-color: rgba(249, 249, 249, 0.9); /* Higher opacity (last arg) means less transparency */
}
/* Ensure the TOC height doesn't take over the screen; percentages may be higher than view port, so we use pixels */
#toc > ul {
max-height: 350px;
overflow: auto;
}
.toctoggle {
float: right;
}

DualSPHysics Guidelines for Earth Scientists

2019-03-26T21:36:31Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-26T21:31:50Z

Nick:

<h2>History</h2>

<div>[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.</div>

<h2>Guidelines</h2>

The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models

<h2>References Cited</h2>

<sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.

MediaWiki:Common.css

2019-03-26T21:31:42Z

Nick:

/* CSS placed here will affect users of the Vector skin */

@import url("https://fonts.googleapis.com/css?family=Noto+Sans|Noto+Serif")

body {font-family: "Noto Sans", sans-serif}
/* changes the default font used for MediaWiki to Noto Sans (does not include headings or monospaced text) */

div#content h1, div#content h2 {font-family: "Noto Serif", serif}
/* changes the default font used for MediaWiki headings to Noto Serif */

/*
@import url('https://fonts.googleapis.com/css?family=Nunito+Sans|PT+Serif');

$nunito: 'Nunito Sans', sans-serif;
$ptserif: 'PT Serif', serif;

body {font-family: $ptserif}
/* changes the default font used for MediaWiki to PT Serif (does not include headings or monospaced text) */

div#content h1, div#content h2, div#content h3, div#content h4 {font-family: $nunito}
/* changes the default font used for MediaWiki headings to Nunito */
*/

#p-logo a {
display: block;
height: 170px;
width: 170px;
background-repeat: no-repeat;
background-position: 35% 50% !important;
text-decoration: none;
}

/* Change background colors */

#mw-head-base {
margin-top: -5em;
margin-left: 11em;
height: 5em;
background-image: url(http://wiki.geodynamics.umaine.edu/images/9/90/HimalayaPano.png);
background-position: bottom left;
background-repeat: repeat-x;
}

body {
background-color: #ffffff;
}

#mw-head-base {
background-color: #ffffff;
}

#mw-panel {
background-color: #ffffff;
}

#p-navigation {
background-color: #ffffff;
}

#footer {
background-color: #ffffff;
}

#headertabs.round .ui-state-default, .ui-widget-content .ui-state-default, .ui-widget-header .ui-state-default {
border: 1px solid #DDD;
font-weight: normal;
color: #2779AA;
}

/* Reset italic styling set by user agent */
cite, dfn {
font-style: inherit;
}

/* Straight quote marks for <q> */
q {
quotes: '"' '"' "'" "'";
}

/* Avoid collision of blockquote with floating elements by swapping margin and padding */
blockquote {
overflow: hidden;
margin: 1em 0;
padding: 0 40px;
}

/* Prevent the 'double bold' bug in Firefox when using DirectWrite */
strong.selflink {
font-weight: 700;
}

/* Consistent size for <small>, <sub> and <sup> */
small {
font-size: 85%;
}
.mw-body-content sub,
.mw-body-content sup,
span.reference /* for Parsoid */ {
font-size: 80%;
}

/* Same spacing for indented and unidented paragraphs on talk pages */
.ns-talk .mw-body-content dd {
margin-top: 0.4em;
margin-bottom: 0.4em;
}

/* Main page fixes */
#interwiki-completelist {
font-weight: bold;
}

/* Reduce page jumps by hiding collapsed/dismissed content */
.client-js .mw-special-Watchlist #watchlist-message,
.client-js .NavFrame.collapsed .NavContent,
.client-js .collapsible.collapsed > tbody > tr:not(:first-child) {
display: none;
}

/* Tone down 'Changed since last visit' colors */
span.updatedmarker {
background-color: transparent;
color: #006400;
}

/* Edit window toolbar */
#toolbar {
margin-bottom: 6px;
}

/* Hide charinsert base for those not using the gadget */
#editpage-specialchars {
display: none;
}

/* Highlight linked elements (such as clicked references) in blue */
body.action-info .mw-body-content :target,
.citation:target {
background-color: #DEF; /* Fallback */
background-color: rgba(0, 127, 255, 0.133);
}

/* Styling for citations. Breaks long urls, etc., rather than overflowing box */
.citation {
word-wrap: break-word;
}

/* For linked citation numbers and document IDs, where the number need not be shown
on a screen or a handheld, but should be included in the printed version */
@media screen, handheld {
.citation .printonly {
display: none;
}
}

/* Make the list of references smaller */
ol.references,
div.reflist,
div.refbegin {
font-size: 90%; /* Default font-size */
margin-bottom: 0.5em;
}
div.refbegin-100 {
font-size: 100%; /* Option for normal fontsize in {{refbegin}} */
}
div.reflist ol.references {
font-size: 100%; /* Reset font-size when nested in div.reflist */
margin-bottom: 0; /* Avoid double margin when nested in div.reflist */
list-style-type: inherit; /* Enable custom list style types */
}

/* Ensure refs in table headers and the like aren't bold or italic */
sup.reference {
font-weight: normal;
font-style: normal;
}

/* Allow hidden ref errors to be shown by user CSS */
span.brokenref {
display: none;
}

/* Hanging indentation for Template:Refbegin */
.refbegin-hanging-indents > ul {
list-style-type: none;
margin-left: 0;
}
.refbegin-hanging-indents > ul > li,
.refbegin-hanging-indents > dl > dd {
margin-left: 0;
padding-left: 3.2em;
text-indent: -3.2em;
list-style: none;
}

/* Reset top margin for lists embedded in columns */
div.columns {
margin-top: 0.3em;
}
div.columns dl,
div.columns ol,
div.columns ul {
margin-top: 0;
}

/* Avoid elements from breaking between columns */
.nocolbreak,
div.columns li,
div.columns dd dd {
-webkit-column-break-inside: avoid;
page-break-inside: avoid;
break-inside: avoid-column;
}

/* Style for [[Template:Flowlist]] that Lets lists flow around floating objecs */
.flowlist ul {
overflow-x: hidden;
margin-left: 0;
padding-left: 1.6em;
}
.flowlist ol {
overflow-x: hidden;
margin-left: 0;
padding-left: 3.2em;
}
.flowlist dl {
overflow-x: hidden;
}

/* Style for horizontal lists (separator following item).
@source mediawiki.org/wiki/Snippets/Horizontal_lists
@revision 8 (2016-05-21)
@author [[User:Edokter]]
*/
.hlist dl,
.hlist ol,
.hlist ul {
margin: 0;
padding: 0;
}
/* Display list items inline */
.hlist dd,
.hlist dt,
.hlist li {
margin: 0;
display: inline;
}
/* Display nested lists inline */
.hlist.inline,
.hlist.inline dl,
.hlist.inline ol,
.hlist.inline ul,
.hlist dl dl, .hlist dl ol, .hlist dl ul,
.hlist ol dl, .hlist ol ol, .hlist ol ul,
.hlist ul dl, .hlist ul ol, .hlist ul ul {
display: inline;
}
/* Hide empty list items */
.hlist .mw-empty-li {
display: none;
}
/* Generate interpuncts */
.hlist dt:after {
content: ": ";
}
.hlist dd:after,
.hlist li:after {
content: " · ";
font-weight: bold;
}
.hlist dd:last-child:after,
.hlist dt:last-child:after,
.hlist li:last-child:after {
content: none;
}
/* Add parentheses around nested lists */
.hlist dd dd:first-child:before, .hlist dd dt:first-child:before, .hlist dd li:first-child:before,
.hlist dt dd:first-child:before, .hlist dt dt:first-child:before, .hlist dt li:first-child:before,
.hlist li dd:first-child:before, .hlist li dt:first-child:before, .hlist li li:first-child:before {
content: " (";
font-weight: normal;
}
.hlist dd dd:last-child:after, .hlist dd dt:last-child:after, .hlist dd li:last-child:after,
.hlist dt dd:last-child:after, .hlist dt dt:last-child:after, .hlist dt li:last-child:after,
.hlist li dd:last-child:after, .hlist li dt:last-child:after, .hlist li li:last-child:after {
content: ")";
font-weight: normal;
}
/* Put ordinals in front of ordered list items */
.hlist ol {
counter-reset: listitem;
}
.hlist ol > li {
counter-increment: listitem;
}
.hlist ol > li:before {
content: " " counter(listitem) "\a0";
}
.hlist dd ol > li:first-child:before,
.hlist dt ol > li:first-child:before,
.hlist li ol > li:first-child:before {
content: " (" counter(listitem) "\a0";
}

/* Unbulleted lists */
.plainlist ol,
.plainlist ul {
line-height: inherit;
list-style: none none;
margin: 0;
}
.plainlist ol li,
.plainlist ul li {
margin-bottom: 0;
}

/* Default style for navigation boxes */
.navbox { /* Navbox container style */
box-sizing: border-box;
border: 1px solid #a2a9b1;
width: 100%;
clear: both;
font-size: 88%;
text-align: center;
padding: 1px;
margin: 1em auto 0; /* Prevent preceding content from clinging to navboxes */
}
.navbox .navbox {
margin-top: 0; /* No top margin for nested navboxes */
}
.navbox + .navbox {
margin-top: -1px; /* Single pixel border between adjacent navboxes */
}
.navbox-inner,
.navbox-subgroup {
width: 100%;
}
.navbox-group,
.navbox-title,
.navbox-abovebelow {
padding: 0.25em 1em; /* Title, group and above/below styles */
line-height: 1.5em;
text-align: center;
}
th.navbox-group { /* Group style */
white-space: nowrap;
/* @noflip */
text-align: right;
}
.navbox,
.navbox-subgroup {
background: #fdfdfd; /* Background color */
}
.navbox-list {
line-height: 1.5em;
border-color: #fdfdfd; /* Must match background color */
}
/* cell spacing for navbox cells */
tr + tr > .navbox-abovebelow,
tr + tr > .navbox-group,
tr + tr > .navbox-image,
tr + tr > .navbox-list { /* Borders above 2nd, 3rd, etc. rows */
border-top: 2px solid #fdfdfd; /* Must match background color */
}
.navbox th,
.navbox-title {
background: #ccccff; /* Level 1 color */
}
.navbox-abovebelow,
th.navbox-group,
.navbox-subgroup .navbox-title {
background: #ddddff; /* Level 2 color */
}
.navbox-subgroup .navbox-group,
.navbox-subgroup .navbox-abovebelow {
background: #e6e6ff; /* Level 3 color */
}
.navbox-even {
background: #f7f7f7; /* Even row striping */
}
.navbox-odd {
background: transparent; /* Odd row striping */
}
.navbox .hlist td dl,
.navbox .hlist td ol,
.navbox .hlist td ul,
.navbox td.hlist dl,
.navbox td.hlist ol,
.navbox td.hlist ul {
padding: 0.125em 0; /* Adjust hlist padding in navboxes */
}

/* Default styling for Navbar template */
.navbar {
display: inline;
font-size: 88%;
font-weight: normal;
}
.navbar ul {
display: inline;
white-space: nowrap;
}
.mw-body-content .navbar ul {
line-height: inherit;
}
.navbar li {
word-spacing: -0.125em;
}
.navbar.mini li abbr[title] {
font-variant: small-caps;
border-bottom: none;
text-decoration: none;
cursor: inherit;
}
/* Navbar styling when nested in infobox and navbox */
.infobox .navbar {
font-size: 100%;
}
.navbox .navbar {
display: block;
font-size: 100%;
}
.navbox-title .navbar {
/* @noflip */
float: left;
/* @noflip */
text-align: left;
/* @noflip */
margin-right: 0.5em;
}

/* 'show'/'hide' buttons created dynamically by the CollapsibleTables javascript
in [[MediaWiki:Common.js]] are styled here so they can be customised. */
.collapseButton {
/* @noflip */
float: right;
font-weight: normal;
/* @noflip */
margin-left: 0.5em;
/* @noflip */
text-align: right;
width: auto;
}

/* Styling for JQuery makeCollapsible, matching that of collapseButton */
.mw-parser-output .mw-collapsible-toggle {
font-weight: normal;
/* @noflip */
text-align: right;
padding-right: 0.2em;
padding-left: 0.2em;
}
.mw-collapsible-leftside-toggle .mw-collapsible-toggle {
/* @noflip */
float: left;
/* @noflip */
text-align: left;
}

/* Infobox template style */
.infobox {
border: 1px solid #a2a9b1;
border-spacing: 3px;
background-color: #f8f9fa;
color: black;
/* @noflip */
margin: 0.5em 0 0.5em 1em;
padding: 0.2em;
/* @noflip */
float: right;
/* @noflip */
clear: right;
font-size: 88%;
line-height: 1.5em;
}
.infobox caption {
font-size: 125%;
font-weight: bold;
padding: 0.2em;
text-align: center;
}
.infobox td,
.infobox th {
vertical-align: top;
/* @noflip */
text-align: left;
}
.infobox.bordered {
border-collapse: collapse;
}
.infobox.bordered td,
.infobox.bordered th {
border: 1px solid #a2a9b1;
}
.infobox.bordered .borderless td,
.infobox.bordered .borderless th {
border: 0;
}

.infobox.sisterproject {
width: 20em;
font-size: 90%;
}

.infobox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
}
.infobox.standard-talk.bordered td,
.infobox.standard-talk.bordered th {
border: 1px solid #c0c090;
}

/* styles for bordered infobox with merged rows */
.infobox.bordered .mergedtoprow td,
.infobox.bordered .mergedtoprow th {
border: 0;
border-top: 1px solid #a2a9b1;
/* @noflip */
border-right: 1px solid #a2a9b1;
}

.infobox.bordered .mergedrow td,
.infobox.bordered .mergedrow th {
border: 0;
/* @noflip */
border-right: 1px solid #a2a9b1;
}

/* Styles for geography infoboxes, eg countries,
country subdivisions, cities, etc. */
.infobox.geography {
border-collapse: collapse;
line-height: 1.2em;
font-size: 90%;
}

.infobox.geography td,
.infobox.geography th {
border-top: 1px solid #a2a9b1;
padding: 0.4em 0.6em 0.4em 0.6em;
}
.infobox.geography .mergedtoprow td,
.infobox.geography .mergedtoprow th {
border-top: 1px solid #a2a9b1;
padding: 0.4em 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedrow td,
.infobox.geography .mergedrow th {
border: 0;
padding: 0 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedbottomrow td,
.infobox.geography .mergedbottomrow th {
border-top: 0;
border-bottom: 1px solid #a2a9b1;
padding: 0 0.6em 0.4em 0.6em;
}

.infobox.geography .maptable td,
.infobox.geography .maptable th {
border: 0;
padding: 0;
}

/* Normal font styling for table row headers with scope="row" tag */
.wikitable.plainrowheaders th[scope=row] {
font-weight: normal;
/* @noflip */
text-align: left;
}

/* Lists in data cells are always left-aligned */
.wikitable td ul,
.wikitable td ol,
.wikitable td dl {
/* @noflip */
text-align: left;
}
/* ...unless they also use the hlist class */
.toc.hlist ul,
#toc.hlist ul,
.wikitable.hlist td ul,
.wikitable.hlist td ol,
.wikitable.hlist td dl {
text-align: inherit;
}

/* Icons for medialist templates [[Template:Listen]],
[[Template:Multi-listen_start]], [[Template:Video]],
[[Template:Multi-video_start]] */
div.listenlist {
background: url("//upload.wikimedia.org/wikipedia/commons/4/47/Sound-icon.svg") no-repeat scroll 0 0 transparent;
background-size: 30px;
padding-left: 40px;
}

/* Fix for hieroglyphs specificality issue in infoboxes ([[Phabricator:43869]]) */
table.mw-hiero-table td {
vertical-align: middle;
}

/* Style rules for media list templates */
div.medialist {
min-height: 50px;
margin: 1em;
/* @noflip */
background-position: top left;
background-repeat: no-repeat;
}
div.medialist ul {
list-style-type: none;
list-style-image: none;
margin: 0;
}
div.medialist ul li {
padding-bottom: 0.5em;
}
div.medialist ul li li {
font-size: 91%;
padding-bottom: 0;
}

/* Change the external link icon to an Adobe icon for all PDF files
in browsers that support these CSS selectors, like Mozilla and Opera */
div#content a[href$=".pdf"].external,
div#content a[href*=".pdf?"].external,
div#content a[href*=".pdf#"].external,
div#content a[href$=".PDF"].external,
div#content a[href*=".PDF?"].external,
div#content a[href*=".PDF#"].external,
div#mw_content a[href$=".pdf"].external,
div#mw_content a[href*=".pdf?"].external,
div#mw_content a[href*=".pdf#"].external,
div#mw_content a[href$=".PDF"].external,
div#mw_content a[href*=".PDF?"].external,
div#mw_content a[href*=".PDF#"].external {
background: url("//upload.wikimedia.org/wikipedia/commons/2/23/Icons-mini-file_acrobat.gif") no-repeat right;
/* @noflip */
padding-right: 18px;
}

/* Content in columns with CSS instead of tables ([[Template:Columns]]) */
div.columns-2 div.column {
/* @noflip */
float: left;
width: 50%;
min-width: 300px;
}
div.columns-3 div.column {
/* @noflip */
float: left;
width: 33.3%;
min-width: 200px;
}
div.columns-4 div.column {
/* @noflip */
float: left;
width: 25%;
min-width: 150px;
}
div.columns-5 div.column {
/* @noflip */
float: left;
width: 20%;
min-width: 120px;
}

/* Messagebox templates */
.messagebox {
border: 1px solid #a2a9b1;
background-color: #f8f9fa;
width: 80%;
margin: 0 auto 1em auto;
padding: .2em;
}
.messagebox.merge {
border: 1px solid #c0b8cc;
background-color: #f0e5ff;
text-align: center;
}
.messagebox.cleanup {
border: 1px solid #9f9fff;
background-color: #efefff;
text-align: center;
}
.messagebox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
margin: 4px auto;
}
/* For old WikiProject banners inside banner shells. */
.mbox-inside .standard-talk,
.messagebox.nested-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
width: 100%;
margin: 2px 0;
padding: 2px;
}
.messagebox.small {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
}
.messagebox.small-talk {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
background: #F8EABA;
}

/* Cell sizes for ambox/tmbox/imbox/cmbox/ombox/fmbox/dmbox message boxes */
th.mbox-text, td.mbox-text { /* The message body cell(s) */
border: none;
/* @noflip */
padding: 0.25em 0.9em; /* 0.9em left/right */
width: 100%; /* Make all mboxes the same width regardless of text length */
}
td.mbox-image { /* The left image cell */
border: none;
/* @noflip */
padding: 2px 0 2px 0.9em; /* 0.9em left, 0px right */
text-align: center;
}
td.mbox-imageright { /* The right image cell */
border: none;
/* @noflip */
padding: 2px 0.9em 2px 0; /* 0px left, 0.9em right */
text-align: center;
}
td.mbox-empty-cell { /* An empty narrow cell */
border: none;
padding: 0;
width: 1px;
}

/* Article message box styles */
table.ambox {
margin: 0 10%; /* 10% = Will not overlap with other elements */
border: 1px solid #a2a9b1;
/* @noflip */
border-left: 10px solid #36c; /* Default "notice" blue */
background: #fbfbfb;
}
table.ambox + table.ambox { /* Single border between stacked boxes. */
margin-top: -1px;
}
.ambox th.mbox-text,
.ambox td.mbox-text { /* The message body cell(s) */
padding: 0.25em 0.5em; /* 0.5em left/right */
}
.ambox td.mbox-image { /* The left image cell */
/* @noflip */
padding: 2px 0 2px 0.5em; /* 0.5em left, 0px right */
}
.ambox td.mbox-imageright { /* The right image cell */
/* @noflip */
padding: 2px 0.5em 2px 0; /* 0px left, 0.5em right */
}

table.ambox-notice {
/* @noflip */
border-left: 10px solid #36c; /* Blue */
}
table.ambox-speedy {
/* @noflip */
border-left: 10px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.ambox-delete {
/* @noflip */
border-left: 10px solid #b32424; /* Red */
}
table.ambox-content {
/* @noflip */
border-left: 10px solid #f28500; /* Orange */
}
table.ambox-style {
/* @noflip */
border-left: 10px solid #fc3; /* Yellow */
}
table.ambox-move {
/* @noflip */
border-left: 10px solid #9932cc; /* Purple */
}
table.ambox-protection {
/* @noflip */
border-left: 10px solid #a2a9b1; /* Gray-gold */
}

/* Image message box styles */
table.imbox {
margin: 4px 10%;
border-collapse: collapse;
border: 3px solid #36c; /* Default "notice" blue */
background: #fbfbfb;
}
.imbox .mbox-text .imbox { /* For imboxes inside imbox-text cells. */
margin: 0 -0.5em; /* 0.9 - 0.5 = 0.4em left/right. */
display: block; /* Fix for webkit to force 100% width. */
}
.mbox-inside .imbox { /* For imboxes inside other templates. */
margin: 4px;
}

table.imbox-notice {
border: 3px solid #36c; /* Blue */
}
table.imbox-speedy {
border: 3px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.imbox-delete {
border: 3px solid #b32424; /* Red */
}
table.imbox-content {
border: 3px solid #f28500; /* Orange */
}
table.imbox-style {
border: 3px solid #fc3; /* Yellow */
}
table.imbox-move {
border: 3px solid #9932cc; /* Purple */
}
table.imbox-protection {
border: 3px solid #a2a9b1; /* Gray-gold */
}
table.imbox-license {
border: 3px solid #88a; /* Dark gray */
background: #f7f8ff; /* Light gray */
}
table.imbox-featured {
border: 3px solid #cba135; /* Brown-gold */
}

/* Category message box styles */
table.cmbox {
margin: 3px 10%;
border-collapse: collapse;
border: 1px solid #a2a9b1;
background: #DFE8FF; /* Default "notice" blue */
}

table.cmbox-notice {
background: #D8E8FF; /* Blue */
}
table.cmbox-speedy {
margin-top: 4px;
margin-bottom: 4px;
border: 4px solid #b32424; /* Red */
background: #FFDBDB; /* Pink */
}
table.cmbox-delete {
background: #FFDBDB; /* Red */
}
table.cmbox-content {
background: #FFE7CE; /* Orange */
}
table.cmbox-style {
background: #FFF9DB; /* Yellow */
}
table.cmbox-move {
background: #E4D8FF; /* Purple */
}
table.cmbox-protection {
background: #EFEFE1; /* Gray-gold */
}

/* Other pages message box styles */
table.ombox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #a2a9b1; /* Default "notice" gray */
background: #f8f9fa;
}

table.ombox-notice {
border: 1px solid #a2a9b1; /* Gray */
}
table.ombox-speedy {
border: 2px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.ombox-delete {
border: 2px solid #b32424; /* Red */
}
table.ombox-content {
border: 1px solid #f28500; /* Orange */
}
table.ombox-style {
border: 1px solid #fc3; /* Yellow */
}
table.ombox-move {
border: 1px solid #9932cc; /* Purple */
}
table.ombox-protection {
border: 2px solid #a2a9b1; /* Gray-gold */
}

/* Talk page message box styles */
table.tmbox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #c0c090; /* Default "notice" gray-brown */
background: #f8eaba;
}
.mediawiki .mbox-inside .tmbox { /* For tmboxes inside other templates. The "mediawiki" class ensures that */
margin: 2px 0; /* this declaration overrides other styles (including mbox-small above) */
width: 100%; /* For Safari and Opera */
}
.mbox-inside .tmbox.mbox-small { /* "small" tmboxes should not be small when */
line-height: 1.5em; /* also "nested", so reset styles that are */
font-size: 100%; /* set in "mbox-small" above. */
}

table.tmbox-speedy {
border: 2px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.tmbox-delete {
border: 2px solid #b32424; /* Red */
}
table.tmbox-content {
border: 2px solid #f28500; /* Orange */
}
table.tmbox-style {
border: 2px solid #fc3; /* Yellow */
}
table.tmbox-move {
border: 2px solid #9932cc; /* Purple */
}
table.tmbox-protection,
table.tmbox-notice {
border: 1px solid #c0c090; /* Gray-brown */
}

/* Disambig and set index box styles */
table.dmbox {
clear: both;
margin: 0.9em 1em;
border-top: 1px solid #ccc;
border-bottom: 1px solid #ccc;
background: transparent;
}

/* Footer and header message box styles */
table.fmbox {
clear: both;
margin: 0.2em 0;
width: 100%;
border: 1px solid #a2a9b1;
background: #f8f9fa; /* Default "system" gray */
}
table.fmbox-system {
background: #f8f9fa;
}
table.fmbox-warning {
border: 1px solid #bb7070; /* Dark pink */
background: #ffdbdb; /* Pink */
}
table.fmbox-editnotice {
background: transparent;
}
/* Div based "warning" style fmbox messages. */
div.mw-warning-with-logexcerpt,
div.mw-lag-warn-high,
div.mw-cascadeprotectedwarning,
div#mw-protect-cascadeon,
div.titleblacklist-warning,
div.locked-warning {
clear: both;
margin: 0.2em 0;
border: 1px solid #bb7070;
background: #ffdbdb;
padding: 0.25em 0.9em;
}
/* Div based "system" style fmbox messages.
Used in [[MediaWiki:Readonly lag]]. */
div.mw-lag-warn-normal,
div.fmbox-system {
clear: both;
margin: 0.2em 0;
border: 1px solid #a2a9b1;
background: #f8f9fa;
padding: 0.25em 0.9em;
}

/* These mbox-small classes must be placed after all other
ambox/tmbox/ombox etc classes. "html body.mediawiki" is so
they override "table.ambox + table.ambox" above. */
html body.mediawiki .mbox-small { /* For the "small=yes" option. */
/* @noflip */
clear: right;
/* @noflip */
float: right;
/* @noflip */
margin: 4px 0 4px 1em;
box-sizing: border-box;
width: 238px;
font-size: 88%;
line-height: 1.25em;
}
html body.mediawiki .mbox-small-left { /* For the "small=left" option. */
/* @noflip */
margin: 4px 1em 4px 0;
box-sizing: border-box;
overflow: hidden;
width: 238px;
border-collapse: collapse;
font-size: 88%;
line-height: 1.25em;
}

/* Style for compact ambox */
/* Hide the images */
.compact-ambox table .mbox-image,
.compact-ambox table .mbox-imageright,
.compact-ambox table .mbox-empty-cell {
display: none;
}
/* Remove borders, backgrounds, padding, etc. */
.compact-ambox table.ambox {
border: none;
border-collapse: collapse;
background: transparent;
margin: 0 0 0 1.6em !important;
padding: 0 !important;
width: auto;
display: block;
}
body.mediawiki .compact-ambox table.mbox-small-left {
font-size: 100%;
width: auto;
margin: 0;
}
/* Style the text cell as a list item and remove its padding */
.compact-ambox table .mbox-text {
padding: 0 !important;
margin: 0 !important;
}
.compact-ambox table .mbox-text-span {
display: list-item;
line-height: 1.5em;
list-style-type: square;
list-style-image: url(/w/skins/MonoBook/bullet.gif);
}
.skin-vector .compact-ambox table .mbox-text-span {
list-style-type: disc;
list-style-image: url(/w/skins/Vector/images/bullet-icon.svg);
list-style-image: url(/w/skins/Vector/images/bullet-icon.png)\9;
}
/* Allow for hiding text in compact form */
.compact-ambox .hide-when-compact {
display: none;
}

/* Remove default styles for [[MediaWiki:Noarticletext]]. */
div.noarticletext {
border: none;
background: transparent;
padding: 0;
}

/* Hide (formatting) elements from screen, but not from screenreaders */
.visualhide {
position: absolute;
left: -10000px;
top: auto;
width: 1px;
height: 1px;
overflow: hidden;
}

/* suppress missing interwiki image links where #ifexist cannot
be used due to high number of requests see .hidden-redlink on
[[m:MediaWiki:Common.css]] */
.check-icon a.new {
display: none;
speak: none;
}

/* Removes underlines from certain links */
.nounderlines a,
.IPA a:link, .IPA a:visited {
text-decoration: none !important;
}

/* Standard Navigationsleisten, aka box hiding thingy
from .de. Documentation at [[Wikipedia:NavFrame]]. */
div.NavFrame {
margin: 0;
padding: 4px;
border: 1px solid #a2a9b1;
text-align: center;
border-collapse: collapse;
font-size: 95%;
}
div.NavFrame + div.NavFrame {
border-top-style: none;
border-top-style: hidden;
}
div.NavPic {
background-color: #fff;
margin: 0;
padding: 2px;
/* @noflip */
float: left;
}
div.NavFrame div.NavHead {
line-height: 1.6em;
font-weight: bold;
background-color: #ccf;
position: relative;
}
div.NavFrame p,
div.NavFrame div.NavContent,
div.NavFrame div.NavContent p {
font-size: 100%;
}
div.NavEnd {
margin: 0;
padding: 0;
line-height: 1px;
clear: both;
}
a.NavToggle {
position: absolute;
top: 0;
/* @noflip */
right: 3px;
font-weight: normal;
font-size: 90%;
}

/* Hatnotes and disambiguation notices */
.hatnote {
font-style: italic;
}
.hatnote i {
font-style: normal;
}
div.hatnote {
/* @noflip */
padding-left: 1.6em;
margin-bottom: 0.5em;
}
div.hatnote + div.hatnote {
margin-top: -0.5em;
}

/* Allow transcluded pages to display in lists rather than a table. */
.listify td { display: list-item; }
.listify tr { display: block; }
.listify table { display: block; }

/* Geographical coordinates defaults. See [[Template:Coord/link]]
for how these are used. The classes "geo", "longitude", and
"latitude" are used by the [[Geo microformat]]. */
.geo-default, .geo-dms, .geo-dec { display: inline; }
.geo-nondefault, .geo-multi-punct { display: none; }
.longitude, .latitude { white-space: nowrap; }

/* Temporary(!) fix for horizontal TOC in Blink (Chrone/Opera) */
.hlist .tocnumber,
.hlist .toctext {
display: inline;
}
/* When <div class="nonumtoc"> is used on the table of contents,
the ToC will display without numbers */
.nonumtoc .tocnumber {
display: none;
}
.nonumtoc #toc ul,
.nonumtoc .toc ul {
line-height: 1.5em;
list-style: none none;
margin: .3em 0 0;
padding: 0;
}
.hlist.nonumtoc #toc ul ul,
.hlist.nonumtoc .toc ul ul {
/* @noflip */
margin: 0;
}

/* Allow limiting of which header levels are shown in a TOC;
<div class="toclimit-3">, for instance, will limit to
showing ==headings== and ===headings=== but no further
(as long as there are no =headings= on the page, which
there shouldn't be according to the MoS). */
.toclimit-2 .toclevel-1 ul,
.toclimit-3 .toclevel-2 ul,
.toclimit-4 .toclevel-3 ul,
.toclimit-5 .toclevel-4 ul,
.toclimit-6 .toclevel-5 ul,
.toclimit-7 .toclevel-6 ul {
display: none;
}

/* Styling for Template:Quote */
blockquote.templatequote div.templatequotecite {
line-height: 1.5em;
/* @noflip */
text-align: left;
/* @noflip */
padding-left: 1.6em;
margin-top: 0;
}

/* User block messages */
div.user-block {
padding: 5px;
margin-bottom: 0.5em;
border: 1px solid #A9A9A9;
background-color: #FFEFD5;
}

/* Prevent line breaks in silly places:
1) Where desired
2) Links when we don't want them to
3) Bold "links" to the page itself */
.nowrap,
.nowraplinks a,
.nowraplinks .selflink {
white-space: nowrap;
}
.nowrap pre {
white-space: pre;
}
/* But allow wrapping where desired: */
.wrap,
.wraplinks a {
white-space: normal;
}

/* For template documentation */
.template-documentation {
clear: both;
margin: 1em 0 0 0;
border: 1px solid #a2a9b1;
background-color: #ecfcf4;
padding: 1em;
}

/* Increase the height of the image upload box */
#wpUploadDescription {
height: 13em;
}

/* Minimum thumb width */
.thumbinner {
min-width: 100px;
}

/* Prevent floating boxes from overlapping any category listings,
file histories, edit previews, and edit [Show changes] views. */
#mw-subcategories, #mw-pages, #mw-category-media,
#filehistory, #wikiPreview, #wikiDiff {
clear: both;
}

/* Selectively hide headers in WikiProject banners */
.wpb .wpb-header { display: none; }
.wpbs-inner .wpb .wpb-header { display: block; } /* for IE */
.wpbs-inner .wpb .wpb-header { display: table-row; } /* for real browsers */
.wpbs-inner .wpb-outside { display: none; } /* hide things that should only display outside shells */

/* Styling for Abuse Filter tags */
.mw-tag-markers {
font-style:italic;
font-size:90%;
}

/* Hide stuff meant for accounts with special permissions. Made visible again in
[[MediaWiki:Group-sysop.css]], [[MediaWiki:Group-patroller.css]],
[[MediaWiki:Group-templateeditor.css]], [[MediaWiki:Group-extendedmover.css]] and [[Mediawiki:Group-autoconfirmed.css]]. */
.sysop-show,
.templateeditor-show,
.extendedmover-show,
.patroller-show,
.autoconfirmed-show,
.user-show {
display: none;
}

/**
* Hide the redlink generated by {{Editnotice}},
* this overrides the ".sysop-show { display: none; }" above that applies
* to the same link as well. See [[phab:T45013]]
*
* Hide the images in editnotices to keep them readable in VE view.
* Long term, editnotices should become a core feature so that they can be designed responsive.
*/
.ve-ui-mwNoticesPopupTool-item .editnotice-redlink,
.ve-ui-mwNoticesPopupTool-item .mbox-image,
.ve-ui-mwNoticesPopupTool-item .mbox-imageright {
display: none !important;
}

/* Remove bullets when there are multiple edit page warnings */
ul.permissions-errors > li {
list-style: none none;
}
ul.permissions-errors {
margin: 0;
}

/* Pie chart: transparent borders */
.transborder {
border: solid transparent;
}

/* Generic class for Times-based serif, texhtml class for inline math */
.times-serif,
span.texhtml {
font-family: "Nimbus Roman No9 L", "Times New Roman", Times, serif;
font-size: 118%;
line-height: 1;
}
span.texhtml {
white-space: nowrap;
}
span.texhtml span.texhtml {
font-size: 100%;
}
span.mwe-math-mathml-inline {
font-size: 118%;
}

/* Force tabular and lining display for digits and texhtml */
.digits,
.texhtml {
-moz-font-feature-settings: "lnum", "tnum", "kern" 0;
-webkit-font-feature-settings: "lnum", "tnum", "kern" 0;
font-feature-settings: "lnum", "tnum", "kern" 0;
font-variant-numeric: lining-nums tabular-nums;
font-kerning: none;
}

/* Make <math display="block"> be left aligned with one space indent for compatibility with style conventions */
.mwe-math-fallback-image-display,
.mwe-math-mathml-display {
margin-left: 1.6em !important;
margin-top: 0.6em;
margin-bottom: 0.6em;
}
.mwe-math-mathml-display math {
display: inline;
}

/* Fix styling of transcluded prefindex tables */
table#mw-prefixindex-list-table,
table#mw-prefixindex-nav-table {
width: 98%;
}

/* For portals, added 2011-12-07 -bv
On wide screens, show these as two columns
On narrow and mobile screens, let them collapse into a single column */
.portal-column-left {
float: left;
width: 50%;
}
.portal-column-right {
float: right;
width: 49%;
}
.portal-column-left-wide {
float: left;
width: 60%;
}
.portal-column-right-narrow {
float: right;
width: 39%;
}
.portal-column-left-extra-wide {
float: left;
width: 70%;
}
.portal-column-right-extra-narrow {
float: right;
width: 29%;
}
@media only screen and (max-width: 800px) {
/* Decouple the columns on narrow screens */
.portal-column-left,
.portal-column-right,
.portal-column-left-wide,
.portal-column-right-narrow,
.portal-column-left-extra-wide,
.portal-column-right-extra-narrow {
float: inherit;
width: inherit;
}
}

/* Formerly for announcements, now used intermittently */
#bodyContent .letterhead {
background-image:url('//upload.wikimedia.org/wikipedia/commons/e/e0/Tan-page-corner.png');
background-repeat:no-repeat;
padding: 2em;
background-color: #faf9f2;
}

/* Tree style lists */
.treeview ul {
padding: 0;
margin: 0;
}
.treeview li {
padding: 0;
margin: 0;
list-style-type: none;
list-style-image: none;
}
.treeview li li {
background: url("//upload.wikimedia.org/wikipedia/commons/f/f2/Treeview-grey-line.png") no-repeat 0 -2981px;
/* @noflip */
padding-left: 20px;
text-indent: 0.3em;
}
.treeview li li.lastline {
background-position: 0 -5971px
}
.treeview li.emptyline > ul {
/* @noflip */
margin-left: -1px;
}
/* first line here deals with new situation after RemexHTML switch,
* where emptyline cause the first child to become the 2nd child. Such a mess
*/
.mw-parsermigration-right .treeview li.emptyline > ul > .mw-empty-elt:first-child + .emptyline,
.treeview li.emptyline > ul > li:first-child {
background-position: 0 9px
}

/* hidden sortkey for tablesorter */
td .sortkey,
th .sortkey {
display: none;
speak: none;
}

/* Make it possible to hide checkboxes in <inputbox> */
.inputbox-hidecheckboxes form .inputbox-element,
.inputbox-hidecheckboxes .mw-ui-checkbox {
display: none !important;
}

/* Work-around for [[Phabricator:25965]] (Kaltura advertisement) */
.k-player .k-attribution {
visibility: hidden;
}

/* Move 'play' button of video player to bottom left corner */
.PopUpMediaTransform a .play-btn-large {
margin: 0;
top: auto;
right: auto;
bottom: 0;
left: 0;
}

/* Hide FlaggedRevs notice UI when there are no pending changes */
.flaggedrevs_draft_synced,
.flaggedrevs_stable_synced {
display: none;
}

/* Gallery styles background changes are restricted to screen view. In printing we should avoid applying backgrounds. */
@media screen {
/* The backgrounds for galleries. */
#content .gallerybox div.thumb {
/* Light gray padding */
background-color: #f8f9fa;
}

/* Put a chequered background behind images, only visible if they have transparency.
'.filehistory a img' and '#file img:hover' are handled by MediaWiki core (as of 1.19) */
.gallerybox .thumb img {
background: #fff url(//upload.wikimedia.org/wikipedia/commons/5/5d/Checker-16x16.png) repeat;
}
/* But not on articles, user pages, portals or with opt-out. */
.ns-0 .gallerybox .thumb img,
.ns-2 .gallerybox .thumb img,
.ns-100 .gallerybox .thumb img,
.nochecker .gallerybox .thumb img {
background: #fff;
}

/* T178626 */
#contentSub:empty,
#contentSub2:empty {
display: block !important;
}

#contentSub:empty ~ #jump-to-nav,
#contentSub2:empty ~ #jump-to-nav {
margin-top: -1.4em !important;
margin-bottom: 1.4em !important;
}

}

#toc {
position: fixed;
right: 0;
top: 7em; /* 5em is height of header, 6em brings just under */
/* bottom: 5em; /* 5em puts us above the footer; not bad but too low when TOC is collapsed */

z-index: 10000; /* Ensure we float above the header, etc. */

/* Add opacity (translucency) */
background-color: rgb(249, 249, 249);
background-color: rgba(249, 249, 249, 0.9); /* Higher opacity (last arg) means less transparency */
}
/* Ensure the TOC height doesn't take over the screen; percentages may be higher than view port, so we use pixels */
#toc > ul {
max-height: 350px;
overflow: auto;
}
.toctoggle {
float: right;
}

MediaWiki:Common.css

2019-03-26T21:29:34Z

Nick:

MediaWiki:Common.css

2019-03-26T21:28:25Z

Nick:

/* CSS placed here will affect users of the Vector skin */

/*@import url("https://fonts.googleapis.com/css?family=Noto+Sans|Noto+Serif")*/
@import url('https://fonts.googleapis.com/css?family=Nunito+Sans|PT+Serif');

$nunito: 'Nunito Sans', sans-serif;
$ptserif: 'PT Serif', serif;

body {font-family: $ptserif, sans-serif}
/* changes the default font used for MediaWiki to PT Serif (does not include headings or monospaced text) */

div#content h1, div#content h2, div#content h3, div#content h4 {font-family: $nunito, serif}
/* changes the default font used for MediaWiki headings to Nunito */

#p-logo a {
display: block;
height: 170px;
width: 170px;
background-repeat: no-repeat;
background-position: 35% 50% !important;
text-decoration: none;
}

/* Change background colors */

#mw-head-base {
margin-top: -5em;
margin-left: 11em;
height: 5em;
background-image: url(http://wiki.geodynamics.umaine.edu/images/9/90/HimalayaPano.png);
background-position: bottom left;
background-repeat: repeat-x;
}

body {
background-color: #ffffff;
}

#mw-head-base {
background-color: #ffffff;
}

#mw-panel {
background-color: #ffffff;
}

#p-navigation {
background-color: #ffffff;
}

#footer {
background-color: #ffffff;
}

#headertabs.round .ui-state-default, .ui-widget-content .ui-state-default, .ui-widget-header .ui-state-default {
border: 1px solid #DDD;
font-weight: normal;
color: #2779AA;
}

/* Reset italic styling set by user agent */
cite, dfn {
font-style: inherit;
}

/* Straight quote marks for <q> */
q {
quotes: '"' '"' "'" "'";
}

/* Avoid collision of blockquote with floating elements by swapping margin and padding */
blockquote {
overflow: hidden;
margin: 1em 0;
padding: 0 40px;
}

/* Prevent the 'double bold' bug in Firefox when using DirectWrite */
strong.selflink {
font-weight: 700;
}

/* Consistent size for <small>, <sub> and <sup> */
small {
font-size: 85%;
}
.mw-body-content sub,
.mw-body-content sup,
span.reference /* for Parsoid */ {
font-size: 80%;
}

/* Same spacing for indented and unidented paragraphs on talk pages */
.ns-talk .mw-body-content dd {
margin-top: 0.4em;
margin-bottom: 0.4em;
}

/* Main page fixes */
#interwiki-completelist {
font-weight: bold;
}

/* Reduce page jumps by hiding collapsed/dismissed content */
.client-js .mw-special-Watchlist #watchlist-message,
.client-js .NavFrame.collapsed .NavContent,
.client-js .collapsible.collapsed > tbody > tr:not(:first-child) {
display: none;
}

/* Tone down 'Changed since last visit' colors */
span.updatedmarker {
background-color: transparent;
color: #006400;
}

/* Edit window toolbar */
#toolbar {
margin-bottom: 6px;
}

/* Hide charinsert base for those not using the gadget */
#editpage-specialchars {
display: none;
}

/* Highlight linked elements (such as clicked references) in blue */
body.action-info .mw-body-content :target,
.citation:target {
background-color: #DEF; /* Fallback */
background-color: rgba(0, 127, 255, 0.133);
}

/* Styling for citations. Breaks long urls, etc., rather than overflowing box */
.citation {
word-wrap: break-word;
}

/* For linked citation numbers and document IDs, where the number need not be shown
on a screen or a handheld, but should be included in the printed version */
@media screen, handheld {
.citation .printonly {
display: none;
}
}

/* Make the list of references smaller */
ol.references,
div.reflist,
div.refbegin {
font-size: 90%; /* Default font-size */
margin-bottom: 0.5em;
}
div.refbegin-100 {
font-size: 100%; /* Option for normal fontsize in {{refbegin}} */
}
div.reflist ol.references {
font-size: 100%; /* Reset font-size when nested in div.reflist */
margin-bottom: 0; /* Avoid double margin when nested in div.reflist */
list-style-type: inherit; /* Enable custom list style types */
}

/* Ensure refs in table headers and the like aren't bold or italic */
sup.reference {
font-weight: normal;
font-style: normal;
}

/* Allow hidden ref errors to be shown by user CSS */
span.brokenref {
display: none;
}

/* Hanging indentation for Template:Refbegin */
.refbegin-hanging-indents > ul {
list-style-type: none;
margin-left: 0;
}
.refbegin-hanging-indents > ul > li,
.refbegin-hanging-indents > dl > dd {
margin-left: 0;
padding-left: 3.2em;
text-indent: -3.2em;
list-style: none;
}

/* Reset top margin for lists embedded in columns */
div.columns {
margin-top: 0.3em;
}
div.columns dl,
div.columns ol,
div.columns ul {
margin-top: 0;
}

/* Avoid elements from breaking between columns */
.nocolbreak,
div.columns li,
div.columns dd dd {
-webkit-column-break-inside: avoid;
page-break-inside: avoid;
break-inside: avoid-column;
}

/* Style for [[Template:Flowlist]] that Lets lists flow around floating objecs */
.flowlist ul {
overflow-x: hidden;
margin-left: 0;
padding-left: 1.6em;
}
.flowlist ol {
overflow-x: hidden;
margin-left: 0;
padding-left: 3.2em;
}
.flowlist dl {
overflow-x: hidden;
}

/* Style for horizontal lists (separator following item).
@source mediawiki.org/wiki/Snippets/Horizontal_lists
@revision 8 (2016-05-21)
@author [[User:Edokter]]
*/
.hlist dl,
.hlist ol,
.hlist ul {
margin: 0;
padding: 0;
}
/* Display list items inline */
.hlist dd,
.hlist dt,
.hlist li {
margin: 0;
display: inline;
}
/* Display nested lists inline */
.hlist.inline,
.hlist.inline dl,
.hlist.inline ol,
.hlist.inline ul,
.hlist dl dl, .hlist dl ol, .hlist dl ul,
.hlist ol dl, .hlist ol ol, .hlist ol ul,
.hlist ul dl, .hlist ul ol, .hlist ul ul {
display: inline;
}
/* Hide empty list items */
.hlist .mw-empty-li {
display: none;
}
/* Generate interpuncts */
.hlist dt:after {
content: ": ";
}
.hlist dd:after,
.hlist li:after {
content: " · ";
font-weight: bold;
}
.hlist dd:last-child:after,
.hlist dt:last-child:after,
.hlist li:last-child:after {
content: none;
}
/* Add parentheses around nested lists */
.hlist dd dd:first-child:before, .hlist dd dt:first-child:before, .hlist dd li:first-child:before,
.hlist dt dd:first-child:before, .hlist dt dt:first-child:before, .hlist dt li:first-child:before,
.hlist li dd:first-child:before, .hlist li dt:first-child:before, .hlist li li:first-child:before {
content: " (";
font-weight: normal;
}
.hlist dd dd:last-child:after, .hlist dd dt:last-child:after, .hlist dd li:last-child:after,
.hlist dt dd:last-child:after, .hlist dt dt:last-child:after, .hlist dt li:last-child:after,
.hlist li dd:last-child:after, .hlist li dt:last-child:after, .hlist li li:last-child:after {
content: ")";
font-weight: normal;
}
/* Put ordinals in front of ordered list items */
.hlist ol {
counter-reset: listitem;
}
.hlist ol > li {
counter-increment: listitem;
}
.hlist ol > li:before {
content: " " counter(listitem) "\a0";
}
.hlist dd ol > li:first-child:before,
.hlist dt ol > li:first-child:before,
.hlist li ol > li:first-child:before {
content: " (" counter(listitem) "\a0";
}

/* Unbulleted lists */
.plainlist ol,
.plainlist ul {
line-height: inherit;
list-style: none none;
margin: 0;
}
.plainlist ol li,
.plainlist ul li {
margin-bottom: 0;
}

/* Default style for navigation boxes */
.navbox { /* Navbox container style */
box-sizing: border-box;
border: 1px solid #a2a9b1;
width: 100%;
clear: both;
font-size: 88%;
text-align: center;
padding: 1px;
margin: 1em auto 0; /* Prevent preceding content from clinging to navboxes */
}
.navbox .navbox {
margin-top: 0; /* No top margin for nested navboxes */
}
.navbox + .navbox {
margin-top: -1px; /* Single pixel border between adjacent navboxes */
}
.navbox-inner,
.navbox-subgroup {
width: 100%;
}
.navbox-group,
.navbox-title,
.navbox-abovebelow {
padding: 0.25em 1em; /* Title, group and above/below styles */
line-height: 1.5em;
text-align: center;
}
th.navbox-group { /* Group style */
white-space: nowrap;
/* @noflip */
text-align: right;
}
.navbox,
.navbox-subgroup {
background: #fdfdfd; /* Background color */
}
.navbox-list {
line-height: 1.5em;
border-color: #fdfdfd; /* Must match background color */
}
/* cell spacing for navbox cells */
tr + tr > .navbox-abovebelow,
tr + tr > .navbox-group,
tr + tr > .navbox-image,
tr + tr > .navbox-list { /* Borders above 2nd, 3rd, etc. rows */
border-top: 2px solid #fdfdfd; /* Must match background color */
}
.navbox th,
.navbox-title {
background: #ccccff; /* Level 1 color */
}
.navbox-abovebelow,
th.navbox-group,
.navbox-subgroup .navbox-title {
background: #ddddff; /* Level 2 color */
}
.navbox-subgroup .navbox-group,
.navbox-subgroup .navbox-abovebelow {
background: #e6e6ff; /* Level 3 color */
}
.navbox-even {
background: #f7f7f7; /* Even row striping */
}
.navbox-odd {
background: transparent; /* Odd row striping */
}
.navbox .hlist td dl,
.navbox .hlist td ol,
.navbox .hlist td ul,
.navbox td.hlist dl,
.navbox td.hlist ol,
.navbox td.hlist ul {
padding: 0.125em 0; /* Adjust hlist padding in navboxes */
}

/* Default styling for Navbar template */
.navbar {
display: inline;
font-size: 88%;
font-weight: normal;
}
.navbar ul {
display: inline;
white-space: nowrap;
}
.mw-body-content .navbar ul {
line-height: inherit;
}
.navbar li {
word-spacing: -0.125em;
}
.navbar.mini li abbr[title] {
font-variant: small-caps;
border-bottom: none;
text-decoration: none;
cursor: inherit;
}
/* Navbar styling when nested in infobox and navbox */
.infobox .navbar {
font-size: 100%;
}
.navbox .navbar {
display: block;
font-size: 100%;
}
.navbox-title .navbar {
/* @noflip */
float: left;
/* @noflip */
text-align: left;
/* @noflip */
margin-right: 0.5em;
}

/* 'show'/'hide' buttons created dynamically by the CollapsibleTables javascript
in [[MediaWiki:Common.js]] are styled here so they can be customised. */
.collapseButton {
/* @noflip */
float: right;
font-weight: normal;
/* @noflip */
margin-left: 0.5em;
/* @noflip */
text-align: right;
width: auto;
}

/* Styling for JQuery makeCollapsible, matching that of collapseButton */
.mw-parser-output .mw-collapsible-toggle {
font-weight: normal;
/* @noflip */
text-align: right;
padding-right: 0.2em;
padding-left: 0.2em;
}
.mw-collapsible-leftside-toggle .mw-collapsible-toggle {
/* @noflip */
float: left;
/* @noflip */
text-align: left;
}

/* Infobox template style */
.infobox {
border: 1px solid #a2a9b1;
border-spacing: 3px;
background-color: #f8f9fa;
color: black;
/* @noflip */
margin: 0.5em 0 0.5em 1em;
padding: 0.2em;
/* @noflip */
float: right;
/* @noflip */
clear: right;
font-size: 88%;
line-height: 1.5em;
}
.infobox caption {
font-size: 125%;
font-weight: bold;
padding: 0.2em;
text-align: center;
}
.infobox td,
.infobox th {
vertical-align: top;
/* @noflip */
text-align: left;
}
.infobox.bordered {
border-collapse: collapse;
}
.infobox.bordered td,
.infobox.bordered th {
border: 1px solid #a2a9b1;
}
.infobox.bordered .borderless td,
.infobox.bordered .borderless th {
border: 0;
}

.infobox.sisterproject {
width: 20em;
font-size: 90%;
}

.infobox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
}
.infobox.standard-talk.bordered td,
.infobox.standard-talk.bordered th {
border: 1px solid #c0c090;
}

/* styles for bordered infobox with merged rows */
.infobox.bordered .mergedtoprow td,
.infobox.bordered .mergedtoprow th {
border: 0;
border-top: 1px solid #a2a9b1;
/* @noflip */
border-right: 1px solid #a2a9b1;
}

.infobox.bordered .mergedrow td,
.infobox.bordered .mergedrow th {
border: 0;
/* @noflip */
border-right: 1px solid #a2a9b1;
}

/* Styles for geography infoboxes, eg countries,
country subdivisions, cities, etc. */
.infobox.geography {
border-collapse: collapse;
line-height: 1.2em;
font-size: 90%;
}

.infobox.geography td,
.infobox.geography th {
border-top: 1px solid #a2a9b1;
padding: 0.4em 0.6em 0.4em 0.6em;
}
.infobox.geography .mergedtoprow td,
.infobox.geography .mergedtoprow th {
border-top: 1px solid #a2a9b1;
padding: 0.4em 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedrow td,
.infobox.geography .mergedrow th {
border: 0;
padding: 0 0.6em 0.2em 0.6em;
}

.infobox.geography .mergedbottomrow td,
.infobox.geography .mergedbottomrow th {
border-top: 0;
border-bottom: 1px solid #a2a9b1;
padding: 0 0.6em 0.4em 0.6em;
}

.infobox.geography .maptable td,
.infobox.geography .maptable th {
border: 0;
padding: 0;
}

/* Normal font styling for table row headers with scope="row" tag */
.wikitable.plainrowheaders th[scope=row] {
font-weight: normal;
/* @noflip */
text-align: left;
}

/* Lists in data cells are always left-aligned */
.wikitable td ul,
.wikitable td ol,
.wikitable td dl {
/* @noflip */
text-align: left;
}
/* ...unless they also use the hlist class */
.toc.hlist ul,
#toc.hlist ul,
.wikitable.hlist td ul,
.wikitable.hlist td ol,
.wikitable.hlist td dl {
text-align: inherit;
}

/* Icons for medialist templates [[Template:Listen]],
[[Template:Multi-listen_start]], [[Template:Video]],
[[Template:Multi-video_start]] */
div.listenlist {
background: url("//upload.wikimedia.org/wikipedia/commons/4/47/Sound-icon.svg") no-repeat scroll 0 0 transparent;
background-size: 30px;
padding-left: 40px;
}

/* Fix for hieroglyphs specificality issue in infoboxes ([[Phabricator:43869]]) */
table.mw-hiero-table td {
vertical-align: middle;
}

/* Style rules for media list templates */
div.medialist {
min-height: 50px;
margin: 1em;
/* @noflip */
background-position: top left;
background-repeat: no-repeat;
}
div.medialist ul {
list-style-type: none;
list-style-image: none;
margin: 0;
}
div.medialist ul li {
padding-bottom: 0.5em;
}
div.medialist ul li li {
font-size: 91%;
padding-bottom: 0;
}

/* Change the external link icon to an Adobe icon for all PDF files
in browsers that support these CSS selectors, like Mozilla and Opera */
div#content a[href$=".pdf"].external,
div#content a[href*=".pdf?"].external,
div#content a[href*=".pdf#"].external,
div#content a[href$=".PDF"].external,
div#content a[href*=".PDF?"].external,
div#content a[href*=".PDF#"].external,
div#mw_content a[href$=".pdf"].external,
div#mw_content a[href*=".pdf?"].external,
div#mw_content a[href*=".pdf#"].external,
div#mw_content a[href$=".PDF"].external,
div#mw_content a[href*=".PDF?"].external,
div#mw_content a[href*=".PDF#"].external {
background: url("//upload.wikimedia.org/wikipedia/commons/2/23/Icons-mini-file_acrobat.gif") no-repeat right;
/* @noflip */
padding-right: 18px;
}

/* Content in columns with CSS instead of tables ([[Template:Columns]]) */
div.columns-2 div.column {
/* @noflip */
float: left;
width: 50%;
min-width: 300px;
}
div.columns-3 div.column {
/* @noflip */
float: left;
width: 33.3%;
min-width: 200px;
}
div.columns-4 div.column {
/* @noflip */
float: left;
width: 25%;
min-width: 150px;
}
div.columns-5 div.column {
/* @noflip */
float: left;
width: 20%;
min-width: 120px;
}

/* Messagebox templates */
.messagebox {
border: 1px solid #a2a9b1;
background-color: #f8f9fa;
width: 80%;
margin: 0 auto 1em auto;
padding: .2em;
}
.messagebox.merge {
border: 1px solid #c0b8cc;
background-color: #f0e5ff;
text-align: center;
}
.messagebox.cleanup {
border: 1px solid #9f9fff;
background-color: #efefff;
text-align: center;
}
.messagebox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
margin: 4px auto;
}
/* For old WikiProject banners inside banner shells. */
.mbox-inside .standard-talk,
.messagebox.nested-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
width: 100%;
margin: 2px 0;
padding: 2px;
}
.messagebox.small {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
}
.messagebox.small-talk {
width: 238px;
font-size: 85%;
/* @noflip */
float: right;
clear: both;
/* @noflip */
margin: 0 0 1em 1em;
line-height: 1.25em;
background: #F8EABA;
}

/* Cell sizes for ambox/tmbox/imbox/cmbox/ombox/fmbox/dmbox message boxes */
th.mbox-text, td.mbox-text { /* The message body cell(s) */
border: none;
/* @noflip */
padding: 0.25em 0.9em; /* 0.9em left/right */
width: 100%; /* Make all mboxes the same width regardless of text length */
}
td.mbox-image { /* The left image cell */
border: none;
/* @noflip */
padding: 2px 0 2px 0.9em; /* 0.9em left, 0px right */
text-align: center;
}
td.mbox-imageright { /* The right image cell */
border: none;
/* @noflip */
padding: 2px 0.9em 2px 0; /* 0px left, 0.9em right */
text-align: center;
}
td.mbox-empty-cell { /* An empty narrow cell */
border: none;
padding: 0;
width: 1px;
}

/* Article message box styles */
table.ambox {
margin: 0 10%; /* 10% = Will not overlap with other elements */
border: 1px solid #a2a9b1;
/* @noflip */
border-left: 10px solid #36c; /* Default "notice" blue */
background: #fbfbfb;
}
table.ambox + table.ambox { /* Single border between stacked boxes. */
margin-top: -1px;
}
.ambox th.mbox-text,
.ambox td.mbox-text { /* The message body cell(s) */
padding: 0.25em 0.5em; /* 0.5em left/right */
}
.ambox td.mbox-image { /* The left image cell */
/* @noflip */
padding: 2px 0 2px 0.5em; /* 0.5em left, 0px right */
}
.ambox td.mbox-imageright { /* The right image cell */
/* @noflip */
padding: 2px 0.5em 2px 0; /* 0px left, 0.5em right */
}

table.ambox-notice {
/* @noflip */
border-left: 10px solid #36c; /* Blue */
}
table.ambox-speedy {
/* @noflip */
border-left: 10px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.ambox-delete {
/* @noflip */
border-left: 10px solid #b32424; /* Red */
}
table.ambox-content {
/* @noflip */
border-left: 10px solid #f28500; /* Orange */
}
table.ambox-style {
/* @noflip */
border-left: 10px solid #fc3; /* Yellow */
}
table.ambox-move {
/* @noflip */
border-left: 10px solid #9932cc; /* Purple */
}
table.ambox-protection {
/* @noflip */
border-left: 10px solid #a2a9b1; /* Gray-gold */
}

/* Image message box styles */
table.imbox {
margin: 4px 10%;
border-collapse: collapse;
border: 3px solid #36c; /* Default "notice" blue */
background: #fbfbfb;
}
.imbox .mbox-text .imbox { /* For imboxes inside imbox-text cells. */
margin: 0 -0.5em; /* 0.9 - 0.5 = 0.4em left/right. */
display: block; /* Fix for webkit to force 100% width. */
}
.mbox-inside .imbox { /* For imboxes inside other templates. */
margin: 4px;
}

table.imbox-notice {
border: 3px solid #36c; /* Blue */
}
table.imbox-speedy {
border: 3px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.imbox-delete {
border: 3px solid #b32424; /* Red */
}
table.imbox-content {
border: 3px solid #f28500; /* Orange */
}
table.imbox-style {
border: 3px solid #fc3; /* Yellow */
}
table.imbox-move {
border: 3px solid #9932cc; /* Purple */
}
table.imbox-protection {
border: 3px solid #a2a9b1; /* Gray-gold */
}
table.imbox-license {
border: 3px solid #88a; /* Dark gray */
background: #f7f8ff; /* Light gray */
}
table.imbox-featured {
border: 3px solid #cba135; /* Brown-gold */
}

/* Category message box styles */
table.cmbox {
margin: 3px 10%;
border-collapse: collapse;
border: 1px solid #a2a9b1;
background: #DFE8FF; /* Default "notice" blue */
}

table.cmbox-notice {
background: #D8E8FF; /* Blue */
}
table.cmbox-speedy {
margin-top: 4px;
margin-bottom: 4px;
border: 4px solid #b32424; /* Red */
background: #FFDBDB; /* Pink */
}
table.cmbox-delete {
background: #FFDBDB; /* Red */
}
table.cmbox-content {
background: #FFE7CE; /* Orange */
}
table.cmbox-style {
background: #FFF9DB; /* Yellow */
}
table.cmbox-move {
background: #E4D8FF; /* Purple */
}
table.cmbox-protection {
background: #EFEFE1; /* Gray-gold */
}

/* Other pages message box styles */
table.ombox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #a2a9b1; /* Default "notice" gray */
background: #f8f9fa;
}

table.ombox-notice {
border: 1px solid #a2a9b1; /* Gray */
}
table.ombox-speedy {
border: 2px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.ombox-delete {
border: 2px solid #b32424; /* Red */
}
table.ombox-content {
border: 1px solid #f28500; /* Orange */
}
table.ombox-style {
border: 1px solid #fc3; /* Yellow */
}
table.ombox-move {
border: 1px solid #9932cc; /* Purple */
}
table.ombox-protection {
border: 2px solid #a2a9b1; /* Gray-gold */
}

/* Talk page message box styles */
table.tmbox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #c0c090; /* Default "notice" gray-brown */
background: #f8eaba;
}
.mediawiki .mbox-inside .tmbox { /* For tmboxes inside other templates. The "mediawiki" class ensures that */
margin: 2px 0; /* this declaration overrides other styles (including mbox-small above) */
width: 100%; /* For Safari and Opera */
}
.mbox-inside .tmbox.mbox-small { /* "small" tmboxes should not be small when */
line-height: 1.5em; /* also "nested", so reset styles that are */
font-size: 100%; /* set in "mbox-small" above. */
}

table.tmbox-speedy {
border: 2px solid #b32424; /* Red */
background: #fee7e6; /* Pink */
}
table.tmbox-delete {
border: 2px solid #b32424; /* Red */
}
table.tmbox-content {
border: 2px solid #f28500; /* Orange */
}
table.tmbox-style {
border: 2px solid #fc3; /* Yellow */
}
table.tmbox-move {
border: 2px solid #9932cc; /* Purple */
}
table.tmbox-protection,
table.tmbox-notice {
border: 1px solid #c0c090; /* Gray-brown */
}

/* Disambig and set index box styles */
table.dmbox {
clear: both;
margin: 0.9em 1em;
border-top: 1px solid #ccc;
border-bottom: 1px solid #ccc;
background: transparent;
}

/* Footer and header message box styles */
table.fmbox {
clear: both;
margin: 0.2em 0;
width: 100%;
border: 1px solid #a2a9b1;
background: #f8f9fa; /* Default "system" gray */
}
table.fmbox-system {
background: #f8f9fa;
}
table.fmbox-warning {
border: 1px solid #bb7070; /* Dark pink */
background: #ffdbdb; /* Pink */
}
table.fmbox-editnotice {
background: transparent;
}
/* Div based "warning" style fmbox messages. */
div.mw-warning-with-logexcerpt,
div.mw-lag-warn-high,
div.mw-cascadeprotectedwarning,
div#mw-protect-cascadeon,
div.titleblacklist-warning,
div.locked-warning {
clear: both;
margin: 0.2em 0;
border: 1px solid #bb7070;
background: #ffdbdb;
padding: 0.25em 0.9em;
}
/* Div based "system" style fmbox messages.
Used in [[MediaWiki:Readonly lag]]. */
div.mw-lag-warn-normal,
div.fmbox-system {
clear: both;
margin: 0.2em 0;
border: 1px solid #a2a9b1;
background: #f8f9fa;
padding: 0.25em 0.9em;
}

/* These mbox-small classes must be placed after all other
ambox/tmbox/ombox etc classes. "html body.mediawiki" is so
they override "table.ambox + table.ambox" above. */
html body.mediawiki .mbox-small { /* For the "small=yes" option. */
/* @noflip */
clear: right;
/* @noflip */
float: right;
/* @noflip */
margin: 4px 0 4px 1em;
box-sizing: border-box;
width: 238px;
font-size: 88%;
line-height: 1.25em;
}
html body.mediawiki .mbox-small-left { /* For the "small=left" option. */
/* @noflip */
margin: 4px 1em 4px 0;
box-sizing: border-box;
overflow: hidden;
width: 238px;
border-collapse: collapse;
font-size: 88%;
line-height: 1.25em;
}

/* Style for compact ambox */
/* Hide the images */
.compact-ambox table .mbox-image,
.compact-ambox table .mbox-imageright,
.compact-ambox table .mbox-empty-cell {
display: none;
}
/* Remove borders, backgrounds, padding, etc. */
.compact-ambox table.ambox {
border: none;
border-collapse: collapse;
background: transparent;
margin: 0 0 0 1.6em !important;
padding: 0 !important;
width: auto;
display: block;
}
body.mediawiki .compact-ambox table.mbox-small-left {
font-size: 100%;
width: auto;
margin: 0;
}
/* Style the text cell as a list item and remove its padding */
.compact-ambox table .mbox-text {
padding: 0 !important;
margin: 0 !important;
}
.compact-ambox table .mbox-text-span {
display: list-item;
line-height: 1.5em;
list-style-type: square;
list-style-image: url(/w/skins/MonoBook/bullet.gif);
}
.skin-vector .compact-ambox table .mbox-text-span {
list-style-type: disc;
list-style-image: url(/w/skins/Vector/images/bullet-icon.svg);
list-style-image: url(/w/skins/Vector/images/bullet-icon.png)\9;
}
/* Allow for hiding text in compact form */
.compact-ambox .hide-when-compact {
display: none;
}

/* Remove default styles for [[MediaWiki:Noarticletext]]. */
div.noarticletext {
border: none;
background: transparent;
padding: 0;
}

/* Hide (formatting) elements from screen, but not from screenreaders */
.visualhide {
position: absolute;
left: -10000px;
top: auto;
width: 1px;
height: 1px;
overflow: hidden;
}

/* suppress missing interwiki image links where #ifexist cannot
be used due to high number of requests see .hidden-redlink on
[[m:MediaWiki:Common.css]] */
.check-icon a.new {
display: none;
speak: none;
}

/* Removes underlines from certain links */
.nounderlines a,
.IPA a:link, .IPA a:visited {
text-decoration: none !important;
}

/* Standard Navigationsleisten, aka box hiding thingy
from .de. Documentation at [[Wikipedia:NavFrame]]. */
div.NavFrame {
margin: 0;
padding: 4px;
border: 1px solid #a2a9b1;
text-align: center;
border-collapse: collapse;
font-size: 95%;
}
div.NavFrame + div.NavFrame {
border-top-style: none;
border-top-style: hidden;
}
div.NavPic {
background-color: #fff;
margin: 0;
padding: 2px;
/* @noflip */
float: left;
}
div.NavFrame div.NavHead {
line-height: 1.6em;
font-weight: bold;
background-color: #ccf;
position: relative;
}
div.NavFrame p,
div.NavFrame div.NavContent,
div.NavFrame div.NavContent p {
font-size: 100%;
}
div.NavEnd {
margin: 0;
padding: 0;
line-height: 1px;
clear: both;
}
a.NavToggle {
position: absolute;
top: 0;
/* @noflip */
right: 3px;
font-weight: normal;
font-size: 90%;
}

/* Hatnotes and disambiguation notices */
.hatnote {
font-style: italic;
}
.hatnote i {
font-style: normal;
}
div.hatnote {
/* @noflip */
padding-left: 1.6em;
margin-bottom: 0.5em;
}
div.hatnote + div.hatnote {
margin-top: -0.5em;
}

/* Allow transcluded pages to display in lists rather than a table. */
.listify td { display: list-item; }
.listify tr { display: block; }
.listify table { display: block; }

/* Geographical coordinates defaults. See [[Template:Coord/link]]
for how these are used. The classes "geo", "longitude", and
"latitude" are used by the [[Geo microformat]]. */
.geo-default, .geo-dms, .geo-dec { display: inline; }
.geo-nondefault, .geo-multi-punct { display: none; }
.longitude, .latitude { white-space: nowrap; }

/* Temporary(!) fix for horizontal TOC in Blink (Chrone/Opera) */
.hlist .tocnumber,
.hlist .toctext {
display: inline;
}
/* When <div class="nonumtoc"> is used on the table of contents,
the ToC will display without numbers */
.nonumtoc .tocnumber {
display: none;
}
.nonumtoc #toc ul,
.nonumtoc .toc ul {
line-height: 1.5em;
list-style: none none;
margin: .3em 0 0;
padding: 0;
}
.hlist.nonumtoc #toc ul ul,
.hlist.nonumtoc .toc ul ul {
/* @noflip */
margin: 0;
}

/* Allow limiting of which header levels are shown in a TOC;
<div class="toclimit-3">, for instance, will limit to
showing ==headings== and ===headings=== but no further
(as long as there are no =headings= on the page, which
there shouldn't be according to the MoS). */
.toclimit-2 .toclevel-1 ul,
.toclimit-3 .toclevel-2 ul,
.toclimit-4 .toclevel-3 ul,
.toclimit-5 .toclevel-4 ul,
.toclimit-6 .toclevel-5 ul,
.toclimit-7 .toclevel-6 ul {
display: none;
}

/* Styling for Template:Quote */
blockquote.templatequote div.templatequotecite {
line-height: 1.5em;
/* @noflip */
text-align: left;
/* @noflip */
padding-left: 1.6em;
margin-top: 0;
}

/* User block messages */
div.user-block {
padding: 5px;
margin-bottom: 0.5em;
border: 1px solid #A9A9A9;
background-color: #FFEFD5;
}

/* Prevent line breaks in silly places:
1) Where desired
2) Links when we don't want them to
3) Bold "links" to the page itself */
.nowrap,
.nowraplinks a,
.nowraplinks .selflink {
white-space: nowrap;
}
.nowrap pre {
white-space: pre;
}
/* But allow wrapping where desired: */
.wrap,
.wraplinks a {
white-space: normal;
}

/* For template documentation */
.template-documentation {
clear: both;
margin: 1em 0 0 0;
border: 1px solid #a2a9b1;
background-color: #ecfcf4;
padding: 1em;
}

/* Increase the height of the image upload box */
#wpUploadDescription {
height: 13em;
}

/* Minimum thumb width */
.thumbinner {
min-width: 100px;
}

/* Prevent floating boxes from overlapping any category listings,
file histories, edit previews, and edit [Show changes] views. */
#mw-subcategories, #mw-pages, #mw-category-media,
#filehistory, #wikiPreview, #wikiDiff {
clear: both;
}

/* Selectively hide headers in WikiProject banners */
.wpb .wpb-header { display: none; }
.wpbs-inner .wpb .wpb-header { display: block; } /* for IE */
.wpbs-inner .wpb .wpb-header { display: table-row; } /* for real browsers */
.wpbs-inner .wpb-outside { display: none; } /* hide things that should only display outside shells */

/* Styling for Abuse Filter tags */
.mw-tag-markers {
font-style:italic;
font-size:90%;
}

/* Hide stuff meant for accounts with special permissions. Made visible again in
[[MediaWiki:Group-sysop.css]], [[MediaWiki:Group-patroller.css]],
[[MediaWiki:Group-templateeditor.css]], [[MediaWiki:Group-extendedmover.css]] and [[Mediawiki:Group-autoconfirmed.css]]. */
.sysop-show,
.templateeditor-show,
.extendedmover-show,
.patroller-show,
.autoconfirmed-show,
.user-show {
display: none;
}

/**
* Hide the redlink generated by {{Editnotice}},
* this overrides the ".sysop-show { display: none; }" above that applies
* to the same link as well. See [[phab:T45013]]
*
* Hide the images in editnotices to keep them readable in VE view.
* Long term, editnotices should become a core feature so that they can be designed responsive.
*/
.ve-ui-mwNoticesPopupTool-item .editnotice-redlink,
.ve-ui-mwNoticesPopupTool-item .mbox-image,
.ve-ui-mwNoticesPopupTool-item .mbox-imageright {
display: none !important;
}

/* Remove bullets when there are multiple edit page warnings */
ul.permissions-errors > li {
list-style: none none;
}
ul.permissions-errors {
margin: 0;
}

/* Pie chart: transparent borders */
.transborder {
border: solid transparent;
}

/* Generic class for Times-based serif, texhtml class for inline math */
.times-serif,
span.texhtml {
font-family: "Nimbus Roman No9 L", "Times New Roman", Times, serif;
font-size: 118%;
line-height: 1;
}
span.texhtml {
white-space: nowrap;
}
span.texhtml span.texhtml {
font-size: 100%;
}
span.mwe-math-mathml-inline {
font-size: 118%;
}

/* Force tabular and lining display for digits and texhtml */
.digits,
.texhtml {
-moz-font-feature-settings: "lnum", "tnum", "kern" 0;
-webkit-font-feature-settings: "lnum", "tnum", "kern" 0;
font-feature-settings: "lnum", "tnum", "kern" 0;
font-variant-numeric: lining-nums tabular-nums;
font-kerning: none;
}

/* Make <math display="block"> be left aligned with one space indent for compatibility with style conventions */
.mwe-math-fallback-image-display,
.mwe-math-mathml-display {
margin-left: 1.6em !important;
margin-top: 0.6em;
margin-bottom: 0.6em;
}
.mwe-math-mathml-display math {
display: inline;
}

/* Fix styling of transcluded prefindex tables */
table#mw-prefixindex-list-table,
table#mw-prefixindex-nav-table {
width: 98%;
}

/* For portals, added 2011-12-07 -bv
On wide screens, show these as two columns
On narrow and mobile screens, let them collapse into a single column */
.portal-column-left {
float: left;
width: 50%;
}
.portal-column-right {
float: right;
width: 49%;
}
.portal-column-left-wide {
float: left;
width: 60%;
}
.portal-column-right-narrow {
float: right;
width: 39%;
}
.portal-column-left-extra-wide {
float: left;
width: 70%;
}
.portal-column-right-extra-narrow {
float: right;
width: 29%;
}
@media only screen and (max-width: 800px) {
/* Decouple the columns on narrow screens */
.portal-column-left,
.portal-column-right,
.portal-column-left-wide,
.portal-column-right-narrow,
.portal-column-left-extra-wide,
.portal-column-right-extra-narrow {
float: inherit;
width: inherit;
}
}

/* Formerly for announcements, now used intermittently */
#bodyContent .letterhead {
background-image:url('//upload.wikimedia.org/wikipedia/commons/e/e0/Tan-page-corner.png');
background-repeat:no-repeat;
padding: 2em;
background-color: #faf9f2;
}

/* Tree style lists */
.treeview ul {
padding: 0;
margin: 0;
}
.treeview li {
padding: 0;
margin: 0;
list-style-type: none;
list-style-image: none;
}
.treeview li li {
background: url("//upload.wikimedia.org/wikipedia/commons/f/f2/Treeview-grey-line.png") no-repeat 0 -2981px;
/* @noflip */
padding-left: 20px;
text-indent: 0.3em;
}
.treeview li li.lastline {
background-position: 0 -5971px
}
.treeview li.emptyline > ul {
/* @noflip */
margin-left: -1px;
}
/* first line here deals with new situation after RemexHTML switch,
* where emptyline cause the first child to become the 2nd child. Such a mess
*/
.mw-parsermigration-right .treeview li.emptyline > ul > .mw-empty-elt:first-child + .emptyline,
.treeview li.emptyline > ul > li:first-child {
background-position: 0 9px
}

/* hidden sortkey for tablesorter */
td .sortkey,
th .sortkey {
display: none;
speak: none;
}

/* Make it possible to hide checkboxes in <inputbox> */
.inputbox-hidecheckboxes form .inputbox-element,
.inputbox-hidecheckboxes .mw-ui-checkbox {
display: none !important;
}

/* Work-around for [[Phabricator:25965]] (Kaltura advertisement) */
.k-player .k-attribution {
visibility: hidden;
}

/* Move 'play' button of video player to bottom left corner */
.PopUpMediaTransform a .play-btn-large {
margin: 0;
top: auto;
right: auto;
bottom: 0;
left: 0;
}

/* Hide FlaggedRevs notice UI when there are no pending changes */
.flaggedrevs_draft_synced,
.flaggedrevs_stable_synced {
display: none;
}

/* Gallery styles background changes are restricted to screen view. In printing we should avoid applying backgrounds. */
@media screen {
/* The backgrounds for galleries. */
#content .gallerybox div.thumb {
/* Light gray padding */
background-color: #f8f9fa;
}

/* Put a chequered background behind images, only visible if they have transparency.
'.filehistory a img' and '#file img:hover' are handled by MediaWiki core (as of 1.19) */
.gallerybox .thumb img {
background: #fff url(//upload.wikimedia.org/wikipedia/commons/5/5d/Checker-16x16.png) repeat;
}
/* But not on articles, user pages, portals or with opt-out. */
.ns-0 .gallerybox .thumb img,
.ns-2 .gallerybox .thumb img,
.ns-100 .gallerybox .thumb img,
.nochecker .gallerybox .thumb img {
background: #fff;
}

/* T178626 */
#contentSub:empty,
#contentSub2:empty {
display: block !important;
}

#contentSub:empty ~ #jump-to-nav,
#contentSub2:empty ~ #jump-to-nav {
margin-top: -1.4em !important;
margin-bottom: 1.4em !important;
}

}

#toc {
position: fixed;
right: 0;
top: 7em; /* 5em is height of header, 6em brings just under */
/* bottom: 5em; /* 5em puts us above the footer; not bad but too low when TOC is collapsed */

z-index: 10000; /* Ensure we float above the header, etc. */

/* Add opacity (translucency) */
background-color: rgb(249, 249, 249);
background-color: rgba(249, 249, 249, 0.9); /* Higher opacity (last arg) means less transparency */
}
/* Ensure the TOC height doesn't take over the screen; percentages may be higher than view port, so we use pixels */
#toc > ul {
max-height: 350px;
overflow: auto;
}
.toctoggle {
float: right;
}

DualSPHysics Guidelines for Earth Scientists

2019-03-26T21:18:57Z

Nick:

<h2>History</h2>

[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful [https://dual.sphysics.org/index.php/features/ features] to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.

<h2>Guidelines</h2>

The following guidelines are based on my experience working with the DualSPHysics code. My hope is that the points presented here will allow you to succeed in creating models

<h2>References Cited</h2>

<sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.

DualSPHysics Guidelines for Earth Scientists

2019-03-26T21:18:46Z

Nick:

DualSPHysics Guidelines for Earth Scientists

2019-03-26T21:12:31Z

Nick:

'''History'''

[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful features to the code which broaden the scope of scientific questions we can address using the SPH method. In particular, the addition of new boundary conditions, liquid + sediment physics, and fluid-structure interaction with Discrete Element Method systems have created research opportunities in the earth sciences.

'''Guidelines'''

'''References Cited'''

<sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.

DualSPHysics Guidelines for Earth Scientists

2019-03-26T20:55:11Z

Nick:

[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a [https://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed Particle Hydrodynamics] (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs. Since then, the DualSPHysics development team has added many useful features to the code which broaden the scope of scientific questions we can address using the SPH method.

'''References Cited'''

<sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.

DualSPHysics Guidelines for Earth Scientists

2019-03-26T20:51:25Z

Nick:

[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a Smoothed Particle Hydrodynamics (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

Researchers in the [https://umaine.edu/earthclimate/ UMaine School of Earth and Climate Sciences] and [https://climatechange.umaine.edu/ Climate Change Institute] began using DualSPHysics v3.1 in 2014 to investigate the kinematics of icebergs.

'''References Cited'''

<sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.

DualSPHysics Guidelines for Earth Scientists

2019-03-26T20:20:29Z

Nick: Created page with "[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a Smoothed Particle Hydrodynamics (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-S..."

[https://dual.sphysics.org/ DualSPHysics]<sup>1</sup> is a Smoothed Particle Hydrodynamics (SPH) solver used to solve the fundamental equations of fluid dynamics, the Navier-Stokes equations. Among the modern SPH solvers available, there are many advantages to choosing DualSPHysics, most notably the optimization of the code for GPU parallel processing. Running the DualSPHysics code on a GPU vastly decreases solution times, thereby allowing high-resolution and/or large-domain cases to be executed efficiently.

'''References Cited'''

<sup>1</sup>Crespo, A.J.C., Domínguez, J.M., Rogers, B.D., Gómez-Gesteira, M., Longshaw, S., Canelas, R., Vacondio, R., Barreiro, A., and García-Feal, O., 2015, DualSPHysics: Open-source parallel CFD solver based on Smoothed Particle Hydrodynamics (SPH): Computer Physics Communications, v. 187, p. 204–216, doi: 10.1016/j.cpc.2014.10.004.

DropdownElements

2019-03-07T04:20:13Z

Nick:

10,100,1000
----

Ten.gif,Hundred.gif,Thousand.gif
----

Ten sentence.|Hundred sentence.| Thousand sentence.