Versions Compared

Key

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

...

Adjust your model set up so that every Event has fixations in all three main directions (or local coordinate systems main direction) included.

E7f716c48

This Error is only produced after another Error was encountered. The optimisation algorithm tried to continue despite the previous Error but could not continue. The optimisation fails with this Error although the primary Error is the reason for the terminated optimisation.

E4ebe0a20

Projected memory requirement exceeds available memory - complexity … (detail …) is too high. Theoretical limit: complexity … (detail …), recommended: complexity … (detail …)

The chosen complexity value is too high to be calculated on this machine. A certain maximum complexity value is recommended. Have a look here.

Eb20f3415

boundary condition is missing elements

A Non-Design Space was removed and the applied boundary conditions are not considered

The Design Space has lost the connection to the force/constraint application point. The model is no longer complete and it doesn’t make sense to continue with the optimisation.

Make sure that the Keep Non Design function is activated. Increase the Complexity or increase the Safety Factor.

Eb20f3980

Missing config entry …

The configuration file is missing an entry or command. Please check your entries in the Advanced User Settings or if you are using the Command Line Optimisation please check the Configuration File. You can find all commands for the Advanced User Settings here and the Configuration File here.

E0d03bf38

Unable to resolve input file name statistics.csv

This may occur if an optimisation is started with Advanced User Settings with which only 1 or 2 iterations should be calculated. If this is the case please add the following Advanced User Settings commands:

...

schedule.level.3.subiterations.~.outputMode.OutputGeneratedSurface

E39d2c328

unexpected error loading file statistics.csv: Unable to open input file

This may occur if an optimisation is started with Advanced User Settings with which only 1 or 2 iterations should be calculated. How to resolve this here.

...

schedule.level.3.subiterations.~.outputMode.OutputGeneratedSurface

E58799450

unexpected error writing file file_name.ply:

One of the result files cannot be written. This can happen while using parallelization (default). This can be resolved by adding following Advanced User Settings commands:

...

process.workers = 1

E724493a8

Unable to open file … for writing

There are no privileges to access a file which is needed. Please check where the project folder is placed in which all the results are written. Network drives and cloud storage (e.g. OneDrive) are not recommended.

E3ee97ff0

supportReductionIntensity … is out of bounds 0-10.

Please adjust the Intensity value of the Support Reduction according to the boundaries.

E449a19a0

invalid supportReductionMode … expected off, passive, reactive or active.

Please set the Support Reduction Mode to one of the supported modes.

E4a364e88

missing / incompatible strutDensity setting for use with support avoidance.

If you are using the Support Reduction, you need to define a Strut Density.

W6e184ce8

Permanently shutting down soft symmetry because all dimensions have become unsalvagably asymmetric.

Eb20f33c1

LicenseConstraintException    failed to acquire … count … instances of … feature.

A license for the GD Engine and/or the GPU calculation couldn’t be acquiered. Please check your licenses.

E0850d340

Attempted to write a checkpoint on unpaused job.

Restart file could not be written at this point in the optimisation. Please have a look at the prior error code which shows the primary reason for the failed optimisation.

E16808658

Legacy config format is disabled.

Please export the Scenario again (version 2022.1 or newer) to generate the supported json file format.

W1a123238

Symmetry coordinate systems are deprecated and will be removed in 2022.4 release. Use configuration.principalCoordinateSystem instead.

This can only happen when the configuration file was manually adjusted and a command line optimisation executed. The symmetry coordinate system has been replaced by a general principal coordinate system. Have a look at the Configuration File page for further information.

E18f03ac8

Given symmetry coordinate system and principal coordinate system conflict.

This can only happen when the configuration file was manually adjusted and a command line optimisation executed. The symmetry coordinate system has been replaced by a general principal coordinate system. Have a look at the Configuration File page for further information.

W2cc566c0

Fixed … reshaping error(s) - boundary violations … threshold exceeded …

Information message that the algorithm corrected some errors in the file. The optimisation continues as before.

E79aa1a40

Fractured design space - make sure the model consists of only a single, connected body.

Occurs mainly if no Interface is placed between Design Space and Retained Volume.

W31ac7fa8

Supervoxel downsampling caused … material collision(s)

...

W17b312a1

Nastran file … at … corrupted. Trying to rerun nastran

For eigenfrequency optimisations MSC Nastran is called in the background. In this case the .h5 is defect. Make sure the correct path to MSC Nastran is defined in the application settings (path to nastXXXX.exe)

W17b312a2

Nastran file … h5 not found in … Trying to rerun nastran

For eigenfrequency optimisations MSC Nastran is called in the background. In this case the .h5 couldn’t be found. Make sure the correct path to MSC Nastran is defined in the application settings (path to nastXXXX.exe)

W1ee5aa1b

First frequency … Hz is significantly below frequency constraint… Hz

The first calculated eigenfrequency of the full Design Space is lower than the chosen frequency constraint. The optimisation logic isn’t able to reduce material in this case. There is a workaround on the frequency help page.

W26473bd0

Detail specified together with either complexity or resolution - using detail for optimization

Detail and Complexity are both set. Detail is used.

W312309f8

error computing new UFI for …. voxels

Please contact MSC Apex Support.

W3203a74e

unable to remove file …

Access to a specific file was denied. The file couldn’t be deleted.

