How to Read Corner Stress Data through Compose？

yuankun hu

Hello everybody,

          Previously, we were unable to obtain the results of querying corner stress through Compose，but only the stress of the centroid using commands such as readcae, readvector or readmultvectors.

          I currently found a readcae3d instruction in the help document of the 2022 version of the compose , which describes the ability to extract corner stress data.

             To verify whether this command can extract corner stress data, I established a simple model(shell 2D), where a cantilever beam is subjected to a force at the end,。

         Q1:         I read the stress of the unit in the h3d file through the readcae3d statement, but the error request is invalid. This unit number does exist, I don't know which one went wrong.（But for another simple model, I successfully extracted corner stress）

         Q2:         I read the average Corner stress at nodes in the H3D file using the readcae3d statement and found that the extracted node Corner stress does not match the Corner stress of the same node I queried in Hyperview. The difference between the two is significant. May I ask what is the reason?  

       Q3:           I want to use the readcae3d statement to read the average Corner stress at the nodes in the h3d file (in the local coordinate system), and view the help document. Three coordinate systems can be selected . Which one should I choose is the local coordinate system, and what does the 'elemental' coordinate system option mean?

        The hm model, oml file, and h3d file are all in a compressed package. Please discuss how to solve this problem together。

Thanks you very much in advance,

Best regards,

yuankun

João Marabisa

Hi, yuankun!

For the different available options, please refer to HyperView help. The standard HyperView profile sometimes uses by default different options to the readcae3D in Compose! When it happens (rarely) you can use another HyperView profile to check:

Using it, and adapting your script to read the N8 result after applying Corner Data, Averaging Method, and the result from Compose is the same from HyperView:

João Marabisa

Hi, yuankun!

For the different available options, please refer to HyperView help. The standard HyperView profile sometimes uses by default different options to the readcae3D in Compose! When it happens (rarely) you can use another HyperView profile to check:

Using it, and adapting your script to read the N8 result after applying Corner Data, Averaging Method, and the result from Compose is the same from HyperView:

yuankun hu

João Marabisa said:

Hi, yuankun!

For the different available options, please refer to HyperView help. The standard HyperView profile sometimes uses by default different options to the readcae3D in Compose! When it happens (rarely) you can use another HyperView profile to check:

Using it, and adapting your script to read the N8 result after applying Corner Data, Averaging Method, and the result from Compose is the same from HyperView:

First, thank you for your prompt reply！！！

I used the OML script you uploaded to extract corner stress, but an error occurred. The data in the corner data is incorrect. I checked the help document and the keyword here is true. When I make modifications, I can correctly extract corner stress data. My composite version is 2022.1. What is your version of Compose, and why is the correct keyword is 'only' for extracting corner data？

The average corner stress at node 8 extracted by the OML script is 513.2MPa，The average corner stress at node 8 extracted through the Hyperview version is 565.9MPa, which is the same as the value you extracted. Is it the reason why our composite version is different?

 

Thanks you very much in advance,

Best regards,

yuankun

yuankun hu

João Marabisa said:

Hi, yuankun!

For the different available options, please refer to HyperView help. The standard HyperView profile sometimes uses by default different options to the readcae3D in Compose! When it happens (rarely) you can use another HyperView profile to check:

Using it, and adapting your script to read the N8 result after applying Corner Data, Averaging Method, and the result from Compose is the same from HyperView:

Thank you very much for your timely reply !!!

I have updated my compose version, starting from 2022.1 and now it is 2022.3.Looking at the latest 2022.3 version of the help document, I found the keyword 'only' for corner data.

(Value 'only' behaves similar to the Use corner data selection in HyperView).

Well, it may be the latest version that completely solves the problem of extracting corner stress data and the consistency with the corner stress data extracted in Hyperview.

 

João Marabisa

yuankun hu said:

Thank you very much for your timely reply !!!

I have updated my compose version, starting from 2022.1 and now it is 2022.3.Looking at the latest 2022.3 version of the help document, I found the keyword 'only' for corner data.

(Value 'only' behaves similar to the Use corner data selection in HyperView).

Well, it may be the latest version that completely solves the problem of extracting corner stress data and the consistency with the corner stress data extracted in Hyperview.

 

Hi yuankun,

I'm using 2022.3 - Glad it worked!