[Paraview] image data extents are not displayed in Information tab
Michael Jackson
mike.jackson at bluequartz.net
Tue Oct 28 08:16:39 EDT 2008
vtkImageAlgorithm
_________________________________________________________
Mike Jackson mike.jackson at bluequartz.net
BlueQuartz Software www.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Oct 28, 2008, at 5:31 AM, Dominik Szczerba wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> One more question: where do you derive your reader from (maybe the
> parent class sets something for you)?
>
> Dominik
>
> Dominik Szczerba wrote:
>> Thanks Mike, but this is exactly what I have.
>> Are you sure you see both bounds and extents in Information?
>>
>> Dominik
>>
>> Michael Jackson wrote:
>>> Not sure if it is any help but here is a code snippet from my own
>>> HDF5
>>> image reader code:
>>
>>> outInfo->Set( vtkDataObject::ORIGIN(), DataOrigin, 3 );
>>> outInfo->Set( vtkDataObject::SPACING(), DataSpacing, 3 );
>>> this->DataExtent[0] = this->DataExtent[2] = this->DataExtent[4] =
>>> 0;
>>> this->DataExtent[1] = xDim-1;
>>> this->DataExtent[3] = yDim-1;
>>> this->DataExtent[5] = zDim-1;
>>> outInfo->Set( vtkStreamingDemandDrivenPipeline::WHOLE_EXTENT(),
>>> DataExtent, 6 );
>>> outInfo->Set( vtkStreamingDemandDrivenPipeline::UPDATE_EXTENT(),
>>> DataExtent, 6 );
>>
>>
>>> _________________________________________________________
>>> Mike Jackson mike.jackson at bluequartz.net
>>> BlueQuartz Software www.bluequartz.net
>>> Principal Software Engineer Dayton, Ohio
>>
>>
>>
>>> On Oct 27, 2008, at 7:55 PM, Dominik Szczerba wrote:
>>
>>> What else then WHOLE_EXTENT, UPDATE_EXTENT and SetExtent and do I
>>> have
>>> to fill in RequestInformation/RequestData of my plugin reader
>>> (derived
>>> from vtkImageAlgorithm) in order for Paraview to see the dataset's
>>> extents? Only bounds are displayed in the Information tab, while for
>>> native file formats there is also extents. But when I save the
>>> file in
>>> legacy format for a test the extent is written correctly, so it WAS
>>> known to Paraview, only not displayed properly. What is wrong?
>>
>> _______________________________________________
>> ParaView mailing list
>> ParaView at paraview.org
>> http://www.paraview.org/mailman/listinfo/paraview
>>
>
> - --
> Dominik Szczerba, Ph.D.
> Computational Physics Group
> Foundation for Research
> on Information Technologies in Society
> http://www.itis.ethz.ch
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.4-svn0 (GNU/Linux)
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
>
> iD4DBQFJBtwD/EBMh9bUuzIRAkt4AJiAmtXnkid9/9VtfclXmdm3KSujAKC54Zjd
> i/nAY5Ljmp3e5Tzr+kLAqw==
> =eliP
> -----END PGP SIGNATURE-----
More information about the ParaView
mailing list