Hey, I read some of the previous posts but still kind of confused on how to extract values from a single node. Obviously this does not work: *FILE FORMAT, ASCII *NODE FILE, nset=ptest S, POR, COORD because the S,POR,COORD require element sets.. The problem is that my model is very complex and I do not know how to define the element set that immediately interacts with the single node coordinate I'm interested in. How would one go about this, and what would the .inp file look like.. something like this... *FILE FORMAT, ASCII *EL FILE, POSITION=AVERAGED AT NODES S, POR, COORD But how to define just a single node based on the elements near it?

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.

Hello. I wanted to "warn" that the files generated from A2M do not include underscores, as occurs with the initial input. Ex: initial input file: 'ShellTieScript_SS35m_Elastic_NoDiaphragm'; A2M input file: 'ShellTieScriptSS35mElasticNoDiaphragm_A2M'. There also seems to be some issue with the element and node set names when they include spaces. Ex: set name: "cross section edges" set name according to A2M "crosssectionedges" Not sure if it's on purpose or not, but just wanted to let you know