+
Skip to content

Fix cross-dyadic product: Ensure minor- and major-symmetric result #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
Jul 7, 2023

Conversation

adtzlr
Copy link
Owner

@adtzlr adtzlr commented Jul 6, 2023

Especially the first point was hard to detect because I've used the special case A = B in 99% of all applications where the implementation up to v1.1.2 works without any problems.

@adtzlr adtzlr added the bug label Jul 6, 2023
@adtzlr adtzlr added this to the 2.0.0 milestone Jul 6, 2023
@adtzlr adtzlr self-assigned this Jul 6, 2023
@adtzlr adtzlr requested a review from jfriedlein July 6, 2023 23:23
@adtzlr
Copy link
Owner Author

adtzlr commented Jul 6, 2023

@jfriedlein I did my best in fixing it with gfortran because currently I have no FEA code / Intel Fortran at hand to test the changes. Could you check if your models converge with these changes?

Many many thanks in advance 😄

Copy link
Collaborator

@jfriedlein jfriedlein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides the small typo with the date, it looks fine.

@adtzlr
Copy link
Owner Author

adtzlr commented Jul 7, 2023

Perfect! I checked the numeric results with my Python package adtzlr/hyperelastic but I couldn't test an actual UMAT / HYPELA2 / whatever subroutine inside a FEA package if something happened related to convergence.

@jfriedlein
Copy link
Collaborator

Hi @adtzlr,

I tested the "fix-crossdyadic" branch for LS-Dyna:

  • Ubuntu 20.04.6 LTS, gfortran GNU Fortran (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
  • Windows 10, Visual Studio 2017, ifort17
    For both it compiled fine. Also the tensor functions that I use, worked as perfect as before. (I noticed something that is unrelated to the current fix, so I added this as issue Initialisation of tensor components to zero #45).

For a more reliable and comprehensive test, we should think about unit tests. Probably that is a lot of work to set up, but once the framework is ready, it should be easy to add more and more tests and provide a quality assurance. Maybe a todo for the future.

@adtzlr
Copy link
Owner Author

adtzlr commented Jul 7, 2023

Yes, unit tests are indeed a great idea! Ideally would be an automated CI/CD pipeline with Github Actions. But my experience in Fortran ends with the scope of this package... I usually do some UMAT scripting but thats it.

@mholla
Copy link

mholla commented Jul 12, 2023

ah wow, very happy to hear that my document was helpful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants
点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载