# Updating mesh at every timestep (Nek5000 parallel reader)
**URL:** https://discourse.paraview.org/t/updating-mesh-at-every-timestep-nek5000-parallel-reader/16185
**Category:** ParaView Support
**Created:** [February 18, 2025, 8:23am UTC](https://discourse.paraview.org/t/updating-mesh-at-every-timestep-nek5000-parallel-reader/16185 "2025-02-18T08:23:58Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Emo](https://discourse.paraview.org/u/Emo)
#### Post date: [February 18, 2025, 8:23am UTC](https://discourse.paraview.org/t/updating-mesh-at-every-timestep-nek5000-parallel-reader/16185/1 "2025-02-18T08:23:58Z")
Hi everyone,
The native parallel Nek5000 file reader of Paraview 5.13.2 works well when the mesh is static. It seems by default, it reads the mesh from the first timestep and never updates it again. However, when we have a dynamic mesh (rotation, refinement, etc), only the first timestep is shown correctly and from the second timestep onward, the fields look strange as the mesh information is no longer valid. Is there an option, to force re-reading the mesh at every new timestep for Nek5000 reader?
Thanks in advance
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [February 18, 2025, 8:52am UTC](https://discourse.paraview.org/t/updating-mesh-at-every-timestep-nek5000-parallel-reader/16185/2 "2025-02-18T08:52:05Z")
Hi @Emo
Please share your data.
Best,
---
### Author:  [@Emo](https://discourse.paraview.org/u/Emo)
#### Post date: [February 18, 2025, 9:11am UTC](https://discourse.paraview.org/t/updating-mesh-at-every-timestep-nek5000-parallel-reader/16185/3 "2025-02-18T09:11:19Z")
@mwestphal at Unfortunately, each timestep is about 22GB, but I can share any other information you need.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [February 18, 2025, 9:19am UTC](https://discourse.paraview.org/t/updating-mesh-at-every-timestep-nek5000-parallel-reader/16185/4 "2025-02-18T09:19:07Z")
TBH your description sounds like a bug, I doubt there is a workaround apart using another file format.
Reproducing the issue with a smaller, shareable, dataset would go a long way.
---
### Author:  [@Emo](https://discourse.paraview.org/u/Emo)
#### Post date: [February 18, 2025, 9:31am UTC](https://discourse.paraview.org/t/updating-mesh-at-every-timestep-nek5000-parallel-reader/16185/5 "2025-02-18T09:31:07Z")
@mwestphal sure, I’ll try to create a smaller version of this to share. I think if there was an option to read the mesh per timestep, everything else should be fine.
---
### Author:  [@Emo](https://discourse.paraview.org/u/Emo)
#### Post date: [February 19, 2025, 2:19pm UTC](https://discourse.paraview.org/t/updating-mesh-at-every-timestep-nek5000-parallel-reader/16185/6 "2025-02-19T14:19:58Z")
[Nek5000\_dynamicMesh.tar.gz](https://discourse.paraview.org/uploads/short-url/7RV2o3RziYfdVAd88DYRdNIYGNO.gz) (3.5 MB)
@mwestphal I have attached a small 2D case. The mesh is refined from timestep 1 to 2, the first timestep is shown correctly as the mesh is loaded from the first timestep. The second timestep looks strange as the mesh is cached from the first timestep which is no longer valid
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [February 19, 2025, 2:23pm UTC](https://discourse.paraview.org/t/updating-mesh-at-every-timestep-nek5000-parallel-reader/16185/7 "2025-02-19T14:23:42Z")
I confirm there is a bug, please open an issue here:
[https://gitlab.kitware.com/paraview/paraview/-/issues](https://gitlab.kitware.com/paraview/paraview/-/issues)
Sadly, there does not seems to be any workaround without modifying the source code afaict. A proper fix is needed.
---
### Author:  [@Emo](https://discourse.paraview.org/u/Emo)
#### Post date: [February 19, 2025, 2:35pm UTC](https://discourse.paraview.org/t/updating-mesh-at-every-timestep-nek5000-parallel-reader/16185/8 "2025-02-19T14:35:50Z")
Sure, I opened an issue on Gitlab: [https://gitlab.kitware.com/paraview/paraview/-/issues/22890](https://gitlab.kitware.com/paraview/paraview/-/issues/22890)