Skip to content
Discussion options

You must be logged in to vote

Hi @tannhorn, yes this is a known issue with Paraview release 5.10.0 (many MOOSE users have encountered it, https://discourse.paraview.org/t/unique-name-requirement-for-nodesets-and-sidesets/8171/2).

One way around it is to load the "Legacy" plugin in Paraview. If you go to the "Tools" drop-down menu, select "Manage Plugins" and then load the "LegacyExodusReader" plugin.

I would guess that you probably have different paraview versions in/outside of WSL.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@aprilnovak
Comment options

Answer selected by tannhorn
@tannhorn
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants