Skip to main content
Aug 18, 2023 5:07 AM UTC
Acknowledged

Allow post processing of Simulate results

Related products:Creo Parametric

It would save a lot of rerunning of simulations if you could add measures and recalculate their value from an already run simulation.

I would also be useful to be able to query results at a specific node or location.

5 replies

Aug 18, 2023 6:04 AM UTC
Status changed to: Clarification Needed

Hi @NL_10254580!


Thank you for publishing your idea.


However, you give the bare minimum of information. The more details and context you give to document your idea, the better. Think about ways to educate and convince other Community members to support your idea and present your case to the product management team for consideration.

Here are a few examples of well documented ideas:

Make Shrinkwrap quality more scalable to data size... - PTC Community

Improve/fix the sheetmetal mirror feature - PTC Community

[Eztol] Rename action not synchronous in Eztol - PTC Community


Please elaborate within the next two weeks.

Additionally, I invite you to check out this topic where PTC executives explain product managers' approach to customer ideas and input for product roadmaps.

Aug 28, 2023 11:30 PM UTC

I really, see the value in this feature so I'll comment for NL_102...
1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.

Amusement ride design for a medium size international company

I am currently undertaking stress analysis on the structures which support track/cable paths for vehicles to traverse.

I have to deliver calculation sets which are responsible for life critical applications to project leads, and ultimately, to our international manufacturer.

2. What version of Creo Parametric are you currently running?

7&8

3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.

I would like to be able to generate measures after a simulation is run and apply functions to the calculated stresses/strains to create custom outputs.

 

As an example usage case: in order to conduct a hot spot stress analysis (using most reputable methods e.g. Eurocode or  FKM guideline) you must first identify a highly stressed area of the model. Once found, stresses at this location are extracted from the FEA model and run through a series of calculations which advise whether the reported stresses are within acceptable limits for the assessed geometry.

This process may require:
- Using a either von Mises stress, normal stress components, or a weighted average of the two, depending on the ductility of the material.

- Calculation of stress gradients surrounding the area of examination (often normal to the surface of the part)

- Determination of the total load passed through an area

 

 Some of these items are possible with the current tools, others are not:

- It is possible to identify the area of highest stress for either VMS or normal stress, it is not possible to identify the area of highest stress based on a weighted average of VMS and normal stresses. The data is generated for both - all that is required is the option to apply a custom function to the calculated stresses/strains before displaying it on screen (we actually have a python script which can do this, so I know it is possible, but this is clunky go between which others do not have access to)

 

- It is not possible to set up measures to extract stresses at the highly stressed area before running a simulation as you cannot determine where the highly stressed area is before the simulation is run. This means it is not possible to easily extract these stresses without re-running a simulation, which if we are running a fully converged model, can take several hours.

It is possible to calculate stress gradients near a point of examination by using the simulate results cross section tool, and then using a dynamic query, however this interface is very clunky when trying to be precise and is not able to be permanently captured within the model (as it disappears as soon as you exit dynamic query).

It would be much easier to extract this information if a measure could be set up using geometry after the simulation has been run

E.g. in simulate results define a datum point in the model and then apply a measure of stress at this point – or even at the very least, extract stresses at the existing nodes which could then be interpolated in an external calculation.

 

- It is possible to determine the total load through a surface IF YOU REMEMBERED TO DEFINE THE MEASURE BEFORE RUNNING THE SIMULATION. If you forget to set up your measures beforehand you are faced with the only option of re-running the entire study.

I know these ideas are possible as we have implemented them ourselves using our python post processor. Once a simulation is run, all the required information has been generated, but there is no means in simulate results to extract it if you didn’t set up the measures prior.

 

This functionality is available in Ansys and we are moving from using Creo simulate to Ansys more and more due to these limitations. This requires additional licensing and switching between programmes which is undesirable and significantly reduces the usefulness of Creo.

Aug 28, 2023 11:39 PM UTC

Thanks for your comment Andy, I would like to add that some of our contact simulations take over 20 hours to complete so rerunning is not a trivial task. Therefore, enabling the ability to add points, curves, and other features post-simulation and then report stress and displacement at/along the specified features would save valuable time.

For less complicated simulations the ability to add measures you forgot or correct measures that may have been created incorrectly (eg. contact forces, constraint reactions, spring loads, etc.) after the simulation has run and evaluate them without rerunning would be a widely used time saving.

Aug 29, 2023 6:24 AM UTC
Status changed to: Acknowledged

Hi @NL_10254580!

 Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

Nov 6, 2024 5:04 PM UTC

Required functionality.