Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket
Please refer here for more information: CNX-573
Description & Motivation
In creating content for Revit & Grasshopper to ETABS, I noticed that the
CSIOpening
component is essentially useless. We write and appendCSIOpening
information to theAreaObj
, but this information is not used when receiving in ETABS.Definition in Grasshopper:
Receiving in ETABS:
These
AreaObj
s should have Yes for attribute OpeningChanges:
Looking at the API docs:
We need to
SetOpening
in the same way we assignDiaphragmAssignment
/CSIAreaSpring
:For
AreaToSpeckle
we targetCSIOpening
and notproperty
(otherwise ETABS ➡️ Speckle ➡️ ETABS won't be compatible).Validation of changes:
Grasshopper ➡️ Speckle ➡️ ETABS
ETABS ➡️ Speckle ➡️ ETABS
Revit ➡️ Speckle ➡️ ETABS
ETABS ➡️ Speckle ➡️ Revit
Previously:
Now:
Checklist:
Comments
This is messy. We need to revisit at a later stage.