# Failure importing section, static mechanical analysis

**URL:** <https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871>\
**Category:** Uncategorized\
**Created:** [October 11, 2023, 5:01pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871 "2023-10-11T17:01:46Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jpel32](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@Jpel32](https://calculix.discourse.group/u/Jpel32)\
**Post date:** [October 11, 2023, 5:01pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/1 "2023-10-11T17:01:46Z")

</div>

Hello everyone! I am new to the CCX community but so far I love it. I’m currently working on an automated script for simulating mechanical response (simple compression test) of 3D printed lattices. I’ve been able to generate the structures in a separate software and import elements, nodes, BC’s, etc. However, I am consistently receiving the following Error when I import into PrePoMax:

“Error: Failed to import section: \*SOLID SECTION, ELSET=ALL\_NODES, MATERIAL=MAT\_FIG4\_TGH\_15”

I’m assigning the material to the entire lattice, so the section is simply all elements. I’m using python to modify and compile the .inp file from the secondary software, so I thought it was an issue with my code. However, I tried creating the section from within PrePoMax, then exporting a .inp, then re-importing that same .inp and I receive the same error.

I can attach my .inp input file example if that is helpful. I appreciate any help that could be provided on this!

---

<div class="post-metadata">

**Author:** ![Calc\_em](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@Calc\_em](https://calculix.discourse.group/u/Calc_em)\
**Post date:** [October 11, 2023, 5:16pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/2 "2023-10-11T17:16:26Z")

</div>

Can you say which software you are using for mesh preparation ? Is it Abaqus ?

---

<div class="post-metadata">

**Author:** ![Jpel32](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@Jpel32](https://calculix.discourse.group/u/Jpel32)\
**Post date:** [October 11, 2023, 6:19pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/3 "2023-10-11T18:19:40Z")

</div>

I’m using nTopology, which is able to output .inp but it needs some slight modifications before using like replacing " " with “\_” in certain places

---

<div class="post-metadata">

**Author:** ![JuanP74](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@JuanP74](https://calculix.discourse.group/u/JuanP74)\
**Post date:** [October 11, 2023, 6:27pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/4 "2023-10-11T18:27:36Z")

</div>

check if you can import it with cgx

---

<div class="post-metadata">

**Author:** ![Jpel32](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@Jpel32](https://calculix.discourse.group/u/Jpel32)\
**Post date:** [October 11, 2023, 6:28pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/5 "2023-10-11T18:28:23Z")

</div>

Ok I’ll give it a shot, here’s a link to .inp if helpful: [Lattice\_07\_20231005.inp - Google Drive](https://drive.google.com/file/d/1IatztSxDCYC58RqAn9K41yPnyxwbpmwz/view?usp=sharing)

---

<div class="post-metadata">

**Author:** ![Calc\_em](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@Calc\_em](https://calculix.discourse.group/u/Calc_em)\
**Post date:** [October 11, 2023, 6:45pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/6 "2023-10-11T18:45:39Z")

</div>

It might be better to prepare the geometry in nTopology, export it to STL or STEP and mesh in Gmsh for use in CalculiX.

---

<div class="post-metadata">

**Author:** ![Disla](https://yyz2.discourse-cdn.com/free1/user_avatar/calculix.discourse.group/disla/32/3548_2.png) [@Disla](https://calculix.discourse.group/u/Disla)\
**Post date:** [October 11, 2023, 6:49pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/7 "2023-10-11T18:49:15Z")

</div>

Hi Jpel32 and welcome.  
a quick note that caught my attention

ELSET=ALL\_NODES

Elset is intended for elements.  
¿ALL\_NODES, is a set of elements or nodes?

---

<div class="post-metadata">

**Author:** ![JuanP74](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@JuanP74](https://calculix.discourse.group/u/JuanP74)\
**Post date:** [October 11, 2023, 7:15pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/8 "2023-10-11T19:15:51Z")

</div>

nset not according to input deck rules, the manual reads:

First line:  
• \*NSET  
• Enter any needed parameters and their values.  
Following line if the GENERATE parameter is omitted:  
• List of nodes and/or sets of nodes previously defined to be assigned to this  
node set ( **maximum 16 entries per line** ).

cgx shows the error when reading.

---

<div class="post-metadata">

**Author:** ![Jpel32](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@Jpel32](https://calculix.discourse.group/u/Jpel32)\
**Post date:** [October 11, 2023, 7:20pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/9 "2023-10-11T19:20:11Z")

</div>

Thank you for looking at my file! Which line do you see “ELEST=ALL\_NODES” in ?

---

<div class="post-metadata">

**Author:** ![Jpel32](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@Jpel32](https://calculix.discourse.group/u/Jpel32)\
**Post date:** [October 11, 2023, 7:21pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/10 "2023-10-11T19:21:49Z")

</div>

Hmm that may be the issue. When I was printing the nodesets from python I don’t think I specified 16 per line. I’ll try that and then see what happens, thanks for the advice!

---

<div class="post-metadata">

**Author:** ![Calc\_em](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@Calc\_em](https://calculix.discourse.group/u/Calc_em)\
**Post date:** [October 11, 2023, 7:55pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/11 "2023-10-11T19:55:44Z")

</div>

> [@Jpel32](#):
>
> Which line do you see “ELEST=ALL\_NODES” in ?

It’s right here in your first post:

> [@Jpel32](#):
>
> ELSET=ALL\_NODES

---

<div class="post-metadata">

**Author:** ![Jpel32](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@Jpel32](https://calculix.discourse.group/u/Jpel32)\
**Post date:** [October 11, 2023, 8:15pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/12 "2023-10-11T20:15:04Z")

</div>

@Calc_em Oh I see. I may have had an older file open when I copied the error message. This is what is reads now:  
Error: Failed to import section: \*SOLID SECTION, MATERIAL=MAT\_FIG4\_TGH\_15, ELSET=ALL\_ELEMENTS  
Where ALL\_ELEMENTS is just all of the elements.

@JuanP74 I edited my script to output 16 entries max, but am recieving the same error in PrePoMax. Here is the updated .inp file. [Lattice\_04\_20231005.inp - Google Drive](https://drive.google.com/file/d/1Row7L_sYk_qJjIN_nOUpu9YMZS6TTgPY/view?usp=sharing)

I appreciate everyones help!

---

<div class="post-metadata">

**Author:** ![JuanP74](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@JuanP74](https://calculix.discourse.group/u/JuanP74)\
**Post date:** [October 11, 2023, 8:35pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/13 "2023-10-11T20:35:35Z")

</div>

it works in cgx. I have experienced some issues from prepomax when reading input files. You could try asking in prepomax discourse forum

 ![Captura de pantalla 2023-10-11 a las 22.33.42](https://global.discourse-cdn.com/free1/uploads/calculix/original/2X/5/56cfca4bdeb27500a1663fdb5f245bd35208c5b1.png)

---

<div class="post-metadata">

**Author:** ![Calc\_em](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@Calc\_em](https://calculix.discourse.group/u/Calc_em)\
**Post date:** [October 11, 2023, 9:02pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/14 "2023-10-11T21:02:16Z")

</div>

> [@JuanP74](#):
>
> I have experienced some issues from prepomax when reading input files.

The inp file importer in PrePoMax still needs some improvements, it doesn’t support all the different forms of mesh definition syntax permitted by CalculiX. It’s a known issue though.

---

<div class="post-metadata">

**Author:** ![fgr](https://avatars.discourse-cdn.com/v4/letter/f/f4b2a3/32.png) [@fgr](https://calculix.discourse.group/u/fgr)\
**Post date:** [October 12, 2023, 8:34am UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/15 "2023-10-12T08:34:19Z")

</div>

@Jpel32 , It seems like that PrePoMax ver. 1.3.4 and probably also newer versions are capable of loading your structure without errors

 ![Structure](https://global.discourse-cdn.com/free1/uploads/calculix/original/2X/a/a5c51e17c06542a11ccf3f3f68224a742e94a070.jpeg)

---

<div class="post-metadata">

**Author:** ![Jpel32](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@Jpel32](https://calculix.discourse.group/u/Jpel32)\
**Post date:** [October 12, 2023, 3:25pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/16 "2023-10-12T15:25:46Z")

</div>

@fgr Interesting, I am using v1.4.1. I will maybe try 1.3.4 and see what happens

---

<div class="post-metadata">

**Author:** ![Jpel32](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@Jpel32](https://calculix.discourse.group/u/Jpel32)\
**Post date:** [October 12, 2023, 3:29pm UTC](https://calculix.discourse.group/t/failure-importing-section-static-mechanical-analysis/1871/17 "2023-10-12T15:29:08Z")

</div>

@fgr @Calc_em @JuanP74 @Disla  
I attempted to open the .inp file in v1.4.0 and it worked, seems as though it was an issue with the newer 1.4.1 version. Thank you everyone for your help!
