Requesting Implementation of CSI API in Future Builds and Extends support to more FEM Packages

[udhay111]

Requesting Implementation of CSI API in Future Builds and Extends support to more FEM Packages

About CSI API

Computers and Structures, Inc.’s Application Programming Interface (API) has been launched by CSI which exposes all components for CSi Procucts all as whole.

To know more about CSI API follow this link

Why CSI API In Future builds

In future, Adapters and engines can be more efficiently utilised and can be extended to all CSI products especially for bridges, Plants and Post tensioning structures using CSI SAFE, CSI Bridge and CSI Plant. It will be game changer for Structural Analysis Package.

So in future more can be achieved for CSI products Engine and Adapters via BHOM environment with ditching SAP2000 and Etabs Toolkit as whole and cocentrate on more csi Products or maintaining for legacy versions of SAP2000 and ETABS

Expectation

Similarly I am Requesting Developer teams to also implements Adapters and engines extend support to more FEM packages like ABAQUS and ANSYS

More over this is my Humble request to Developer team as whole.

please post me about this via this email[email protected]
Thanks for being patience to go through my thoughts.

[FraserGreenroyd]

FYI @IsakNaslundBh @JosefTaylor

[IsakNaslundBh]

Hi @udhay111 , thanks for raising this.

In future, Adapters and engines can be more efficiently utilised and can be extended to all CSI products especially for bridges, Plants and Post tensioning structures using CSI SAFE, CSI Bridge and CSI Plant. It will be game changer for Structural Analysis Package.

We have been discussing this as well, moving all to a CSI_Toolkit that would work with Etabs/SAP etc. I think it is a really good idea and something that we should strive to do, but can not promise any timeframe for when it could be done I am afraid as resource need to be balanced with other priorities.

If/when there is any progress on it I will make sure to link back to this issue! :)

Similarly I am Requesting Developer teams to also implements Adapters and engines extend support to more FEM packages like ABAQUS and ANSYS

This is something we would be very much supportive of, but currently we are not able to action internally. If you would be keen to start implementing the adapters yourself, we would be happy to support you and there is also scope to host this adapter in the BHoM organisation and, once progress is made, for it to be included in BHoM installers.

[udhay111]

Thanks for the mail i I understand the time constraint as it ground work of writing lots of code. But guys keep the good work. once again thanks for your support and timely response. sure I will post adapter upto my extent.

…

On Tue, 19 Apr, 2022, 7:39 pm Isak Näslund, ***@***.***> wrote: Hi @udhay111 <https://github.com/udhay111> , thanks for raising this. In future, Adapters and engines can be more efficiently utilised and can be extended to all CSI products especially for bridges, Plants and Post tensioning structures using CSI SAFE, CSI Bridge and CSI Plant. It will be game changer for Structural Analysis Package. We have been discussing this as well, moving all to a CSI_Toolkit that would work with Etabs/SAP etc. I think it is a really good idea and something that we should strive to do, but can not promise any timeframe for when it could be done I am afraid as resource need to be balanced with other priorities. If/when there is any progress on it I will make sure to link back to this issue! :) Similarly I am Requesting Developer teams to also implements Adapters and engines extend support to more FEM packages like ABAQUS and ANSYS This is something we would be very much supportive of, but currently we are not able to action internally. If you would be keen to start implementing the adapters yourself, we would be happy to support you and there is also scope to host this adapter in the BHoM organisation and, ones progress is made, for it to be included in BHoM installers. — Reply to this email directly, view it on GitHub <#260 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASKJPXTYJH7NUUEGFSIV6U3VF25BVANCNFSM5TUIOBIQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>