Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Complete Update regarding the new Input Config

The Configuration File contains all information necessary for the algorithm to run through the optimisation. It is subdivided into different areas regarding the Geometry, Loads and Constraints, Cases (Events) and optimisation parameter. The file is written in JSON file format.

...

applicationRequest

OptimizationLoop

Indicates that the regular optimisation loop is executed

automaticFunctionalFacesDetection.positiveNonDesignDirection

true

Functional Surfaces are automatically detected. These areas grow during an optimisation to guarantee sharp edges and functional surfaces after the intersection.

If all functional surfaces have a Machining Allowance applied to them, this option should be deactivated.

Loads and Constraints

The Loads and Constraints section collects all information regarding the loads and fixations applied to the different geometries.

...

configuration.symmetry.x

configuration.symmetry.y

configuration.symmetry.z

x-axis as symmetry plane (Y-Z-Plane).

y-axis as symmetry plane (X-Z-Plane).

z-axis as symmetry plane (X-Y-Plane).

configuration.symmetry.coordinateSystem

If the symmetry is to refer to a local coordinate system, the following command must also be entered (Coordinate_system_1 is the name of the local coordinate system and can vary).

configuration.maxConcurrentGPUSolvers

Maximum number of GPUs used by the optimisation (support GPUs: Nvidia Quadro Graphics Cards supported by CUDA Driver)

configuration.buildSpace

Geometry used for the intersection with the Design Space to receive the nominal geometry

configuration.offsetSpace

Geometry used for the intersection with the Design Space to receive the print geometry

configuration.unitSystem

Used unit system

configuration.eigenThreads

Number of CPU threads that can be used to build the matrix. At least two cores should always remain free. We recommend using 2-6 threads.

configuration.complexity

Defines how complex the design is getting. More information here.

configuration.solver.<name>.strategy

InternalCPU: CPU based solver

ExternLegacy: External (GPU) solver

configuration.solver.<name>.host

IP of the external solver, localhost for the same workstation. IP for cloud, for what the matrix is built locally and sent to the calculation unit. Large amounts of data can be moved with a corresponding amount of time.

configuration.solver.<name>.port

Port which is used to access the CudaSolver. This can be selected arbitrarily, according to the specified value when starting the solver. (The default port for the Cuda service is 42001)

automaticFunctionalFacesDetection.positiveNonDesignDirection=true

false

Functional Surfaces are automatically detected. These areas grow during an optimisation to guarantee sharp edges and functional surfaces after the intersection.

If all functional surfaces have a Machining Allowance applied to them, this option should be deactivated.

Example

Info

"configuration": {
".index": 9,
"buildSpace": "DesignSpace_machiningCut",
"complexity": "14",
"eigenThreads": "4",
"offsetSpace": "DesignSpace_machiningOffset",
"remesher": {
".index": 1,
"designCandidateRemesher": {
".index": 0,
"enabled": "true"
},
"voxelIntersectionRemesher": {
".index": 1,
"enabled": "true"
}
},
"solver": {
".index": 0,
"solver1": {
".index": 0,
"host": "localhost",
"port": "42004",
"strategy": "ExternLegacy"
}
},
"unitSystem": "SI_K"

...