Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations waross on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

NFORC difference between scripting and GUI

Status
Not open for further replies.

Rasoul63

Mechanical
Dec 16, 2014
1
Hello,

This question was asked before by deyentl but nobody answered it. Now I have the same problem. I'd really appreciate it if you could give me an idea that what;s the reason.
I copied the question here:

Hello everybody,

I'm trying to calculate the nodal forces in a very simple model with only 8 elements. I have two approaches, and I would expect both to be equivalent, but they aren't. The first method uses the GUI to plot the NFORC1 field output and then goes to Tools > Query > Probe Values. The second model uses scripting by the following command:

nodal_forces = myodb.steps['Step-1'].frames[-1].fieldOutputs['NFORC1']
node = odb.rootAssembly.instances[InstanceName].nodes[5] #Or any other number
nodal_forces.getSubset(region = node).values[0].data

To make the case even stronger, the value reported by the GUI is not found at any node through scripting. Therefore, it cannot be related to using the wrong index or anything like that.

Do you have any idea what may be causing this remarkable contradiction between GUI and scripting?

Best regards
deyentl
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor