Remove and replace symmetry coordinate system
The Configuration File contains all information necessary for the algorithm to run through the optimisation. It is subdivided into different areas regarding the Configuration, Schedule, Material, Failure Criterion, Event, Boundary Conditions, Design, Geometry, Machining Allowance, Non-Design Spaces and Coordinate System. The file is written in the JSON-file format.
...
configuration.offsetSpace | Geometry used for the intersection with the Design Space to receive the print geometry |
configuration.buildSpace | Geometry used for the intersection with the Design Space to receive the nominal geometry |
configuration.complexity | Defines how complex the design is getting. More information here. |
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.maxConcurrentGPUSolvers | Maximum number of GPUs used by the optimisation (support GPUs: Nvidia Quadro Graphics Cards supported by CUDA Driver) |
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). |
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) |
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. |
configuration.unitSystem | Used unit system |
...
In the Coordinate System section all used coordinate systems are listed and defined. All Coordinate System are based on the Principal Coordinate System that is always written to the configuration file.
coordinateSystem.<name>.alpha coordinateSystem.<name>.beta coordinateSystem.<name>.gamma | The coordinate system is located/orientated with coordinate values and Euler angles regarding the global coordinate system. |
coordinateSystem.<name>.origin.x coordinateSystem.<name>.origin.y coordinateSystem.<name>.origin.z | The coordinate system has a point of origin. |
...