MantisBT - ParaView |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0011087 | ParaView | Bug | public | 2010-08-03 15:27 | 2010-08-03 17:29 |
|
| Reporter | Alan Scott | |
| Assigned To | | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | won't fix | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Target Version | 3.10 | Fixed in Version | | |
| Project | |
| Topic Name | |
| Type | |
|
| Summary | 0011087: Data is bad for raw image files |
| Description | ParaView trunk, local server, windows.
Download the file aneurism.raw from http://www.gris.uni-tuebingen.de/edu/areas/scivis/volren/datasets/datasets.html. [^]
Although not necessary, this bug is obvious if you open the Color Editor, then change Choose Preset to the Blue to Red rainbow.
You must follow the following steps, or the bug goes away.
Open with ParaView, Data Scalar Type is Unsigned Char, Data extents are 0-255, 0-255, 0-255. Apply.
Slice, Apply. Turn off show plane. Turn off eyeball for aneurism.raw dataset.
Click on the Color Legend.
Bug - notice that we are just seeing a grayscale, from white to black. But, there is no black, gray or white in the selected color map!
I am marking this as important, since it is incorrectly changing how data is represented.
|
| Steps To Reproduce | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | 0011090 | closed | David Partyka | Color legend misleading when not mapping scalars | | related to | 0011091 | closed | David Partyka | Slice representation does not turn off map scalars |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2010-08-03 15:27 | Alan Scott | New Issue | |
| 2010-08-03 15:30 | Alan Scott | Note Added: 0021615 | |
| 2010-08-03 15:37 | Utkarsh Ayachit | Note Added: 0021616 | |
| 2010-08-03 15:37 | Utkarsh Ayachit | Priority | high => normal |
| 2010-08-03 15:37 | Utkarsh Ayachit | Target Version | 3.8.1 => 3.10 |
| 2010-08-03 16:09 | Alan Scott | Note Added: 0021617 | |
| 2010-08-03 16:25 | Utkarsh Ayachit | Note Added: 0021618 | |
| 2010-08-03 16:25 | Utkarsh Ayachit | Status | backlog => closed |
| 2010-08-03 16:25 | Utkarsh Ayachit | Resolution | open => won't fix |
| 2010-08-03 17:17 | Ken Moreland | Relationship added | related to 0011090 |
| 2010-08-03 17:28 | Ken Moreland | Relationship added | related to 0011091 |
| 2010-08-03 17:29 | Ken Moreland | Note Added: 0021620 | |
|
Notes |
|
|
(0021615)
|
|
Alan Scott
|
|
2010-08-03 15:30
|
|
|
Ah - I forgot to add that if you try to select points on the surface, then turn on point label visibility on the Selection Inspector for ImageFile, you just get grumbling in the output window. |
|
|
|
(0021616)
|
|
Utkarsh Ayachit
|
|
2010-08-03 15:37
|
|
This is because if the data has unsigned char, ParaView directly uses that data array as the color, instead of using a lookuptable to map the value to color.
Go to Display tab and toggle "Map Scalars" to force the use the LUT for color mapping. |
|
|
|
(0021617)
|
|
Alan Scott
|
|
2010-08-03 16:09
|
|
|
This makes sense. In this case, why not close this bug? |
|
|
|
(0021618)
|
|
Utkarsh Ayachit
|
|
2010-08-03 16:25
|
|
|
Closing as per Alan's comments. |
|
|
|
(0021620)
|
|
Ken Moreland
|
|
2010-08-03 17:29
|
|
|
This behavior itself may be correct, but there are a couple of other poor behaviors that lead to confusion. I added two related bugs about them. |
|