ON-DEM Benchmark Definition Template
Please delete text below when you make your template.
Before completing this form/template, please consider the nature of the comparison that you will consider. We have adopted the following definitions:
1. Benchmark: Comparison between two or more codes (e.g. in terms of performance, accuracy, etc.)
Verification: A given code does what is supposed to. Verification is provided by means of an analytical solution (if available) or in terms of the ability of the code to replicate the relevant physics.
Validation: A given code agrees with observed reality. Validation is usually provided by comparison against physical experiments/measurements.
Challenge: Where experimental measurements are made independently, and these are simulated using a given DEM code. The simulation results are then independently verified against experimental results which were not known by the people simulating them.
Benchmark Lead(s) Add/remove rows if necessary please use Confluence profile tags (e.g. @Daniel Barreto ) | ||
Confirmed collaborator(s) (At least one collaborator in addition to lead(s) is required. Every benchmark must consider at least two different DEM codes). Add rows if necessary. | ||
DEM Code name | Responsible persons | |
|
| |
Benchmark Type
| Benchmark Verification Validation Challenge | |
Target Result (e.g. How close to an analytical solution?) |
| |
Benchmark Description Describe the problem and state the physics/behaviour to be considered by the problem (maximum 200 words)
| ||
Benchmark Geometry and Boundary Conditions This should be ideally provided as a file(s) stored in a repository (provide details below adding/removing rows if needed). Where appropriate, also include a relevant image of the problem, and additional notes here.
Please describe/specify boundary conditions (rigid boundaries, periodic boundaries, stress and/or strain control:
File type(s) for geometry, e.g., .stl, etc.:
| ||
File name | Description | Location/link (e.g. DOI) |
|
|
|
|
|
|
|
|
|
Image(s) of the geometry (Paste here) | ||
Additional notes
| ||
Particle Type Select all applicable | Spheres Sphere clumps Ellipsoidal Super-quadrics Level-set Potential surfaces Polygonal Polyhedra Sphero-polyhedra Other (specify):
| |
Mixture Type Select all applicable | Monodisperse Bidisperse Polydisperse Uniformly graded Other (specify): | |
Particle properties Provide particle density/densities, Young’s modulus and Poisson’s ratio (where appropriate), as well as properties that are required to define particle shape (i.e. radii, longest/shortest axis, sphere separation distance for clumps, etc.). Add/remove rows if required. | ||
|
| |
|
| |
|
| |
Contact model(s) and properties Specify model used in the normal and tangential direction and provide all its properties required for unambiguous definition. Add/remove rows if required. Normal direction: Tangential direction: ON-DEM Contact Model Database Reference: | ||
|
| |
|
| |
|
| |
|
| |
Simulation setup Parameters for simulation and analysis. Add rows if required (e.g. number of cycles, unbalanced force ratio, etc.) | ||
Time-step |
| |
Data output interval |
| |
|
| |
Initial configuration Provide any additional input files and or details not included in the Problem Geometry section. These should be provided as files stored in a repository File type(s) Repository link and file name: Additional details and images:
| ||
Output data format The Open DEM format must be used. Please specify format for any data not specified. Include an example as a file stored in a repository Repository link and fie name: Additional specifications:
| ||
Other considerations and notes Please use this space to provide any additional information and/or data not covered in the previous sections of the template | ||
Tentative schedule | ||
Expression of interest by: |
| |
Start date (data received from): |
| |
Submission deadline for data: |
| |
Data analysis to be completed by: |
| |
Tentative publication date for draft submission |
| |