-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Labels
bugSomething isn't workingSomething isn't working
Description
The COM server does not return the critical support forces correctly, when IAxisVMForces.CriticalNodalSupportForce or IAxisVMForces.CriticalNodalSupportForce2 is called.
A minimal code snippet to reproduce the problem. provided that an AxisVM is running and it was started with the /MULTIINSTANCECOMCLIENTS argument
from axisvm.com.client import start_AxisVM
from axisvm.com.axapp import IAxisVMApplication
from axisvm.com.axmodel import IAxisVMModel
from axisvm.examples.downloads import download_bernoulli_grid
import axisvm.com.tlb as axtlb
axapp: IAxisVMApplication = start_AxisVM(visible=True, join=True, daemon=False)
axapp.model = download_bernoulli_grid()
axmodel: IAxisVMModel = axapp.model
axforces = axmodel.Results.Forces
axforces.AnalysisType = axtlb.atLinearStatic
axforces.LoadLevelOrModeShapeOrTimeStep = 1
axforces.CombinationType = axtlb.ctAuto
axforces.Component=axtlb.nsfRz
axforces.MinMaxType=axtlb.mtMin
record = axforces.CriticalNodalSupportForce(NodalSupportId=5)[0]
Rz_min = record.Rz # this value is wrongAccording to the model, the value of Rz_min should be -72.018.
Another interesting phenomenon is that the API returns a smaller value for axtlb.mtMax than for axtlb.mtMin.
This is the node in the model:

I have tried to get the correct value with all possible combination types, other than axtlb.ctAuto, but none of them yields the correct value.
System details:
- Windows 11 (64 bit)
- Python 3.10.9
- AxisVM version: X7 R2b-qf3
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working