Dear George,
I have used A2M to read the nodal displacements of the fil file, as well as the nodal coordinates. As an example the first line of the U matrix is: 1.0000e+00 8.6664e-04 -4.1478e-05 -8.7155e-03 -3.2920e-04 1.6268e-07 -6.6415e-10 and of the COORD matrix: 1.0000e+00 -8.5265e-14 3.0800e+00 -1.5800e-01 If I do a probe value for the node with label 1 in ABAQUS GUI, it renders: Node: CROSSSECTION-1.1
1 2 3 Magnitude
Base coordinates: -8.52651e-14, 3.08000e+00, -1.58000e-01, -
Scale: 1.00000e+02, 1.00000e+02, 1.00000e+02, -
Deformed coordinates (unscaled): 1.73329e-03, 3.07992e+00, -1.75431e-01, -
Deformed coordinates (scaled): 1.73329e-01, 3.07170e+00, -1.90110e+00, -
Displacement (unscaled): 1.73329e-03, -8.29570e-05, -1.74310e-02, 1.75172e-02 Apparently the node identification is correct (same base coordinates), but the displacement components are not.. any idea? It is important to note that for some reason the INP file could not have COORD, U in the same line so i divided them as you said in a previous post: *NODE FILE
COORD
*NODE FILE
U
At first glance, it seems that SSAVG comparison is suffering from similar issues.
Dear Luis,
The output values that you sent me are not enough to figure out what may be happening with the Abaqus model.
Could you send me a version of your Abaqus model so that I can reproduce the error and fix the issue? Confidentiality in the various files and/or models shared with the Abaqus2Matlab work team is explicitly declared.
The issue with U and COORD not being at the same data line is simply a syntax convention of the Abaqus input files and is not related to the numerical results of an Abaqus analysis.
Best regards