Versions Compared

Key

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

With the Advanced User Settings the optimisation parameters can be influenced even further than the options Strut Density and Shape Quality. Furthermore, a few unsupported options are available using the Advanced User Settings like Restart, usage of a Startspace, thickness constraints or Casting design rules.

Child pages (Children Display)
depth1
allChildrentrue
style
sortAndReverse
excerptTypesimplerich content
first0

The Advanced User Settings can be added to a Scenario by right clicking on this and selecting the option as shown in the picture below.

...

This governs how far the optimization value of two symmetric elements is allowed to differ while still being considered equivalent. In theory any value works: the higher the value the more zealously the algorithm will try to keep Soft Symmetry, possibly degrading the quality of the produced geometry compared to a non-symmetric one. The default value is 1e5e-12.

Attempt Soft Symmetry:

Whether or not Soft Symmetry is attempted at all can be (de)activated here.

...

Specifies how many asymmetric elements are sufficient for the "dynamic" setting of attemptSoftSymmetry to turn off soft symmetry. Values between 0 and 1 are allowed, where the number represents the proportion of voxels. The default value is 0.6.

The default settings can be changed with the following commands:

configuration.equivalenceDelta = 1e5e-12

configuration.attemptSoftSymmetry = dynamic

configuration.softSymmetryThreshold = 0.36

Manufacturing Method: AM - Support Reduction - Overhang Angle

...

By default the first 10 eigenmodes are considered to an upper frequency limit of 3 times the frequency target. This can be modified with the following commands:

event.Event_2.frequencyMax=4500

event.Event_2.frequencyCount=10

If the Frequency Constraint is higher than the first calculated Eigenfrequency of the whole Design Space in the first Iteration, this can lead to the case that no material will be reduced. This can be resolved by reducing the Frequency Constraint or by entering the following command to the Advanced User Settings:

schedule.iterations.~.operator.optloop_loop_analysis_Event-2_extractLocalFailures.useMetricGoalFactor=1

It has been found that comparable heavy point masses can cause that the optimisation does not achieve the Frequency Constraint. To address this the impact value can be set up to a value greater than 1. This can be done with the following Advanced User Settings command:

event.Event_2.impact=1.5

Info

Event_2 has to be replaced with the name of the frequency event.

...