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

RAM_Toolkit: Beams Not Supported Error For Cantilevers #15

Closed
enarhi opened this issue Jul 5, 2018 · 3 comments · Fixed by #92
Closed

RAM_Toolkit: Beams Not Supported Error For Cantilevers #15

enarhi opened this issue Jul 5, 2018 · 3 comments · Fixed by #92
Assignees
Labels
severity:medium Slows progress, but workaround is possible type:feature New capability or enhancement

Comments

@enarhi
Copy link
Member

enarhi commented Jul 5, 2018

RAM DataCheck throws warnings for unsupported beams due to api only bringing in beam geometry with no supports at ends where columns do not occur.

@ncbrown2
Copy link
Contributor

Regarding comment on #40 , through the ILayoutBeam interface we can get/set dEndCantilever for a beam, as well as directly get and set StubCantileverCoordinates. Should cantilever lengths be stored as custom data for the bar, or interpreted and used to automatically adjust the lengths of beams when going from RAM to BHoM?

I think cantilever object creation (BHoM to RAM) will be more complicated, since in RAM a user has to define a beam first, and then add either a stub cantilever or extension second, and we don't have a good way of dealing with this in our Create Bar components...does this sound correct?

@enarhi
Copy link
Member Author

enarhi commented Sep 25, 2018

Sounds correct on all counts. Creating RAM cantilevers will be an essential feature so we will have to figure out how to manage it.

@al-fisher al-fisher added severity:low Doesn't stop/slow current workflow type:feature New capability or enhancement and removed feature_minor labels Mar 20, 2019
@enarhi enarhi added severity:medium Slows progress, but workaround is possible and removed severity:low Doesn't stop/slow current workflow labels Apr 17, 2019
@enarhi enarhi added this to the BHoM 2.4 β MVP milestone Aug 19, 2019
@enarhi
Copy link
Member Author

enarhi commented Aug 20, 2019

This will be managed by adding data for isCantilever and cantilever distances to the bar, and then using this data to create the bar accordingly. This requires a step of adding cantilever information to bars that can be handled in Revit params, gh, etc. Samples will need to clearly show how to handle this to ease usage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity:medium Slows progress, but workaround is possible type:feature New capability or enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants