# no fields are rendered after opening OpenPMD file
**URL:** https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533
**Category:** ParaView Support
**Created:** [October 10, 2024, 6:42pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533 "2024-10-10T18:42:36Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [October 10, 2024, 6:42pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/1 "2024-10-10T18:42:36Z")
I opened an OpenPMD file in Paraview 5.13.1 on MacOS Sequoia 15.0.1, but nothing is rendered (no box representing the simulation volume). I also don’t see any options to change the coloring of the geometry representation to that of any of the fields that it lists in the reader:
This can be reproduced with the attached files, by opening the “paraview.pmd” file:
[openpmd\_test\_files.tar.gz](https://discourse.paraview.org/uploads/short-url/qFdC3H0UVz38isMkCWe0lgrS0ev.gz) (321.0 KB)
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 11, 2024, 9:32am UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/2 "2024-10-11T09:32:40Z")
I confirm that ParaView open the file as an empty files without any points or cells.
More investigation is needed in order to figure out if this is an issue in the file or in the reader.
---
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [October 14, 2024, 4:35pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/3 "2024-10-14T16:35:28Z")
@mwestphal This is a regression between Paraview 5.12.1 and 5.13.0. It works in the former version, and displays the above behavior in the latter.
I can also open the \*.bp file directly with the ADIOS2 image reader in all versions 5.12.1-5.13.1. I think it’s a Paraview bug.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 14, 2024, 5:02pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/4 "2024-10-14T17:02:48Z")
Maybe @ayenpure or @AxelHuebl has some idea of what changed in the openPMD file that might explain this behavior?
---
### Author:  [@ayenpure](https://discourse.paraview.org/u/ayenpure)
#### Post date: [October 31, 2024, 7:35pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/5 "2024-10-31T19:35:53Z")
We did a bunch of new additions to the openPMD reader over the last couple months to support different data layouts supported by the openPMD API. I suspect some of it might have broken existing functionality from 5.12.1. I’ll investigate this.
---
### Author:  [@ayenpure](https://discourse.paraview.org/u/ayenpure)
#### Post date: [October 31, 2024, 8:03pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/6 "2024-10-31T20:03:37Z")
Issue identified: Since we did not fully support AMR grids using the openPMD reader, in the last iteration of updates we skipped all arrays whose variable names contain `_lvl`. This was done because the openPMD reader crashed when there were arrays with different shapes becase of different levels of refinement. As a side effect, the feature the data that was previously possible to load will break. If you’re interested I can send a python drop-in replacement to get around the issue until we implement full AMR support in the near future.
---
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [November 1, 2024, 5:45pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/7 "2024-11-01T17:45:09Z")
Yes, please send a patch. That would be very helpful, thanks!
---
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [November 1, 2024, 5:51pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/8 "2024-11-01T17:51:13Z")
@ayenpure Can my test data that includes `_lvl`-named fields be added to the test suite? That would avoid a lot of headaches in the future.
---
### Author:  [@ayenpure](https://discourse.paraview.org/u/ayenpure)
#### Post date: [November 1, 2024, 5:57pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/9 "2024-11-01T17:57:29Z")
@BenWibking Can you tell me if you’re building ParaView or downloading pre-built binaries?
Also, are you using Linux of MacOS if using binaries?
It would be ideal for the openPMD reader to have a test but currently we don’t have one.
I’m not certain if ParaView has tests for python plugins, @cory.quammen is this true?
---
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [November 1, 2024, 9:35pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/10 "2024-11-01T21:35:59Z")
I’m using the pre-built binaries on macOS. I typically build Paraview using Spack on Linux. It would be great if you could add a patch to the Spack package.
---
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [November 11, 2024, 3:40pm UTC](https://discourse.paraview.org/t/no-fields-are-rendered-after-opening-openpmd-file/15533/11 "2024-11-11T15:40:00Z")
@ayenpure Can you send a patch to workaround this issue?