# ANSYS inputs

**URL:** https://discourse.paraview.org/t/ansys-inputs/1125
**Category:** ParaView Support
**Created:** [January 9, 2019, 7:37pm UTC](https://discourse.paraview.org/t/ansys-inputs/1125 "2019-01-09T19:37:40Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![jed-pnnl](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/j/f0a364/32.png) [@jed-pnnl](https://discourse.paraview.org/u/jed-pnnl)
#### Post date: [January 9, 2019, 7:37pm UTC](https://discourse.paraview.org/t/ansys-inputs/1125/1 "2019-01-09T19:37:40Z")

</div>

Can someone provide the details of what Paraview is looking for in an ANSYS .inp file?

---

<div class="post-metadata">

### Author: ![dcthomp](https://discourse.paraview.org/user_avatar/discourse.paraview.org/dcthomp/32/20_2.png) [@dcthomp](https://discourse.paraview.org/u/dcthomp)
#### Post date: [January 11, 2019, 1:11am UTC](https://discourse.paraview.org/t/ansys-inputs/1125/2 "2019-01-11T01:11:04Z")

</div>

I do not believe ParaView can read ANSYS files. It reads AVS UCD files that have a file extension of `.inp`, documented at

[https://people.sc.fsu.edu/~jburkardt/data/ucd/ucd.html](https://people.sc.fsu.edu/~jburkardt/data/ucd/ucd.html)

Although there are some exceptions, generally ParaView does not read simulation input decks; only simulation output for post-processing.