About Large Deformation Analysis

Hi everyone,

In the Large Deformation analysis of a cantilever beam, I am unable to use Node force, Beam forces, Beam Displacement, Deformation Energy, Node displacement, and React forces.
The error message is "1. Model of iteration #0: There are no calculated results available for the model. Did you forget to calculate the model?”
Is there a solution to this issue?

I am using Rhino 8 with Karamba3D 3.14 Core and Pro license.
Additionally, these functions worked correctly in the infinite deformation (Analyze component) analysis.

Thanks

Hi, the Large Deformation does not output any results, it simply does the form finding procedure, you will need to analyse the model to get the results afterwards.

Dear @matttam,

Thanks! I solved that problem by connecting the analysis component after the large deformation.
However, if the number of polyline segments exceeds a certain number, the error message “Input plug ‘Pos|Ind’: Could not find node at {~, ~, ~}” appears in the Nodal Forces component and "The position is outside the valid domain: {~; ~} (Parameter ‘position’))” occurs in the Model View component.
I think it is a tolerance (limit distance) issue, but nothing has changed. How can this be solved?

Best,

you will probably need to input the new or moved point to be able to locate this, because the original point no longer exists in the model.

I found that the moving points are obtained in the DefModel of ModelView, then I connected the patch like LaDeform → Analyse → ModelView --(DefModel)–>Disassemble --(Model & Pt)–> N-Forces. However I can’t find any node other than the support point. Is there something wrong with the input Model in N-Forces?

Hi, can you share your script so that we can take a look at it

Hi, This is the script. The red zone is about N-Force.
BeamLargeDeformation.gh (45.4 KB)

Dear @matttam ,
After making various changes, I found that if I connect the N-Force’s input “Model” to the Model-View’s output “Model” instead of “DefModel”, some nodes are found. However, there are more nodes that are not found.
Best,

Dear @HIbikiTotsuka,
thanks for your bug report.
I could find and fix the problem. It will be part of the next service release.
– Clemens

1 Like