JSON Objects: Boundary Conditions¶
All scenarios require the specification of boundary conditions. Different scenarios support different types of boundary conditions, but all boundary conditions have a couple of common members.
boundary¶
All boundary conditions must be applied to a specified surface. The value should be a path to an *.ply or *.stl file. This path can be relative to the location of the scenario json file. For example, if the configuration json file is in the same directory as restraint.ply then the following would be valid.
"boundary": "restraint.ply"
units¶
All boundary conditions can optionally specify units.
type¶
The type member differentiates the variety of possible boundary conditions. Each specific boundary condition will contain an example json instance that will have the value for type.