# Shell elements on Opensees

**URL:** <https://forum.compas-framework.org/t/shell-elements-on-opensees/349>\
**Category:** compas\_fea\
**Created:** [June 19, 2020, 9:27pm UTC](https://forum.compas-framework.org/t/shell-elements-on-opensees/349 "2020-06-19T21:27:47Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![arpastrana](https://avatars.discourse-cdn.com/v4/letter/a/a88e4f/32.png) [@arpastrana](https://forum.compas-framework.org/u/arpastrana)\
**Post date:** [June 19, 2020, 9:27pm UTC](https://forum.compas-framework.org/t/shell-elements-on-opensees/349/1 "2020-06-19T21:27:48Z")

</div>

Hi! Does `compas_fea` on `opensees` support the analysis of shell elements like [this](https://compas-dev.github.io/compas_fea/examples/mesh_floor_rhino.html)? If not, would adding this feature entail a major extension of the current wrappers/functionaliy around `opensees`? I’m thinking about it from the perspective of a fellow pull-requester.

---

<div class="post-metadata">

**Author:** ![tomvanmele](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.compas-framework.org/tomvanmele/32/13_2.png) [@tomvanmele](https://forum.compas-framework.org/u/tomvanmele)\
**Post date:** [June 24, 2020, 7:53am UTC](https://forum.compas-framework.org/t/shell-elements-on-opensees/349/2 "2020-06-24T07:53:28Z")

</div>

hi rafael,

we are currently preparing to release `compas_fea2` which will completely replace version 1.  
not sure how much effort it is to still add something like this to FEA1.  
deferring to @franaudo 🙂

---

<div class="post-metadata">

**Author:** ![franaudo](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.compas-framework.org/franaudo/32/107_2.png) [@franaudo](https://forum.compas-framework.org/u/franaudo)\
**Post date:** [June 24, 2020, 8:27am UTC](https://forum.compas-framework.org/t/shell-elements-on-opensees/349/3 "2020-06-24T08:27:01Z")

</div>

Hi Rafael,

`compas_fea(1)` does not currently support what you are asking. Adding it now would make little (if no) sense, since `compas_fea2` is almost ready and it is designed to ease outside contributions.

---

<div class="post-metadata">

**Author:** ![arpastrana](https://avatars.discourse-cdn.com/v4/letter/a/a88e4f/32.png) [@arpastrana](https://forum.compas-framework.org/u/arpastrana)\
**Post date:** [June 24, 2020, 8:43am UTC](https://forum.compas-framework.org/t/shell-elements-on-opensees/349/4 "2020-06-24T08:43:25Z")

</div>

That’s good news, @franaudo @tomvanmele! With what (cool) new features the next release will surprise us? 🙂

---

<div class="post-metadata">

**Author:** ![franaudo](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.compas-framework.org/franaudo/32/107_2.png) [@franaudo](https://forum.compas-framework.org/u/franaudo)\
**Post date:** [June 24, 2020, 9:05am UTC](https://forum.compas-framework.org/t/shell-elements-on-opensees/349/5 "2020-06-24T09:05:37Z")

</div>

It is a complete restructure to have a clear API (for both users and developers). This should promote more contributions and also help to expand the range of softwares supported (currently only abaqus, ansys and limited opensees).

On top of that, there are already a few upgrades, such as for example the possibility to use user-defined material subroutines for advanced material modelling.

But stay tuned, it should be ready in a few weeks… 😉

---

<div class="post-metadata">

**Author:** ![MP\_Pelle](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.compas-framework.org/mp_pelle/32/228_2.png) [@MP\_Pelle](https://forum.compas-framework.org/u/MP_Pelle)\
**Post date:** [May 26, 2021, 9:52am UTC](https://forum.compas-framework.org/t/shell-elements-on-opensees/349/6 "2021-05-26T09:52:05Z")

</div>

Hi @franaudo  
any news on Compas\_Fea\_v2?

I am curious to understand how you are dealing with OpenSees 🙂  
I am the developer of Alpaca4d https://www.food4rhino.com/app/alpaca4d which is a Grasshopper Wrapper for a limited OpenSees (I have still implemented a lot)

Best,  
Marco

---

<div class="post-metadata">

**Author:** ![franaudo](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.compas-framework.org/franaudo/32/107_2.png) [@franaudo](https://forum.compas-framework.org/u/franaudo)\
**Post date:** [May 26, 2021, 11:00am UTC](https://forum.compas-framework.org/t/shell-elements-on-opensees/349/7 "2021-05-26T11:00:46Z")

</div>

Ciao Marco,

`fea2` is in the making…we expanded the team quite a lot and decided to add more stuff before releasing. I wish I could give you a date, but unfortunately I don’t have it. What I can tell you is that I have added a 3D topology optimization feature and we are working on the integration with `gmesh` and `compas_view2` so that we are independent from the CAD environment (rhino/blender will still be supported though).

Meanwhile, we are still maintaining `compas_fea` (now fully compatible with the latest version of `compas`).

Regarding OpenSees, the approach with `compas_fea` and `compas_fea2` is always to generate an `input file`, because in this way we are consistent across all supported software (abaqus, ansis, sofistik for now): moreover, the bottleneck in terms of time is (almost always) on the analysis part, hence the additional I/O time to generate and read the input file is marginal.

A different strategy would be to use the opensees [python interpreter](https://openseespydoc.readthedocs.io/en/latest/) and generate the model in runtime. Probably you are already aware of it, but I thought it was worth mentioning it. 🙂

Please let me know if you have any other questions!

Ciao,  
Francesco

PS: I haven’t used `alpaca4d` but looks cool! I will give it a try at some point 🙂

---

<div class="post-metadata">

**Author:** ![nfeihl](https://avatars.discourse-cdn.com/v4/letter/n/0ea827/32.png) [@nfeihl](https://forum.compas-framework.org/u/nfeihl)\
**Post date:** [October 11, 2022, 12:58pm UTC](https://forum.compas-framework.org/t/shell-elements-on-opensees/349/8 "2022-10-11T12:58:05Z")

</div>

Hi @franaudo ,

Is there any news about compas\_fea2 ?  
Is it still under active development?

I would love to give it a try at some point.

Best,  
Nicolas

---

<div class="post-metadata">

**Author:** ![franaudo](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.compas-framework.org/franaudo/32/107_2.png) [@franaudo](https://forum.compas-framework.org/u/franaudo)\
**Post date:** [October 11, 2022, 1:49pm UTC](https://forum.compas-framework.org/t/shell-elements-on-opensees/349/9 "2022-10-11T13:49:02Z")

</div>

Hello Nicolas!

I know that I keep saying this…but we are really close 😃

If you want to have a preview, here is the repo: [compas-dev/compas\_fea2: FEA for the COMPAS framework. (github.com)](https://github.com/compas-dev/compas_fea2)

Please note that it is an alpha version and that we will soon publish major updates, but at least you can have an idea 😉

Best,  
Francesco

---

<div class="post-metadata">

**Author:** ![nfeihl](https://avatars.discourse-cdn.com/v4/letter/n/0ea827/32.png) [@nfeihl](https://forum.compas-framework.org/u/nfeihl)\
**Post date:** [October 11, 2022, 3:12pm UTC](https://forum.compas-framework.org/t/shell-elements-on-opensees/349/10 "2022-10-11T15:12:13Z")

</div>

👏 🙌 ✨

> [@franaudo](#):
>
> I know that I keep saying this…but we are really close 😃

super nice!

Thanks a lot for the repo link, I will definitely have a look. 🤓

Cheers,  
Nicolas
