# run into an issue when import .vtu generated by Abaqus
**URL:** https://discourse.paraview.org/t/run-into-an-issue-when-import-vtu-generated-by-abaqus/9483
**Category:** ParaView Support
**Created:** [April 20, 2022, 8:03pm UTC](https://discourse.paraview.org/t/run-into-an-issue-when-import-vtu-generated-by-abaqus/9483 "2022-04-20T20:03:46Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@marine3454](https://discourse.paraview.org/u/marine3454)
#### Post date: [April 20, 2022, 8:03pm UTC](https://discourse.paraview.org/t/run-into-an-issue-when-import-vtu-generated-by-abaqus/9483/1 "2022-04-20T20:03:46Z")
Hi all,
I wonder if someone would be able to come up with a good solution regarding my issue.
My python script is designed to extract nodal temperature (NT11) variable from abaqus and eventually the script writes .vtu file using ParaView XML format.
I haven’t had any issue with my script for a couple of years, but recently ran across new issue.
With this FE model,
the script does make .vtu without any error in abaqus, but Paraview shows nothing when import the .vtu file. But I am noticed something is wrong because the .vtu file size is less than 1KB.
Since I haven’t gotten any errors either from abaqus or Paraview, I have no idea what causes this issue.
So could someone please take a look at it?
abaqus input, python script, .vtu files are attached.
[meltingpool.py](https://discourse.paraview.org/uploads/short-url/vxYZnMLU9gYuMKfHEjYBtXKFqCS.py) (4.5 KB)
[paratest.vtu](https://discourse.paraview.org/uploads/short-url/9G5sAxzd8jbj63HWuqpfT36pmlG.vtu) (648 Bytes)
[paratest.inp](https://discourse.paraview.org/uploads/short-url/mc7W3QBBZ5cRvPT7AVpy6MpeygI.inp) (372.1 KB)
\*ps1) if you would like to use my script for any reasons, you would be welcome to use.
\*ps2) when tested with different model, the script works perfect as shown below:
---
### Author:  [@Kenichiro-Yoshimi](https://discourse.paraview.org/u/Kenichiro-Yoshimi)
#### Post date: [April 20, 2022, 11:47pm UTC](https://discourse.paraview.org/t/run-into-an-issue-when-import-vtu-generated-by-abaqus/9483/2 "2022-04-20T23:47:52Z")
Isn’t the problem that the converter script doesn’t support uppercase for identifiers such as \ ***NODE** and \ ***ELEMENT**?
---
### Author:  [@marine3454](https://discourse.paraview.org/u/marine3454)
#### Post date: [April 22, 2022, 4:05pm UTC](https://discourse.paraview.org/t/run-into-an-issue-when-import-vtu-generated-by-abaqus/9483/3 "2022-04-22T16:05:35Z")
No, that’s not causing the issue I addressed.
---
### Author:  [@Kenichiro-Yoshimi](https://discourse.paraview.org/u/Kenichiro-Yoshimi)
#### Post date: [April 22, 2022, 7:41pm UTC](https://discourse.paraview.org/t/run-into-an-issue-when-import-vtu-generated-by-abaqus/9483/4 "2022-04-22T19:41:05Z")
I don’t have the odb input and the Abaqus python library, so I can’t test it, but at least I was able to load the nodes and elements into ParaView with the following changes to the script.
```python
if line.strip().lower() == '*node':
state = 1
elif line.lower().startswith('*element, type=dc3d8'):
state = 2
```
---
### Author:  [@marine3454](https://discourse.paraview.org/u/marine3454)
#### Post date: [April 26, 2022, 7:35pm UTC](https://discourse.paraview.org/t/run-into-an-issue-when-import-vtu-generated-by-abaqus/9483/5 "2022-04-26T19:35:00Z")
Yes, I tested with your changes in the script and I am able to import the model. It looks good. Thank you for your tips.
btw, I’ve never seen this uppercase issue before. so how were you able to figure that out on your side?