# VTK Lagrange Pyramid 74
**URL:** https://discourse.paraview.org/t/vtk-lagrange-pyramid-74/14035
**Category:** ParaView Support
**Created:** [February 27, 2024, 2:15pm UTC](https://discourse.paraview.org/t/vtk-lagrange-pyramid-74/14035 "2024-02-27T14:15:12Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Frankx9](https://discourse.paraview.org/u/Frankx9)
#### Post date: [February 27, 2024, 2:15pm UTC](https://discourse.paraview.org/t/vtk-lagrange-pyramid-74/14035/1 "2024-02-27T14:15:12Z")
Hello,
is there any script to generate a simple vtk lagrange pyramid (type = 74) to check the proper node ordering to export the solution?
Best regards
---
### Author:  [@dcthomp](https://discourse.paraview.org/u/dcthomp)
#### Post date: [March 4, 2024, 3:04pm UTC](https://discourse.paraview.org/t/vtk-lagrange-pyramid-74/14035/2 "2024-03-04T15:04:28Z")
In VTK, there is the `Filters/Sources/vtkCellTypeSource.cxx`. It is exposed in ParaView as “Unstructured Cell Types” in the Sources menu.
---
### Author:  [@Frankx9](https://discourse.paraview.org/u/Frankx9)
#### Post date: [March 4, 2024, 4:43pm UTC](https://discourse.paraview.org/t/vtk-lagrange-pyramid-74/14035/3 "2024-03-04T16:43:44Z")
In VTK I found this:
```auto
case VTK_LAGRANGE_PYRAMID:
// vtk does not have vtkHigherOrderPyramid.
switch (npts)
{
case 5:
case 13:
case 14:
case 19:
default:
vtkLog(WARNING, << "Unsupported number of points for cell - VTK_PYRAMID."
<< "Supported: None "
<< "Got: " << npts);
break;
}
break;
```
in [https://gitlab.kitware.com/vtk/vtk/-/blob/master/Filters/General/vtkFiniteElementFieldDistributor.cxx](https://gitlab.kitware.com/vtk/vtk/-/blob/master/Filters/General/vtkFiniteElementFieldDistributor.cxx).
Are they planned to be supported?
Best
---
### Author:  [@dcthomp](https://discourse.paraview.org/u/dcthomp)
#### Post date: [March 4, 2024, 4:56pm UTC](https://discourse.paraview.org/t/vtk-lagrange-pyramid-74/14035/4 "2024-03-04T16:56:10Z")
There are no plans at this point; the issue is that while there are arbitrary-order formulations for integration, those formulations do not behave well when evaluating the shape functions _and their inverses_ near (but not at) the tip of the pyramid. This is needed for visualization, but not integration.