Skip to content
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

MidasCivil_Toolkit: Capturing when an absolute value for distance has been used #76

Open
peterjamesnugent opened this issue Mar 22, 2019 · 0 comments
Labels
severity:low Doesn't stop/slow current workflow size:S Measured in minutes type:documentation Wiki, help or in code attributes

Comments

@peterjamesnugent
Copy link
Member

The string used to define a beam load does not change whether the distance from A/B is entered as a parameter or absolutely. This is something we should make abundantly clear in the Wiki.

For example, with an element of 1m or less, it would be impossible to tell if the distance is parametric or absolute.

@peterjamesnugent peterjamesnugent added severity:low Doesn't stop/slow current workflow size:S Measured in minutes type:bug Error or unexpected behaviour labels Mar 22, 2019
@peterjamesnugent peterjamesnugent added this to the BHoM 2.4 MVP milestone Mar 22, 2019
@peterjamesnugent peterjamesnugent added type:documentation Wiki, help or in code attributes and removed type:bug Error or unexpected behaviour labels Mar 26, 2019
@peterjamesnugent peterjamesnugent removed this from the BHoM 2.4 MVP milestone Jun 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity:low Doesn't stop/slow current workflow size:S Measured in minutes type:documentation Wiki, help or in code attributes
Projects
None yet
Development

No branches or pull requests

1 participant