About Simulation Results Deletion

The results associated with a simulation object can be very large. This can affect performance and transfer time when exporting or sharing the generated 3D XML file over a network or when archiving. By deleting the simulation results, you can reduce the file size without compromising preprocessing or postprocessing specifications.

You can delete a simulation's experience content for a specific analysis case or for all cases at once. You can delete a simulation's experience content, the Knowledgeware parameters related to its sensors, or both:

Delete experience content

Otherwise known as "lightweight data," experience content is the subset of results data that apps like 3DPlay can use to browse the results of a simulation. You can delete a simulation's experience content to improve performance when you do not have immediate plans to share simulation data in 3DPlay.

Delete/invalidate sensor data

Knowledgeware parameters enable you to share sensor data with other apps. You can delete or invalidate this data for large sets of results or when sharing sensor data is not a priority.

Once you remove the results data from the simulation object, you can no longer access the data nor reassociate it with the simulation object. The simulation object retains all modeling and results specifications so that Knowledgeware parameters can be regenerated at the next solve or import of results. By default, the app deletes bulk data (simulation output) associated with the simulation but preserves experience content and sensors data.

Save the simulation for your changes to take effect. If you save the simulation object, the results, experience content, and sensor data are unavailable or invalidated (depending on your selections) until the simulation runs again. If you view the simulation in 3DPlay, no simulation data is available. Rerun the simulation to update Knowledgeware parameters and to recreate invalidated or deleted parameters. If you close the simulation without saving, the experience content and sensor data remain available on a subsequent open or import.