-
Notifications
You must be signed in to change notification settings - Fork 46
feat: MC2020 14.6.1-Material properties of concrete #155
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
base: dev
Are you sure you want to change the base?
feat: MC2020 14.6.1-Material properties of concrete #155
Conversation
Co-authored-by: talledodiego <[email protected]>
…codes into ec_2004_crack_control
| return 0.20 | ||
|
|
||
|
|
||
| def sigma_c( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function should be considered removed in favour of one of our builtin constitutive laws. @talledodiego can you advice on this?
|
|
||
| # Dictionary for normal concrete grades and | ||
| # their respective fck and fck,cube values | ||
| _concrete_strengths = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a clever solution when the data is given in a table in the code, but it might be a short-coming when we start implementing methods on the material level, and the characteristic cylinder strength is the expected input and not the strength class. @talledodiego any thoughts on this?
|
|
||
|
|
||
| # Dictionary for concrete properties based on grade | ||
| concrete_properties = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above, @talledodiego, any thoughts?
mortenengen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What a massive PR @DanielGMorenaFhecor! Thanks for the contribution 💪
I have merged dev, fixed docstrings, added the functions to the API docs, left a couple of comments, and asked @talledodiego for a review of compliance with the design code.
| @@ -0,0 +1,1363 @@ | |||
| """Tests for fib MC2020 Chapter 14.6.1.""" | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are several lines that are not covered by tests. Can you please add tests to reach 100% coverage of the contribution?
Please, find here all the code implementations for the following specified chapters:
The code is already up to review 👍