[Paraview] proper formatting of 2D data

[Szasz Robert]

Thank you Burlen, I just filed a bug report this morning. I will also 
adjust the export routines to avoid negative spacings for the time being.
Robert


On 2014-09-19 18:24, Burlen Loring wrote:
> Hi Robert,
>
> Good one! The slice rep uses GPU textures and this behavior looks a 
> bug in the logic that sets up the texture. You should file a bug report.
>
> There's an easy workaround. Convert to a positive spacing and adjust 
> the origin accordinigly. The data will the occupy the same region. 
> Here's how your file looks then:
>
> --8<--
> # vtk DataFile Version 2.0
> testing
> ASCII
> DATASET STRUCTURED_POINTS
> DIMENSIONS 3 4 1
> ORIGIN 0.0 -2.25 0.0
> SPACING 0.5 0.75 1.0
> POINT_DATA 12
> SCALARS test float
> LOOKUP_TABLE default
> 0.0
> 1.0
> 2.0
> 1.0
> 2.0
> 3.0
> 2.0
> 3.0
> 4.0
> 3.0
> 4.0
> 5.0
> -->8--
>
> Burlen
>
> On 09/18/2014 11:56 PM, Robert-Zoltan Szasz wrote:
>> Hi,
>>
>> I tried to visualize 2D structured point data when I observed a 
>> strange behavior. If the spacing in Y direction is negative, the data 
>> is flipped upside-down in 'Slice' representation mode but shown 
>> properly as a  'Surface' representation. Tried in v. 4.0.1 and 4.2rc1 
>> on Linux 64 bit. Here is a small VTK file to test:
>>
>> --8<--
>> # vtk DataFile Version 2.0
>> testing
>> ASCII
>> DATASET STRUCTURED_POINTS
>> DIMENSIONS 3 4 1
>> ORIGIN 0.0 0.0 0.0
>> SPACING 0.5 -0.75 1.0
>> POINT_DATA 12
>> SCALARS test float
>> LOOKUP_TABLE default
>> 0.0
>> 1.0
>> 2.0
>> 1.0
>> 2.0
>> 3.0
>> 2.0
>> 3.0
>> 4.0
>> 3.0
>> 4.0
>> 5.0
>> -->8--
>>
>> I am wondering if I missed something when formatting the file or if 
>> you have any ideas how to avoid this behavior?
>> Thanks,
>> Robert
>>
>
>
>