Code specific implementation questions? #32
Agent6-6-6
started this conversation in
General
Replies: 2 comments 11 replies
-
Actually on the tensile strength, I think it would work as you have it as it is only used for the cracking moment upon further investigation. For moment curvature you're inputting a specific stress/strain curve that could capture the ULS cracking behaviour. |
Beta Was this translation helpful? Give feedback.
11 replies
-
Agreed, I don’t think it makes sense to have it actually be a separate package. I like the idea that, when you install concreteproperties, it comes with some design codes!
…Sent from my iPhone
On Aug 29, 2022, at 00:12, Agent6-6-6 ***@***.***> wrote:
Regarding #31, yeah I agree with the requirement to show the M/N diagrams at a constant load angle if that's what you're specifically referring to, I was just seeing how the conversation would pan out.
A constant load angle is really what I'd expect to be returned for design purposes. I don't think it really will have any bearing on specific design code classes, as you're just calling the methods to display the M/N or Mx/My interaction diagrams from a design code. But generally a true vertical slice through the 3D surface would be considered the normal way of displaying and interpreting the results, pretty sure commercial packages do this (SPColumn for example).
a very convincing argument, I'm now in favour of placing SteelBarNZ in design_code.py.
For now I've put it as a subclass within NZS3101 class, i.e. NZS3101.SteelBarNZ(), my thinking is then it stays with the particular design code class, and ultimately I'd imagine you might want to break any implemented codes into their own file and leave the base DesignCode class in it's own file, throw all the actual design codes into a subfolder. In that way it's about as separate as you can make it without breaking it out into a different package (which I'm not really in favour of from a usability/maintenance perspective).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@robbievanleeuwen
In working through what would be required to implement a NZS3101 design code option, there are a few things I'd like to raise/discuss to get some agreement on the best approach. In many cases it will probably also be relevant to implementing other similar codes which are quite different to the AS300 approach:-
alpha_squash
which is stored as part of the concrete material is really more specific only to a AS3600 code implementation of the interaction diagram, so I wonder if that should just be a variable existing under the AS3600 design code class? Most other codes I'm familiar with work off the max compression route cutting off the interaction diagram at themax_comp
axial load (ACI/NZS/EC2, etc).flexural_tensile_strength
values, making the serviceability one optional and if not provided by user then is is just set to be equal to the ultimate value. Other specific functions utilising the current variable would need to be updated to refer to the ultimate or serviceability variable depending on the particular use (whether ULS or SLS analysis or parameters being calculated).NZS3101(density = 2300, pphr_class = 'LDPR')
?Beta Was this translation helpful? Give feedback.
All reactions