Skip to content
This repository was archived by the owner on Apr 23, 2025. It is now read-only.

11783 concrete design addon#86

Merged
jarabroz merged 32 commits intomainfrom
11783-Concrete_design_addon
Aug 18, 2023
Merged

11783 concrete design addon#86
jarabroz merged 32 commits intomainfrom
11783-Concrete_design_addon

Conversation

@david-liska
Copy link
Copy Markdown
Contributor

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Unit Tests
  • Attached examples
  • Own example attached to Pull Request

Test Configuration:

  • RFEM / RSTAB / RSECTION version:

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Comment thread includes/GuideObjects/CoordinateSystem.js Outdated
Comment thread includes/BasicObjects/Surface.js Outdated
Comment thread includes/BasicObjects/Surface.js Outdated
reinforcementDirection.SetDirectionRotations(Math.PI / 4, Math.PI / 2);

/**************************************************** Types for concrete design - Surface reinforcement ****************************************************/
var reinforcementMaterial = new Material(undefined, "Grade 40");
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Grade 40 is not EC material for reinforcement - use switch based on Code standard

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It seems you fixed it?

run("../includes/Tools/clearAll.js");

var material = new Material(undefined, "C12/15");
var section = new Section(undefined, "IPE 80", material.GetNo());
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

? It needs to be a concrete beam

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It seems you fixed it?

Comment thread examples/high_level_functions_demos/addon_concrete_design.js Outdated
Comment thread examples/high_level_functions_demos/addon_concrete_design.js Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It could be better to split file into several files - each demo for standard. Then we do not need to deal with switches and selections of standard.
It could be easier also for Automated testing.

Copy link
Copy Markdown
Contributor Author

@david-liska david-liska Jul 7, 2023

Choose a reason for hiding this comment

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

Steel design is based on this idea too and finished AT is design with this way (there is only problem with time, for one test slightly exceeds 1 minute - concrete design example has less standards). We can discuss about it.

Comment thread includes/AddOns/TypesForConcreteDesign/SurfaceReinforcement.js Outdated
Comment thread includes/AddOns/TypesForConcreteDesign/SurfaceReinforcement.js Outdated
Comment thread includes/AddOns/ConcreteDesign/ConcreteDesignSupport.js Outdated
@@ -0,0 +1,34 @@
/*
NO API support?
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Why?

@@ -0,0 +1,34 @@
/*
NO API support?
*/
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

If there is not support in JS and perhaps released why to create this?

Comment thread includes/AddOns/ConcreteDesign/UltimateConfigurationNTC.js Outdated
Comment thread includes/AddOns/ConcreteDesign/UltimateConfigurationEN.js Outdated
@pull-request-quantifier-deprecated
Copy link
Copy Markdown

This PR has 5541 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Large
Size       : +5473 -68
Percentile : 100%

Total files changed: 23

Change summary by file extension:
.ps1 : +1 -1
.js : +5466 -67
.xml : +6 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@jarabroz jarabroz self-requested a review August 18, 2023 09:06
@jarabroz jarabroz merged commit f1b4ebe into main Aug 18, 2023
@jarabroz jarabroz deleted the 11783-Concrete_design_addon branch August 18, 2023 09:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants