[Paraview-developers] finishing idx reader plugin
Ali Moeinvaziri
moeinvaz at gmail.com
Thu Feb 27 18:14:07 EST 2014
It seems like it's not going through with 2 attachments.
I'll send them one at a time.
-AM
On Thu, Feb 27, 2014 at 3:41 PM, Ali Moeinvaziri <moeinvaz at gmail.com> wrote:
> I see now. Sorry :-)
>
> Here it is. The entire data is about 530M. If you still want it
> I'll be happy to send it. There are two parts into data. One is
> binary (the biggest size), plus a small 'header' text file which
> I'll include that for now.
>
>
> On Thu, Feb 27, 2014 at 3:29 PM, Utkarsh Ayachit <
> utkarsh.ayachit at kitware.com> wrote:
>
>> Sorry, my bad. By upper part, I mean like the one attached. You may
>> also want to expand the nodes in the tree, if there are any. This
>> gives me information about data types. Alternatively, just send me the
>> data.
>>
>> On Thu, Feb 27, 2014 at 5:23 PM, Ali Moeinvaziri <moeinvaz at gmail.com>
>> wrote:
>> > Here is the right hand side of the screen.
>> > -AM
>> >
>> >
>> >
>> > On Thu, Feb 27, 2014 at 3:19 PM, Ali Moeinvaziri <moeinvaz at gmail.com>
>> wrote:
>> >>
>> >> Oops. Here is one from the upper part. I'll be more than happy to send
>> >> a complete snapshot. But, last time I did, it didn't pass the list
>> server.
>> >> The
>> >> entire image would be about 340KB. Maybe I should send one from the
>> >> right hand side, for completeness. I'll do that in the next e-mail.
>> >>
>> >> -AM
>> >>
>> >>
>> >>
>> >> On Thu, Feb 27, 2014 at 3:07 PM, Utkarsh Ayachit
>> >> <utkarsh.ayachit at kitware.com> wrote:
>> >>>
>> >>> I was interested more in the top-part of that panel :). that's what's
>> >>> telling us the data type. The "unsigned char" is just the type for the
>> >>> data arrays.
>> >>>
>> >>> On Thu, Feb 27, 2014 at 4:08 PM, Ali Moeinvaziri <moeinvaz at gmail.com>
>> >>> wrote:
>> >>> > Hi,
>> >>> >
>> >>> > Attached, please find a snapshot of information panel, as you
>> >>> > requested.
>> >>> > I hope this e-mail goes through, with the attachment (48K).
>> >>> >
>> >>> > Cheers,
>> >>> > -AM
>> >>> >
>> >>> >
>> >>> > On Thu, Feb 27, 2014 at 1:07 PM, Utkarsh Ayachit
>> >>> > <utkarsh.ayachit at kitware.com> wrote:
>> >>> >>
>> >>> >> Can you send the screen shot of the Information panel please?
>> >>> >>
>> >>> >> On Thu, Feb 27, 2014 at 3:05 PM, moeinvaz <moeinvaz at gmail.com>
>> wrote:
>> >>> >> > I see "unsigned char" for Data Type. Now, the IDX is visible
>> >>> >> > in volume under other programs, like visit and visus. Any way to
>> >>> >> > set Volume in code or force representation to Volume?
>> >>> >> >
>> >>> >> > Thanks,
>> >>> >> > -AM
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> > On 02/27/2014 12:58 PM, Utkarsh Ayachit wrote:
>> >>> >> >>
>> >>> >> >> I presume IDX is not producing data that's volume render-able.
>> What
>> >>> >> >> is
>> >>> >> >> the "Information" panel saying for the data type that's loaded.
>> >>> >> >>
>> >>> >> >> Utkarsh
>> >>> >> >>
>> >>> >> >> On Thu, Feb 27, 2014 at 2:53 PM, moeinvaz <moeinvaz at gmail.com>
>> >>> >> >> wrote:
>> >>> >> >>>
>> >>> >> >>> Hi,
>> >>> >> >>>
>> >>> >> >>> Thanks for replying.
>> >>> >> >>>
>> >>> >> >>> After running paraview and loading the IDX file, the only
>> >>> >> >>> representations available (under properties) are:
>> >>> >> >>>
>> >>> >> >>> 3D Glyphs
>> >>> >> >>> Outline
>> >>> >> >>> Points
>> >>> >> >>> Surface
>> >>> >> >>> Surgace With Edges
>> >>> >> >>> Wireframe
>> >>> >> >>>
>> >>> >> >>> There is no "Volume" to change representation to. I guess I
>> have
>> >>> >> >>> to add it in code or xml first. I'm still browsing the web on
>> >>> >> >>> how to do that. Is there any quick link/page on how to make
>> this
>> >>> >> >>> happen?
>> >>> >> >>>
>> >>> >> >>> Thanks,
>> >>> >> >>> -AM
>> >>> >> >>>
>> >>> >> >>>
>> >>> >> >>> On 02/27/2014 10:54 AM, Utkarsh Ayachit wrote:
>> >>> >> >>>>
>> >>> >> >>>>
>> >>> >> >>>> Have you tried changing the representation type to "Volume"?
>> >>> >> >>>>
>> >>> >> >>>> On Wed, Feb 26, 2014 at 6:43 PM, moeinvaz <moeinvaz at gmail.com
>> >
>> >>> >> >>>> wrote:
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>> Hi,
>> >>> >> >>>>>
>> >>> >> >>>>> The previous e-mail apparently was not delivered due to the
>> >>> >> >>>>> large size of attachment. I'll be more than happy to send
>> >>> >> >>>>> the image to individual e-mail address(es) if anybody would
>> >>> >> >>>>> like to see it.
>> >>> >> >>>>>
>> >>> >> >>>>> Meanwhile, if you can point me to the right direction, I
>> >>> >> >>>>> appreciate it.
>> >>> >> >>>>>
>> >>> >> >>>>> Regards,
>> >>> >> >>>>> -AM
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>> On 02/14/2014 09:48 AM, Ali Moeinvaziri wrote:
>> >>> >> >>>>>>
>> >>> >> >>>>>>
>> >>> >> >>>>>>
>> >>> >> >>>>>> Hi,
>> >>> >> >>>>>>
>> >>> >> >>>>>> I have a partially working plugin to read IDX data in. It's
>> >>> >> >>>>>> possible
>> >>> >> >>>>>> to visualize data one slice at a time, by applying slice
>> >>> >> >>>>>> filter.
>> >>> >> >>>>>> However,
>> >>> >> >>>>>> I cannot see the entire volume in paraview. Attached is an
>> >>> >> >>>>>> image
>> >>> >> >>>>>> after
>> >>> >> >>>>>> applying the slice filter. Is there any procedure or
>> tricks on
>> >>> >> >>>>>> using
>> >>> >> >>>>>> vtk?
>> >>> >> >>>>>>
>> >>> >> >>>>>> I appreciate any hints.
>> >>> >> >>>>>> -AM
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>> _______________________________________________
>> >>> >> >>>>> Paraview-developers mailing list
>> >>> >> >>>>> Paraview-developers at paraview.org
>> >>> >> >>>>>
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>> >>> >
>> >>> >
>> >>
>> >>
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20140227/53a55726/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: visus.idx
Type: application/octet-stream
Size: 209 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20140227/53a55726/attachment.obj>
More information about the Paraview-developers
mailing list