-
Notifications
You must be signed in to change notification settings - Fork 577
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seacas issue again? Nalu nodal output failing again in Paraview #13795
Comments
I think that this looks correct?
|
Subject: Problem with output and viz in Paraview Greetings, I recently noticed (today) that in Paraview 5.13.0, I am not able to load in vector-based STK fields in addition to generic fields of a given length. However, in the previous Paraview release, I am able to viz all fields without issue. It is not clear to me if this is a STK or Paraview issue. I say this since Ensight is also acting strange in that the vector fields are not being loaded in automatically. I see the following type of errors in Paraview: ( 85.251s) [paraview ] vtkIOSSReader.cxx:458 ERR| Error reading entity block (or set) named 'block_1' from '/home/spdomin/gitHubWork/naluAnalysis/asc_pem/3dFuelSpillNoEvap/output/3dFuelSpillNoEvap.e.15.16'; skipping. Details: ERROR: Could not find field 'velocityx' |
Adding this for future reference:
|
Modifying the previous future reference comment: To set the IOSS properties via an environment variable, the syntax would be:
See https://sandialabs.github.io/seacas-docs/ioss_html/index.html#properties. The use of an environment variable is near the bottom of that page. |
@spdomin If you still have any of the files which were failing on ParaView, could you send me a copy to help debug the issue. Thanks. |
Nalu output and visualization is again broken - and it looks like a previous Seacas issue, @gsjaardema and/or @alanw0 👍
( 14.588s) [paraview ] vtkIOSSReader.cxx:458 ERR| Error reading entity block (or set) named 'block_1' from '/home/spdomin/myFile.e.4.0 skipping. Details: ERROR: Could not find field 'velocityx'
I am guessing this is due to that last Seacas snapshot that caused other issues?
The text was updated successfully, but these errors were encountered: