# Compas\_fea example file error

**URL:** <https://forum.compas-framework.org/t/compas-fea-example-file-error/159>\
**Category:** compas\_fea\
**Created:** [March 25, 2019, 4:15pm UTC](https://forum.compas-framework.org/t/compas-fea-example-file-error/159 "2019-03-25T16:15:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Voulp](https://avatars.discourse-cdn.com/v4/letter/v/e5b9ba/32.png) [@Voulp](https://forum.compas-framework.org/u/Voulp)\
**Post date:** [March 25, 2019, 4:15pm UTC](https://forum.compas-framework.org/t/compas-fea-example-file-error/159/1 "2019-03-25T16:15:58Z")

</div>

Hello,

I try to run the compas\_fea beam frame example on Rhino and I get the attached error message. The script gets stuck in the Abaqus analysis. I have linked Abaqus in my Path folder, I can open it using the cmd prompt, and it runs, but do I need to do something else?

Thanks!

 ![compas_fea%20error](https://us1.discourse-cdn.com/flex015/uploads/compas_framework1/original/1X/d6277246fa06ba88347a9a1c89b47f7fdf3218bd.jpeg)

---

<div class="post-metadata">

**Author:** ![andrewliew](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.compas-framework.org/andrewliew/32/88_2.png) [@andrewliew](https://forum.compas-framework.org/u/andrewliew)\
**Post date:** [March 26, 2019, 7:11am UTC](https://forum.compas-framework.org/t/compas-fea-example-file-error/159/2 "2019-03-26T07:11:18Z")

</div>

Hi Voulp,

As this is the `plot_data` part, it is most likely the Abaqus analysis has worked okay, as you are now trying to plot results.

It is most probably an issue with your Anaconda/CPython install and/pr `PATH` outside of Rhino (which the `rhino` module and `plot_data` function try to access), or, a `PYTHONPATH` issue for `compas_fea`.

I cannot tell which without more info. Can you pop by the office so we can find out more? Then we can post the solution back here.

Andrew

---

<div class="post-metadata">

**Author:** ![andrewliew](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.compas-framework.org/andrewliew/32/88_2.png) [@andrewliew](https://forum.compas-framework.org/u/andrewliew)\
**Post date:** [March 26, 2019, 8:52am UTC](https://forum.compas-framework.org/t/compas-fea-example-file-error/159/3 "2019-03-26T08:52:50Z")

</div>

Problem was related to your group’s installation of Abaqus which appears to not have MPI installed/support for using Abaqus MPI multiprocessing. It was not a path problem as expected above.

The current temp solution is to turn off multiple `cpus` with `cpus=1` in `analyse_and_extract()`, or a later better fix is for me to enable the `THREADS` multiprocessing option. This is Issue [#100](https://github.com/compas-dev/compas_fea/issues/100) on the issue tracker.

---

<div class="post-metadata">

**Author:** ![mattiskoh](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@mattiskoh](https://forum.compas-framework.org/u/mattiskoh)\
**Post date:** [April 10, 2019, 8:29am UTC](https://forum.compas-framework.org/t/compas-fea-example-file-error/159/4 "2019-04-10T08:29:44Z")

</div>

Another (I guess rather obvious) option is to simply to install Abaqus MPI. Installer is (atleast for me) located at:

> C:\SIMULIA\Abaqus\6.14-1\installation\_info\client\_install

It should be installed automatically with Abaqus according to SIMULIA…

---

<div class="post-metadata">

**Author:** ![andrewliew](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.compas-framework.org/andrewliew/32/88_2.png) [@andrewliew](https://forum.compas-framework.org/u/andrewliew)\
**Post date:** [April 11, 2019, 7:45am UTC](https://forum.compas-framework.org/t/compas-fea-example-file-error/159/5 "2019-04-11T07:45:45Z")

</div>

I think it has something to do with your startup install scripts for Abaqus, whenever I install, I get a pop-up saying that MPI is getting installed, so something is happening automatically my end.

Either way, the problem should be resolved now as I have turned on `THREADS` instead of `MPI` as the default multi-processing option, there was no speed difference for me. See the closed issue [here](https://github.com/compas-dev/compas_fea/issues/100). Therefore you can revert to turning off `cpus = 1` (hopefully).
