Closed SerGlushko closed 3 years ago
I think there is problem with transformation calculations I'll check this week and fix the issue. Thanks
Hi This works fine now. this is the result of your code I did not changed the code.
Hello, I've downloaded the latest version of the library, results remain the same for me
Could you please also check with model.Solve_MPC()
instead of model.Solve()
?
I've coppied your code into this file:
https://github.com/BriefFiniteElementNet/BriefFiniteElement.Net/blob/7ab78543b48b2f50fd1942dba29f686033e5dd3e/BriefFiniteElementNet.Validation/GithubIssues/Issue96.cs#L10
If you set BriefFiniteElementNet.TestConsole.csproj
as startup project, it will call
Could you please check?
I've tested Solve_MPC method, it returns NaN. Same for the project in the TestConsole
Here's the matrix:
There was problem with bar transformation which is fixed. Could you please do check again? Thanks
The example works correctly now, but I've tried the latest version in my main project that uses some legacy code too. The issue is still there for FrameElement2Node elements
it should be fixed, could you please do check again?
It works for FrameElement2Node now too. Thank you!
Describe the bug Greetings! First of all, thank you for your continued development and support of this fantastic library. I've been using BFE.NET version from autumn 2019 in my project and decided to migrate to the newest build. I have encountered an issue: any 2D frame or truss I create have NaN values of support reactions, internal forces and deformations for the vertical elements, e.g BarElement (0, 0, 0), (0, 0, 1). This issue might also effect FrameElement2Node elements.
To Reproduce This is the code We've used and caused wrong result/ runtime error
Expected behavior The expected result for n0 is "F: 0, 0, 4000, M: 0, 0, 0"
Additional context
I've tested multiple frame configurations and ones without strictly vertical elements had correct results.