Here is the e-mail describing the bug. Hello, We have found a possible error in the Alegra generated Exodus data in VisIt when using the Exodus Reader in multiple VisIt versions including 2.12.3 and 2.13.0 When turning of the second elment block VisIt gives and error message. "ERROR: Pseudocolor: () viewer: The pipeline object is being used improperly." Is this a know problem with a known workaround? We have sample data available to demonstrate this issue. We also had to load the data without using the Alegra preset in the Exodus reader or it would not even generate a pseudocolor plot. I have attempted to attach a 2 partition exodus file of 12 elements.If the attachment does not go through, then please contact me for the data. Thanks, Joe ~~~~~~~~~Joseph G. Hennessey Ph.D., SAIC, Team SAIC HITS Army Research Lab DOD Supercomputing Resource Center (ARL DSRC) ARL DSRC HITS SAIC (SAIC) Bldg. 120 , C214Voice: 410278-3619Email: joseph.g.hennessey2.ctr@mail.mil
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 3192
Status: Pending
Project: VisIt
Tracker: Bug
Priority: High
Subject: Bug reading Exodus files.
Assigned to: Kathleen Biagas
Category: -
Target version: 2.13.4
Author: Eric Brugger
Start: 08/01/2018
Due date:
% Done: 0%
Estimated time:
Created: 08/01/2018 12:11 pm
Updated: 08/30/2018 03:52 pm
Likelihood: 3 - Occasional
Severity: 4 - Crash / Wrong Results
Found in version: 2.12.3
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
Here is the e-mail describing the bug. Hello, We have found a possible error in the Alegra generated Exodus data in VisIt when using the Exodus Reader in multiple VisIt versions including 2.12.3 and 2.13.0 When turning of the second elment block VisIt gives and error message. "ERROR: Pseudocolor: () viewer: The pipeline object is being used improperly." Is this a know problem with a known workaround? We have sample data available to demonstrate this issue. We also had to load the data without using the Alegra preset in the Exodus reader or it would not even generate a pseudocolor plot. I have attempted to attach a 2 partition exodus file of 12 elements.If the attachment does not go through, then please contact me for the data. Thanks, Joe ~~~~~~~~~Joseph G. Hennessey Ph.D., SAIC, Team SAIC HITS Army Research Lab DOD Supercomputing Resource Center (ARL DSRC) ARL DSRC HITS SAIC (SAIC) Bldg. 120 , C214Voice: 410278-3619Email: joseph.g.hennessey2.ctr@mail.mil
Comments:
I've emailed user twice about this issue. Since there has been no response, I am moving resolution to a later release.Analysis of the issue...I have looked at your file and see some issues with the naming conventions chosen for material specifc quantities.Note: The Exodus file format, AFAIK, does nothing to capture information regarding material volume fractions or variables that have materialspecific values. This is all deduced by the way things are named in the file.We can open your file and plot materials fine byCreating a .visit file with contents...!NBLOCKS 2region2.exo.2.0region2.exo.2.1Open as...Open file as type ExodusHit Set default open optionsSelect custom material conventionsdefine the string, %s@n?'&VOLFRC%d&n&':'VOID_FRC': for "Namescheme for material volume fractions" However, only the Density variable will work with materialspecific quantities. A few other variables there, ECON1, PRESS1/PRESSURE, TEMP1/TEMPERATURE do not follow a sufficiently simple naming convention that VisIt can deduce their relationships to each other or the associated materials.To correct, the material specific variables must have the same root name as the "overall" variable. So, you would have to do something like...PRESSURE1/PRESSURE, TEMPERATURE1/TEMPERATUREAnd, I really have no idea what ECON1 might be paired with.
brugger1
commented
5 years ago
Here is the e-mail describing the bug. Hello, We have found a possible error in the Alegra generated Exodus data in VisIt when using the Exodus Reader in multiple VisIt versions including 2.12.3 and 2.13.0 When turning of the second elment block VisIt gives and error message. "ERROR: Pseudocolor: () viewer: The pipeline object is being used improperly." Is this a know problem with a known workaround? We have sample data available to demonstrate this issue. We also had to load the data without using the Alegra preset in the Exodus reader or it would not even generate a pseudocolor plot. I have attempted to attach a 2 partition exodus file of 12 elements.If the attachment does not go through, then please contact me for the data. Thanks, Joe
~~~~~~~~~Joseph G. Hennessey Ph.D., SAIC, Team SAIC HITS Army Research Lab DOD Supercomputing Resource Center (ARL DSRC) ARL DSRC HITS SAIC (SAIC) Bldg. 120 , C214Voice: 410278-3619Email: joseph.g.hennessey2.ctr@mail.mil-----------------------REDMINE MIGRATION----------------------- This ticket was migrated from Redmine. As such, not all information was able to be captured in the transition. Below is a complete record of the original redmine ticket.
Ticket number: 3192 Status: Pending Project: VisIt Tracker: Bug Priority: High Subject: Bug reading Exodus files. Assigned to: Kathleen Biagas Category: - Target version: 2.13.4 Author: Eric Brugger Start: 08/01/2018 Due date: % Done: 0% Estimated time: Created: 08/01/2018 12:11 pm Updated: 08/30/2018 03:52 pm Likelihood: 3 - Occasional Severity: 4 - Crash / Wrong Results Found in version: 2.12.3 Impact: Expected Use: OS: All Support Group: Any Description: Here is the e-mail describing the bug. Hello, We have found a possible error in the Alegra generated Exodus data in VisIt when using the Exodus Reader in multiple VisIt versions including 2.12.3 and 2.13.0 When turning of the second elment block VisIt gives and error message. "ERROR: Pseudocolor: () viewer: The pipeline object is being used improperly." Is this a know problem with a known workaround? We have sample data available to demonstrate this issue. We also had to load the data without using the Alegra preset in the Exodus reader or it would not even generate a pseudocolor plot. I have attempted to attach a 2 partition exodus file of 12 elements.If the attachment does not go through, then please contact me for the data. Thanks, Joe
~~~~~~~~~Joseph G. Hennessey Ph.D., SAIC, Team SAIC HITS Army Research Lab DOD Supercomputing Resource Center (ARL DSRC) ARL DSRC HITS SAIC (SAIC) Bldg. 120 , C214Voice: 410278-3619Email: joseph.g.hennessey2.ctr@mail.milComments: I've emailed user twice about this issue. Since there has been no response, I am moving resolution to a later release.Analysis of the issue...I have looked at your file and see some issues with the naming conventions chosen for material specifc quantities.Note: The Exodus file format, AFAIK, does nothing to capture information regarding material volume fractions or variables that have materialspecific values. This is all deduced by the way things are named in the file.We can open your file and plot materials fine byCreating a .visit file with contents...!NBLOCKS 2region2.exo.2.0region2.exo.2.1Open as...Open file as type ExodusHit Set default open optionsSelect custom material conventionsdefine the string, %s@n?'&VOLFRC%d&n&':'VOID_FRC': for "Namescheme for material volume fractions" However, only the Density variable will work with materialspecific quantities. A few other variables there, ECON1, PRESS1/PRESSURE, TEMP1/TEMPERATURE do not follow a sufficiently simple naming convention that VisIt can deduce their relationships to each other or the associated materials.To correct, the material specific variables must have the same root name as the "overall" variable. So, you would have to do something like...PRESSURE1/PRESSURE, TEMPERATURE1/TEMPERATUREAnd, I really have no idea what ECON1 might be paired with.