W4fb68977

symmetry not supported with frequency conditions

The hard symmetry isn’t supported for eigenfrequency optimisations.

W5b09c551

condition-based frequency-analysis event … must have at least one condition

At least one displacement constraint / fixation is needed for a eigenfrequency optimisation.

W6b26eae6

frequency failures cannot be extracted without input frequencies

MSC Nastran hasn’t found any eigenfrequencies in the given range. The optimisation continues. The first calculated eigenfrequency is much higher than the entered Frequency Constraint.

W757e1585

Could not load Nastran result for nastran frequency event. Reason …. Proceeding as if empty

MSC Nastran hasn’t found any eigenfrequencies in the given range. The optimisation continues. The first calculated eigenfrequency is much higher than the entered Frequency Constraint.

We8be37f1

Smoothing failed, mesh was not changed

The smoothing algorithm failed for this iteration. The optimisation continues.

E7f716c48

This Error is only produced after another Error was encountered. The optimisation algorithm tried to continue despite the previous Error but could not continue. The optimisation fails with this Error although the primary Error is the reason for the terminated optimisation.

E4ebe0a20

Projected memory requirement exceeds available memory - complexity … (detail …) is too high. Theoretical limit: complexity … (detail …), recommended: complexity … (detail …)

The chosen complexity value is too high to be calculated on this machine. A certain maximum complexity value is recommended. Have a look here.

Eb20f3415

boundary condition is missing elements

A Non-Design Space was removed and the applied boundary conditions are not considered

The Design Space has lost the connection to the force/constraint application point. The model is no longer complete and it doesn’t make sense to continue with the optimisation.

Make sure that the Keep Non Design function is activated. Increase the Complexity or increase the Safety Factor.

Eb20f3980

Missing config entry …

The configuration file is missing an entry or command. Please check your entries in the Advanced User Settings or if you are using the Command Line Optimisation please check the Configuration File. You can find all commands for the Advanced User Settings here and the Configuration File here.

E58799450

unexpected error writing file file_name.ply:

One of the result files cannot be written. This can happen while using parallelization (default). This can be resolved by adding following Advanced User Settings commands:

process.workers = 1

E724493a8

Unable to open file … for writing

There are no privileges to access a file which is needed. Please check where the project folder is placed in which all the results are written. Network drives and cloud storage (e.g. OneDrive) are not recommended.

E3ee97ff0

supportReductionIntensity … is out of bounds 0-10.

Please adjust the Intensity value of the Support Reduction according to the boundaries.

E449a19a0

invalid supportReductionMode … expected off, passive, reactive or active.

Please set the Support Reduction Mode to one of the supported modes.

E4a364e88

missing / incompatible strutDensity setting for use with support avoidance.

If you are using the Support Reduction, you need to define a Strut Density.

W6e184ce8

Permanently shutting down soft symmetry because all dimensions have become unsalvagably asymmetric.

Eb20f33c1

LicenseConstraintException    failed to acquire … count … instances of … feature.

A license for the GD Engine and/or the GPU calculation couldn’t be acquiered. Please check your licenses.

E0850d340

Attempted to write a checkpoint on unpaused job.

Restart file could not be written at this point in the optimisation. Please have a look at the prior error code which shows the primary reason for the failed optimisation.

E16808658

Legacy config format is disabled.

Please export the Scenario again (version 2022.1 or newer) to generate the supported json file format.

W1a123238

Symmetry coordinate systems are deprecated and will be removed in 2022.4 release. Use configuration.principalCoordinateSystem instead.

This can only happen when the configuration file was manually adjusted and a command line optimisation executed. The symmetry coordinate system has been replaced by a general principal coordinate system. Have a look at the Configuration File page for further information.

E18f03ac8

Given symmetry coordinate system and principal coordinate system conflict.

This can only happen when the configuration file was manually adjusted and a command line optimisation executed. The symmetry coordinate system has been replaced by a general principal coordinate system. Have a look at the Configuration File page for further information.

W2cc566c0

Fixed … reshaping error(s) - boundary violations … threshold exceeded …

Information message that the algorithm corrected some errors in the file. The optimisation continues as before.

E79aa1a40

Fractured design space - make sure the model consists of only a single, connected body.

Occurs mainly if no Interface is placed between Design Space and Retained Volume.

E413ccf6b

point mass … refers to non-existing geometry …

Make sure the point mass refers to a geometry.

E72deb9d2

Using RBE2 point masses with linear-static analyses is not supported yet

RBE2 isn’t supported for static load cases / events yet. It is supported for frequency load cases / events.

E7d830f0a

Point masses without position are not supported yet

A point mass has to have a defined position.

E40a1d044

Nastran directory could not be created

Please contact the MSC support.

E56b33469

Unable to export Nastran model: Incompatible FEA setup

Please contact the MSC support.

E56b33470

Unable to export Nastran model: not enough data modes

Please contact the MSC support.

E61ad1352

NastranExport.h5 formatting error: Path << path << not found in nastran data sets

Please contact the MSC support.

E53eeff00

feature … is unavailable

Please contact the MSC support.

E2f8f1750

Nastran requires paths to not contain space characters under GNU/Linux

Please do not use space characters in paths under Linux.

Escalations

E45ca3ab0

W45ca3ab0

...