# Compas - Grasshopper - Abaqus

**URL:** <https://forum.compas-framework.org/t/compas-grasshopper-abaqus/814>\
**Category:** compas\
**Created:** [March 21, 2024, 3:25pm UTC](https://forum.compas-framework.org/t/compas-grasshopper-abaqus/814 "2024-03-21T15:25:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MilenaJ](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.compas-framework.org/milenaj/32/590_2.png) [@MilenaJ](https://forum.compas-framework.org/u/MilenaJ)\
**Post date:** [March 21, 2024, 3:25pm UTC](https://forum.compas-framework.org/t/compas-grasshopper-abaqus/814/1 "2024-03-21T15:25:26Z")

</div>

Hello all,

I was wondering if there is a good example that I can start with that sets up my geometry fully in Grasshopper, then use Compas to connect to Abaqus. What I am trying to do is to control the parameters of my structure from Grasshopper, as this would be good for some other parts of an algorithm that I am writing in Grasshopper.  
Also, I tried first to go through examples available on the website that connect Rhino to Abaqus (frankly, I am a beginner when it comes to textual programming), but I encounter an error. When I type the line _from compas\_fea.cad import rhino_  
I get: _1. Error running script: cannot import name ‘RhinoMesh’ from ‘compas\_rhino.geometry’_  
I am using Rhino 8.

Edit: I also tried running the script for an arbitrary beam model just to see if it couples with Abaqus (without visualization in Rhino) but I get the following message: \*\*\*\* Saving data to structure.results unsuccessful \*\*\*\*

---

<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:** [May 7, 2024, 10:53pm UTC](https://forum.compas-framework.org/t/compas-grasshopper-abaqus/814/2 "2024-05-07T22:53:55Z")

</div>

hi,

the first version of `compas_fea` is no longer actively supported and will soon be archived and replaced with a newer version that is based on COMPAS 2.

we are unfortunately a bit stuck in version limbo because of the delayed transition from COMPAS 1 to COMPAS 2 in some of the extension packages (such as `compas_fea`).

we are working to resolve this asap. will keep you posted…