Skip to content

Rethink beam materials in core and 4C #452

@isteinbrecher

Description

@isteinbrecher

Thanks again for the new functionality, I really enjoy using the get_four_c_beam function - it makes it so easy to quickly switch the entire discretization without importing anything else!

#430 (comment) it would be nice if we can also do this for materials and not just for the beams. Currently, if one switches between beam types, e.g., Kirchhoff, Reissner, ... one has to switch the Material (with imports) as well. So it would be nice to have a similar functionality.

Alternatively, we can also rethink how beam materials are handled in FourC. A few things that come to mind:

  • Maybe it makes sense to generally unify this and not have individual classes for different types. How does this work if I have different beam types referencing the same material?
  • Add a basic support for different cross-section types, e.g., circle, rectangle, ... that can then also be customised and extended by the user.

Refactoring the material has been on my mind for a long time, so let's use this issue to gather thoughts and see if and how we can do this.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions