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

ETABS_Toolkit: Implementation of GeneralisedTSectionProfile #214

Open
kThorsager opened this issue Oct 3, 2019 · 2 comments
Open

ETABS_Toolkit: Implementation of GeneralisedTSectionProfile #214

kThorsager opened this issue Oct 3, 2019 · 2 comments
Labels
severity:medium Slows progress, but workaround is possible type:feature New capability or enhancement

Comments

@kThorsager
Copy link
Contributor

Description:

Implementation of GeneralisedTSectionProfile
From the looks of it ETABS does not have any standard sections which can handle BHoM's GeneralisedTSectionProfile so it would have to be via the "Section Designer" in ETABS.

I could not find any proper method for assigning a section in the Section Designer via API but I did not look very hard...

If that is impossible it would at least be nice to get the data pushed in some manner (like, assigning a false section where the notes define how the section should be) so that it would be easier to both find the faulty section and find the real section properties to assign it

related to #213

@kThorsager kThorsager added severity:medium Slows progress, but workaround is possible type:feature New capability or enhancement labels Oct 3, 2019
@JosefTaylor
Copy link
Contributor

Correct, section designer is not yet in the API. Not sure how we're going to get that going.

If the section has already been defined in ETABS (using section designer) then a section with the same name will point to it.

Here are our choices for how to push unsupported bars to ETABS as I see them:

  1. Create an explicit section (general section in ETABS) and throw a reflection note
  2. Create a null section and throw a reflection warning
  3. Create a 1m diameter rod and throw a reflection warning
  4. Don't send the bar, throw a reflection error

@kThorsager
Copy link
Contributor Author

A note to that is that asymmetric sections (tex GeneralisedTSectionProfile) does not get its J calculated (at least in my case, got a reflection error1. Can only calculate torsional constant of symmetric T sections or angles), which is needed in General section definition
Perhaps that can be added

Barring that I like no 3 as it seems like easiest to continue work from, as you can still find your bar in ETABS and "simply" reassign the section

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

No branches or pull requests

3 participants