Re: [Paraview] Input Editor - Cramped Input Port Selection

[Christian Werner]

I vote yes for the mockup!

Utkarsh Ayachit wrote:

I agree, the pipeline preview is confusing and for the most part
useless. Unless people object, I'd vote for removing it as well.

Attached is a sample mockup. In case of filters like Append which have
single input port, but multiple input connections, the use can type in
a comma separated list of the inputs in the input field or select
multiple items using the pipeline browser in the dialog.

Utkarsh

On Mon, Mar 15, 2010 at 11:22 AM, Christian Werner
 wrote:
  

As a user, may I present three suggestions, two of which should be very easy
and still yield an improvement.

1) remove the Pipeline Preview: This may be rude because it's somehow nice.
But then again, you cannot change what happens to the pipeline anyway. Also,
I don't think one would change his mind about the selection of the inputs
just because the Pipeline Preview shows something unsuspected. Most of the
time the user knows what he is doing and wants to quickly and easily select
his inputs. The actual layout works against this intend. The Pipeline
Preview can be included again once a nice layout is found.

2) hide the Pipeline Preview and make it visible if the user wants to

3) change the layout such that the inputs are shown on top and let QT manage
the form's height. You normally don't use so many inputs, so this  most
probably would never lead to problems.


Best regards,
Christian

Paul Edwards wrote:


One simple fix would be to make sure that the preview window isn't
selectable.  A lot of my users get confused thinking one box is for
the input and the other as the source.

Regards,
Paul

On 12 March 2010 19:10, Utkarsh Ayachit 
wrote:

  

I cannot agree more. I am going to take a stab and fixing this before
3.8. We've just had too many complaints about this dialog to keep on
delaying this.

Utkarsh

On Fri, Mar 12, 2010 at 2:00 PM, Christian Werner
 wrote:



Hello!

I wonder why the input port selection is so cramped in the input editor.
It
is really bad that you cannot actually read out the selections you make
without moving the scrollbar. Then, after scrolling, you cannot change
the
other input without scrolling back. This really steals your time. On the
other hand there is that pipeline preview which is nice to see but
honestly
I'd instantly trade it away for a better overview on my inputs. I have
attached a picture that shows the situation on my PC.

By the way, doesn't anyone have any idea about my last issue? (no
cell/point
data in imported ITK volumes):

  

"Create Cell or Point Data out of Image"



Best regards,
Christian

___
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview



  

___
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview










___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Input Editor - Cramped Input Port Selection

[Jérôme]

My 2 cents on this :
It seems to me that the input list is provided in alphabetical order. In my
case I have a lot of custom plugins that take 2 inputs, one being
vtkImageData
and the other a vtkPolyData (such a stream tracer with custom source).
Depending on wich is the 'principal' input, the default input setting of
this
panel have non-corresponding type. For instance, the Image input is set
to an existing PointSet.

I don't know if I am clear enough, but maybe you can try with the stream
tracer
with custom source: in the current configuration, there is no problem. But I
am
quite sure that if you rename the 2nd input "Source" to "ArbitrarySource" in
the
filters.xml, you will understand this tiny problem.

Jerome

2010/3/16 Christian Werner 

> I vote yes for the mockup!
>
> Utkarsh Ayachit wrote:
>
>> I agree, the pipeline preview is confusing and for the most part
>> useless. Unless people object, I'd vote for removing it as well.
>>
>> Attached is a sample mockup. In case of filters like Append which have
>> single input port, but multiple input connections, the use can type in
>> a comma separated list of the inputs in the input field or select
>> multiple items using the pipeline browser in the dialog.
>>
>> Utkarsh
>>
>> On Mon, Mar 15, 2010 at 11:22 AM, Christian Werner
>>  wrote:
>>
>>
>>> As a user, may I present three suggestions, two of which should be very
>>> easy
>>> and still yield an improvement.
>>>
>>> 1) remove the Pipeline Preview: This may be rude because it's somehow
>>> nice.
>>> But then again, you cannot change what happens to the pipeline anyway.
>>> Also,
>>> I don't think one would change his mind about the selection of the inputs
>>> just because the Pipeline Preview shows something unsuspected. Most of
>>> the
>>> time the user knows what he is doing and wants to quickly and easily
>>> select
>>> his inputs. The actual layout works against this intend. The Pipeline
>>> Preview can be included again once a nice layout is found.
>>>
>>> 2) hide the Pipeline Preview and make it visible if the user wants to
>>>
>>> 3) change the layout such that the inputs are shown on top and let QT
>>> manage
>>> the form's height. You normally don't use so many inputs, so this  most
>>> probably would never lead to problems.
>>>
>>>
>>> Best regards,
>>> Christian
>>>
>>> Paul Edwards wrote:
>>>
>>>
 One simple fix would be to make sure that the preview window isn't
 selectable.  A lot of my users get confused thinking one box is for
 the input and the other as the source.

 Regards,
 Paul

 On 12 March 2010 19:10, Utkarsh Ayachit 
 wrote:



> I cannot agree more. I am going to take a stab and fixing this before
> 3.8. We've just had too many complaints about this dialog to keep on
> delaying this.
>
> Utkarsh
>
> On Fri, Mar 12, 2010 at 2:00 PM, Christian Werner
>  wrote:
>
>
>
>> Hello!
>>
>> I wonder why the input port selection is so cramped in the input
>> editor.
>> It
>> is really bad that you cannot actually read out the selections you
>> make
>> without moving the scrollbar. Then, after scrolling, you cannot change
>> the
>> other input without scrolling back. This really steals your time. On
>> the
>> other hand there is that pipeline preview which is nice to see but
>> honestly
>> I'd instantly trade it away for a better overview on my inputs. I have
>> attached a picture that shows the situation on my PC.
>>
>> By the way, doesn't anyone have any idea about my last issue? (no
>> cell/point
>> data in imported ITK volumes):
>>
>>
>>
>>> "Create Cell or Point Data out of Image"
>>>
>>>
>>>
>> Best regards,
>> Christian
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.paraview.org/mailman/listinfo/paraview
>>
>>
>>
>>
>>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
>
>

>>> 
>>>
>>>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensour

Re: [Paraview] Input Editor - Cramped Input Port Selection

[Paul Edwards]

you get my vote!

On 15 March 2010 23:58, Utkarsh Ayachit  wrote:
> I agree, the pipeline preview is confusing and for the most part
> useless. Unless people object, I'd vote for removing it as well.
>
> Attached is a sample mockup. In case of filters like Append which have
> single input port, but multiple input connections, the use can type in
> a comma separated list of the inputs in the input field or select
> multiple items using the pipeline browser in the dialog.
>
> Utkarsh
>
> On Mon, Mar 15, 2010 at 11:22 AM, Christian Werner
>  wrote:
>> As a user, may I present three suggestions, two of which should be very easy
>> and still yield an improvement.
>>
>> 1) remove the Pipeline Preview: This may be rude because it's somehow nice.
>> But then again, you cannot change what happens to the pipeline anyway. Also,
>> I don't think one would change his mind about the selection of the inputs
>> just because the Pipeline Preview shows something unsuspected. Most of the
>> time the user knows what he is doing and wants to quickly and easily select
>> his inputs. The actual layout works against this intend. The Pipeline
>> Preview can be included again once a nice layout is found.
>>
>> 2) hide the Pipeline Preview and make it visible if the user wants to
>>
>> 3) change the layout such that the inputs are shown on top and let QT manage
>> the form's height. You normally don't use so many inputs, so this  most
>> probably would never lead to problems.
>>
>>
>> Best regards,
>> Christian
>>
>> Paul Edwards wrote:
>>>
>>> One simple fix would be to make sure that the preview window isn't
>>> selectable.  A lot of my users get confused thinking one box is for
>>> the input and the other as the source.
>>>
>>> Regards,
>>> Paul
>>>
>>> On 12 March 2010 19:10, Utkarsh Ayachit 
>>> wrote:
>>>

 I cannot agree more. I am going to take a stab and fixing this before
 3.8. We've just had too many complaints about this dialog to keep on
 delaying this.

 Utkarsh

 On Fri, Mar 12, 2010 at 2:00 PM, Christian Werner
  wrote:

>
> Hello!
>
> I wonder why the input port selection is so cramped in the input editor.
> It
> is really bad that you cannot actually read out the selections you make
> without moving the scrollbar. Then, after scrolling, you cannot change
> the
> other input without scrolling back. This really steals your time. On the
> other hand there is that pipeline preview which is nice to see but
> honestly
> I'd instantly trade it away for a better overview on my inputs. I have
> attached a picture that shows the situation on my PC.
>
> By the way, doesn't anyone have any idea about my last issue? (no
> cell/point
> data in imported ITK volumes):
>
>>
>> "Create Cell or Point Data out of Image"
>>
>
> Best regards,
> Christian
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
>

 ___
 Powered by www.kitware.com

 Visit other Kitware open-source projects at
 http://www.kitware.com/opensource/opensource.html

 Please keep messages on-topic and check the ParaView Wiki at:
 http://paraview.org/Wiki/ParaView

 Follow this link to subscribe/unsubscribe:
 http://www.paraview.org/mailman/listinfo/paraview


>>
>>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] New version of the "supercomputer" tutorial available

[Takuya OSHIMA]

Hi,

It may have taken a bit too long, but we are pleased to inform that we
have finished the Japanese translation of The ParaView Tutorial for
ParaView 3.6 and it is now publicly available.

http://oshima.eng.niigata-u.ac.jp/ParaViewTutorial-jp.pdf

We heard that the previous translation (the SC08 version) was used not
only by indivisuals but also for in-house teachings in some industrial
companies. Hence we believe that the translation also helps to enlarge
the community as well.

Many thnaks to Kenneth Moreland for the nice tutorial and providing
the LaTeX sources and images.

p.s.
Am I allowd to create an account and update the wiki
http://paraview.org/Wiki/The_ParaView_Tutorial
or can I ask to somebody?

Takuya

Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN

From: "Moreland, Kenneth" 
Subject: [Paraview] New version of the "supercomputer" tutorial available
Date: Fri, 18 Sep 2009 14:49:22 -0600

> Hi folks,
> 
> I just wanted to let everyone know that there is a new version of the 
> "supercomputer" tutorial available on the Wiki.  Because the tutorial is 
> fairly general purpose, I've actually taken supercomputing out of the name 
> and simply call it The ParaView Tutorial.
> 
> http://www.paraview.org/Wiki/The_ParaView_Tutorial
> 
> Changes for this version of the tutorial include:
> 
> 
>  *   Updated for ParaView version 3.6.
>  *   Exercises broken into smaller chunks.
>  *   Added introduction to Python scripting.
> 
> In the past, readers have asked for the source materials of the document, 
> mainly to perform translations.  I have included a link to the Wiki page 
> where you can download the LaTeX source and images.  As before, anyone who 
> wishes to make a translation is encouraged to do so.
> 
> Enjoy,
> 
> -Ken
> 
>  Kenneth Moreland
> ***  Sandia National Laboratories
> ***
> *** *** ***  email: kmo...@sandia.gov
> **  ***  **  phone: (505) 844-8919
> ***  web:   http://www.cs.unm.edu/~kmorel
> 
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

[Paraview] tensor representation in Paraview

[paolo crosetto]

Good morning,

I have basic question: when calculating the gradient of a vector the output are 
9 scalars ranging from 0 to 8. What do they represent? Are they ordered 
linewise, columnwise or first diagonal entries... ?
Thanks for the help

Paolo Crosetto
  
_
Scatta, ritocca e condividi le tue foto online. Gratis per te
http://www.windowslive.it/foto.aspx___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Use existing texture map for 3D surface

[Dressler, Christian]

Hi Utkarsh,

could you give me some hints or catchwords how to realize that filter? Perhaps 
a link to tutorial you recommend?


Best,

Christian

-Ursprüngliche Nachricht-
Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] 
Gesendet: Freitag, 12. März 2010 16:13
An: Dressler, Christian
Cc: paraview@paraview.org
Betreff: Re: [Paraview] Use existing texture map for 3D surface

The problem is that the uv array needs to be marked as "Texture"
attribute for the PointData. You can write a PythonProgrammableFilter
which generate an output with the Texture coords setup correctly. Let
me know if you need help with that. Also remember this filter will
have to combine the two "u" and "v" arrays produced by
vtkTableToPoints into a single array with 2 components.

Utkarsh

On Fri, Mar 12, 2010 at 10:05 AM, Dressler, Christian
 wrote:
> Hi Eric,
>
> Unfortunately this does not work. Neither for the point cloud, nor for the 
> surface. It does only work after generating a map by paraview, but this is 
> the wrong map.
>
> I also tried to rename the columns header the way paraview does, but it did 
> not work. I am looking for an option similar to the "table to points filter", 
> where I am asked which column has which meaning.
>
> Thanks,
>
> Christian
>
>
> -Ursprüngliche Nachricht-
> Von: Eric E. Monson [mailto:emon...@cs.duke.edu]
> Gesendet: Freitag, 12. März 2010 15:54
> An: Dressler, Christian
> Cc: paraview@paraview.org
> Betreff: Re: [Paraview] Use existing texture map for 3D surface
>
> Hey Christian,
>
> If your data already has valid texture coordinates, highlight your surface in 
> the Pipeline Browser. You should be able to go to the Display tab of the 
> Object Inspector and in the Color section there is an Apply Texture combo box 
> that should not be grayed-out if everything is ready for texturing. If you 
> pull down to Load... it will let you load your texture image and you should 
> see it on your surface.
>
> Let us know if you have problems,
> -Eric
>
> --
> Eric E Monson
> Duke Visualization Technology Group
>
>
> On Mar 12, 2010, at 7:51 AM, Dressler, Christian wrote:
>
>>
>> Hi,
>>
>> I am trying to reconstruct data generated by a surface scanner with 
>> paraview. The data is structured as xyzuv arrays. I managed to calculate the 
>> surface by using the filters "Table to points" and "Delaunay 2D".
>>
>> But I could not figure out, how to apply the texture to the surface. The 
>> uv-coordinates have the same format as the maps generated by the paraview 
>> texture filters (normalized position of bitmap).
>>
>> How can I make paraview using my own texture map?
>>
>>
>> Best,
>>
>> Christian
>> 
>> Dipl.-Ing. Christian Dressler
>> Research Associate  | Working Group - S-DICOM Solutions
>>
>> Universität Leipzig | Faculty of Medicine
>> Innovation Center Computer Assisted Surgery (ICCAS)
>> Semmelweisstr. 14
>> D - 04103 Leipzig
>> Germany
>>
>> phone  +49 (0) 341 97 - 12018
>> fax    +49 (0) 341 97 - 12009
>> christian.dress...@medizin.uni-leipzig.de
>> http://www.iccas.de/?id=430
>> 
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at 
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at: 
>> http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.paraview.org/mailman/listinfo/paraview
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] package .deb

[LUK ShunTim]

Cecile Forella wrote:
> I've problem while doing the debuild instruction :
> 
> Here is the error message :
> 
> /users/mics/forella/Paraview/paraview-3.6.2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:176:
> erreur: braces around scalar initializer for type ‘H5FD_mem_t’
> /users/mics/forella/Paraview/paraview-3.6.2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:176:
> erreur: invalid conversion from ‘haddr_t (*)(const H5FD_t*, H5FD_mem_t)’
> to ‘herr_t (*)(H5FD_t*, haddr_t)’
> /users/mics/forella/Paraview/paraview-3.6.2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:176:
> erreur: invalid conversion from ‘herr_t (*)(H5FD_t*, H5FD_mem_t,
> haddr_t)’ to ‘haddr_t (*)(H5FD_t*)’
> /users/mics/forella/Paraview/paraview-3.6.2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:176:
> erreur: invalid conversion from ‘haddr_t (*)(const H5FD_t*)’ to ‘herr_t
> (*)(H5FD_t*, hid_t, void**)’
> /users/mics/forella/Paraview/paraview-3.6.2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:176:
> erreur: invalid conversion from ‘herr_t (*)(H5FD_t*, H5FD_mem_t, hid_t,
> haddr_t, size_t, void*)’ to ‘herr_t (*)(H5FD_t*, H5FD_mem_t, hid_t,
> haddr_t, size_t, const void*)’
> /users/mics/forella/Paraview/paraview-3.6.2/Utilities/Xdmf2/libsrc/XdmfH5Driver.cxx:176:
> erreur: invalid conversion from ‘herr_t (*)(H5FD_t*, H5FD_mem_t, hid_t,
> haddr_t, size_t, const void*)’ to ‘herr_t (*)(H5FD_t*, hid_t, unsigned
> int)’
> make[3]: *** [Utilities/Xdmf2/libsrc/CMakeFiles/Xdmf.dir/XdmfH5Driver.o]
> Erreur 1


Things built fine for me on debian/sid/amd64. I can't reproduce these
errors.

If you're using the debian (or ubuntu) source packages, maybe you can
get more specific help by asking on a debian/ubuntu list.

Regards,
ST
--
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Use existing texture map for 3D surface

[Utkarsh Ayachit]

Christian,

Sorry I've been meaning to write up a quick  script for you. For
starters take a look at:

http://www.paraview.org/Wiki/Python_Programmable_Filter
http://www.paraview.org/Wiki/Python_recipes

Here's the algorithm:
* Create a new vtkDoubleArray (or another vtkDataArray subclass) with
2 components and number of tuples = number of points.
* Get access the to two input arrays you want to use an texture coordinates.
* Iterate over each value in the two array and insert them as the two
components in the new array
* Set the new array as the TCoords in the output's point data.

Utkarsh

On Tue, Mar 16, 2010 at 6:38 AM, Dressler, Christian
 wrote:
> Hi Utkarsh,
>
> could you give me some hints or catchwords how to realize that filter? 
> Perhaps a link to tutorial you recommend?
>
>
> Best,
>
> Christian
>
> -Ursprüngliche Nachricht-
> Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Gesendet: Freitag, 12. März 2010 16:13
> An: Dressler, Christian
> Cc: paraview@paraview.org
> Betreff: Re: [Paraview] Use existing texture map for 3D surface
>
> The problem is that the uv array needs to be marked as "Texture"
> attribute for the PointData. You can write a PythonProgrammableFilter
> which generate an output with the Texture coords setup correctly. Let
> me know if you need help with that. Also remember this filter will
> have to combine the two "u" and "v" arrays produced by
> vtkTableToPoints into a single array with 2 components.
>
> Utkarsh
>
> On Fri, Mar 12, 2010 at 10:05 AM, Dressler, Christian
>  wrote:
>> Hi Eric,
>>
>> Unfortunately this does not work. Neither for the point cloud, nor for the 
>> surface. It does only work after generating a map by paraview, but this is 
>> the wrong map.
>>
>> I also tried to rename the columns header the way paraview does, but it did 
>> not work. I am looking for an option similar to the "table to points 
>> filter", where I am asked which column has which meaning.
>>
>> Thanks,
>>
>> Christian
>>
>>
>> -Ursprüngliche Nachricht-
>> Von: Eric E. Monson [mailto:emon...@cs.duke.edu]
>> Gesendet: Freitag, 12. März 2010 15:54
>> An: Dressler, Christian
>> Cc: paraview@paraview.org
>> Betreff: Re: [Paraview] Use existing texture map for 3D surface
>>
>> Hey Christian,
>>
>> If your data already has valid texture coordinates, highlight your surface 
>> in the Pipeline Browser. You should be able to go to the Display tab of the 
>> Object Inspector and in the Color section there is an Apply Texture combo 
>> box that should not be grayed-out if everything is ready for texturing. If 
>> you pull down to Load... it will let you load your texture image and you 
>> should see it on your surface.
>>
>> Let us know if you have problems,
>> -Eric
>>
>> --
>> Eric E Monson
>> Duke Visualization Technology Group
>>
>>
>> On Mar 12, 2010, at 7:51 AM, Dressler, Christian wrote:
>>
>>>
>>> Hi,
>>>
>>> I am trying to reconstruct data generated by a surface scanner with 
>>> paraview. The data is structured as xyzuv arrays. I managed to calculate 
>>> the surface by using the filters "Table to points" and "Delaunay 2D".
>>>
>>> But I could not figure out, how to apply the texture to the surface. The 
>>> uv-coordinates have the same format as the maps generated by the paraview 
>>> texture filters (normalized position of bitmap).
>>>
>>> How can I make paraview using my own texture map?
>>>
>>>
>>> Best,
>>>
>>> Christian
>>> 
>>> Dipl.-Ing. Christian Dressler
>>> Research Associate  | Working Group - S-DICOM Solutions
>>>
>>> Universität Leipzig | Faculty of Medicine
>>> Innovation Center Computer Assisted Surgery (ICCAS)
>>> Semmelweisstr. 14
>>> D - 04103 Leipzig
>>> Germany
>>>
>>> phone  +49 (0) 341 97 - 12018
>>> fax    +49 (0) 341 97 - 12009
>>> christian.dress...@medizin.uni-leipzig.de
>>> http://www.iccas.de/?id=430
>>> 
>>>
>>> ___
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at 
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at: 
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.paraview.org/mailman/listinfo/paraview
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at 
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at: 
>> http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.paraview.org/mailman/listinfo/paraview
>>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-top

Re: [Paraview] New version of the "supercomputer" tutorial available

[Utkarsh Ayachit]

Thanks great. You can indeed create a login on the Wiki and update it.

Utkarsh

On Tue, Mar 16, 2010 at 4:47 AM, Takuya OSHIMA
 wrote:
> Hi,
>
> It may have taken a bit too long, but we are pleased to inform that we
> have finished the Japanese translation of The ParaView Tutorial for
> ParaView 3.6 and it is now publicly available.
>
> http://oshima.eng.niigata-u.ac.jp/ParaViewTutorial-jp.pdf
>
> We heard that the previous translation (the SC08 version) was used not
> only by indivisuals but also for in-house teachings in some industrial
> companies. Hence we believe that the translation also helps to enlarge
> the community as well.
>
> Many thnaks to Kenneth Moreland for the nice tutorial and providing
> the LaTeX sources and images.
>
> p.s.
> Am I allowd to create an account and update the wiki
> http://paraview.org/Wiki/The_ParaView_Tutorial
> or can I ask to somebody?
>
> Takuya
>
> Takuya OSHIMA, Ph.D.
> Faculty of Engineering, Niigata University
> 8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN
>
> From: "Moreland, Kenneth" 
> Subject: [Paraview] New version of the "supercomputer" tutorial available
> Date: Fri, 18 Sep 2009 14:49:22 -0600
>
>> Hi folks,
>>
>> I just wanted to let everyone know that there is a new version of the 
>> "supercomputer" tutorial available on the Wiki.  Because the tutorial is 
>> fairly general purpose, I've actually taken supercomputing out of the name 
>> and simply call it The ParaView Tutorial.
>>
>> http://www.paraview.org/Wiki/The_ParaView_Tutorial
>>
>> Changes for this version of the tutorial include:
>>
>>
>>  *   Updated for ParaView version 3.6.
>>  *   Exercises broken into smaller chunks.
>>  *   Added introduction to Python scripting.
>>
>> In the past, readers have asked for the source materials of the document, 
>> mainly to perform translations.  I have included a link to the Wiki page 
>> where you can download the LaTeX source and images.  As before, anyone who 
>> wishes to make a translation is encouraged to do so.
>>
>> Enjoy,
>>
>> -Ken
>>
>>          Kenneth Moreland
>>     ***      Sandia National Laboratories
>> ***
>> *** *** ***  email: kmo...@sandia.gov
>> **  ***  **  phone: (505) 844-8919
>>     ***      web:   http://www.cs.unm.edu/~kmorel
>>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] 64-bit version for MacOS?

[Eric E. Monson]

Hey Karen,

No, the 3.6.1 binary for Intel is i386 architecture. Like Mike said yesterday, 
you'll have to build your own version of Qt 4.6.2 with x86_64 architecture and 
Cocoa, and then build ParaView from source against that Qt build, itself with 
x86_64 arch, too.

I'm not sure if there are any issues with 64-bit ParaView Python support in 
Leopard since for OS X 10.5 you can't get (as far as I know) a 64-bit python 
executable...?

Talk to you later,
-Eric


On Mar 15, 2010, at 9:02 PM, Karen Lee wrote:

> Hi Paraview users and developers,
> 
> I'm wondering if there is a 64-but version of paraview for MacOS. don't seem 
> to see one under 3.6.2. The 3.6.1 one for Macintosh OS X, Tiger and Leopard 
> (Intel) is in 64 bits right?
> 
> Thanks,
> Karen
> ___
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Paraview 3.6.2 / Open MPI 1.4.1: Server Connection Closed! / Server failed to gather information./cslog

[Utkarsh Ayachit]

I am not sure why that could be the case. The only thing that happens
on setting cslog is that each the server process starts writing out an
output log file. Also I am not sure why mpi would hang on attaching a
debugger. Try debugging by just running 2 processes. Is it possible
you have a  broken MPI?

Utkarsh



On Tue, Mar 16, 2010 at 9:54 AM, SCHROEDER, Martin
 wrote:
> hm debugging seems more difficult than i thought. mpirun ssem to hang when 
> the debugging opeion is set.
> i also wonder why this "connection reset by peer" problem doesn't occur when 
> the option "--cslog=somefile" is set...
>
>
> -Ursprüngliche Nachricht-
> Von: SCHROEDER, Martin
> Gesendet: Montag, 15. März 2010 14:33
> An: 'Utkarsh Ayachit'
> Betreff: AW: [Paraview] Paraview 3.6.2 / Open MPI 1.4.1: Server Connection 
> Closed! / Server failed to gather information./cslog
>
> Yes it is possible. I'will try to and send you the output.
> Meanwhile, mpirun sometimes brought back this message:
>
> btl_tcp_frag.c:216:mca_btl_tcp_frag_recv] mca_btl_tcp_frag_recv: readv 
> failed: Connection reset by peer (104)
>
>
>
> -Ursprüngliche Nachricht-
> Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Gesendet: Freitag, 12. März 2010 15:41
> An: SCHROEDER, Martin
> Cc: paraview@paraview.org
> Betreff: Re: [Paraview] Paraview 3.6.2 / Open MPI 1.4.1: Server Connection 
> Closed! / Server failed to gather information./cslog
>
> Is it possible to attach a debugger to the server processes and see where it 
> crashes?
>
> On Fri, Mar 12, 2010 at 7:03 AM, SCHROEDER, Martin  
> wrote:
>> Hello
>> when I'm trying to run paraview (pvserver) on a single host using
>> mpirun with 4 -8 processes, it works.
>> The problem is :
>> when i'm trying to spread pvserver over multiple hosts, using mpirun
>> and a hostfile, the server processes and the client crash when I
>> connect the client to the server.
>>
>> Im'getting these messages in the client's shell:
>>
>> ERROR: In
>> /yatest/cae/src/Paraview3.6.2/ParaView3/Servers/Common/vtkServerConnec
>> tion.cxx,
>> line 67
>> vtkServerConnection (0x1140c30): Server Connection Closed!
>>
>> ERROR: In
>> /yatest/cae/src/Paraview3.6.2/ParaView3/Servers/Common/vtkServerConnec
>> tion.cxx,
>> line 345
>> vtkServerConnection (0x1140c30): Server failed to gather information.
>>
>> If I use the option cslog=/home/.../cstream.log when executing pvserver,
>> it works slowly, but it works on two hosts with 4 processes on each host.
>>
>> Paraview Client and Server are the same Version 3.6.2 Open MPI is
>> 1.4.1
>>
>> Has anyone experienced the same ?
>> Any hint would be great.
>>
>> Mit freundlichen Gruessen / Best regards
>>
>> Martin Schröder, FIEA
>> MTU Aero Engines GmbH
>> Engineering Systems (CAE)
>> Dachauer Str. 665
>> 80995 Muenchen
>> Germany
>>
>> Tel  +49 (0)89  14 89 57 20
>> Fax  +49 (0)89  14 89-96 89 4
>> mailto:martin.schroe...@mtu.de
>> http://www.mtu.de
>>
>>
>>
>> --
>> MTU Aero Engines GmbH
>> Geschaeftsfuehrung/Board of Management: Egon W. Behle, Vorsitzender/CEO; Dr.
>> Rainer Martens, Dr. Stefan Weingartner, Reiner Winkler Vorsitzender
>> des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt
>> Sitz der Gesellschaft/Registered Office: Muenchen
>> Handelsregister/Commercial Register: Muenchen HRB 154230
>>
>> Diese E-Mail sowie ihre Anhänge enthalten MTU-eigene vertrauliche oder
>> rechtlich geschützte Informationen.
>> Wenn Sie nicht der beabsichtigte Empfänger sind, informieren Sie bitte
>> den Absender und löschen Sie diese E-Mail sowie die Anhänge. Das
>> unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet.
>>
>> This e-mail and any attached documents are proprietary to MTU,
>> confidential or protected by law.
>> If you are not the intended recipient, please advise the sender and
>> delete this message and its attachments.
>> Any unauthorised storing, copying or distribution is prohibited.
>>
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.paraview.org/mailman/listinfo/paraview
>>
>>
> --
> MTU Aero Engines GmbH
> Geschaeftsfuehrung/Board of Management: Egon W. Behle, Vorsitzender/CEO; Dr. 
> Rainer Martens, Dr. Stefan Weingartner, Reiner Winkler
> Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus 
> Eberhardt
> Sitz der Gesellschaft/Registered Office: Muenchen
> Handelsregister/Commercial Register: Muenchen HRB 154230
>
> Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder 
> rechtlich geschuetzte Informationen.
> Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den 
> Absender und loeschen Sie diese E-Mail
> sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterle

[Paraview] packaging branded problem

[Eric E. Monson]

Hey all,

I'm having trouble today packaging my branded app on 64-bit Ubuntu. I'm just 
trying to run ccmake to configure, I have  BUILD_SHARED: ON, but it has trouble 
when I turn CMAKE_SKIP_RPATH:ON. It seems to be having trouble expanding 
ParaView_SOURCE_DIR on line 172 of ParaViewMacros.cmake, giving me this error 
during configure stage:

CMake Error: File /Servers/Executables/pv-forward.c.in does not exist.

 CMake Error at 
/home/emonson/Programming/ParaView_cvs/ParaView3/CMake/ParaViewMacros.cmake:172
 (CONFIGURE_FILE):
   configure_file Problem configuring file
 Call Stack (most recent call first):
   
/home/emonson/Programming/ParaView_cvs/ParaView3/CMake/ParaViewBranding.cmake:263
 (add_executable_with_forwarding2)
   MSI_Strip3/CMakeLists.txt:48 (build_paraview_client)

Any clue whether this is something I have set up wrong, or is it a bug? I 
rebuilt paraview yesterday with a new build of Qt, so I'm not sure if I screwed 
something up since this used to work fine.

(CVS 2010-03-15 ParaView, Qt 4.6.2 from source, ffmpeg, CMake 2.6-patch 4)

Thanks,
-Eric

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

[Paraview] reading multiple files

[Paul Edwards]

Hi,

Is there something I need to do to my reader in order to load in
multiple files that I can animate with?  I have put numbers in the
file names and loaded up file.*.dat but stepping the time doesn't work
(and it doesn't show timesteps in the information tab in the object
inspector).

Thanks,
Paul
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Development Install Tree

[Dave Partyka]

Hi Mark,

vtkWrapClientServer should be installed now correctly in the bin dir.
Apparently there was a bug in the install rule that installed it. Thanks for
catching that!

Committer: Dave Partyka 
/cvsroot/ParaView3/ParaView3/Utilities/VTKClientServer/Wrapping/CMakeLists.txt,v
 <--  Utilities/VTKClientServer/Wrapping/CMakeLists.txt

new revision: 1.12; previous revision: 1.11

On Mon, Mar 15, 2010 at 6:08 AM, Mark Olesen wrote:

> On Fri, 2010-03-12 at 13:11 -0500, Dave Partyka wrote:
> > I just tried this on my Debian machine and the biggest executable in
> > my bin dir weighs in at 2.5 MB. Note that this is a Debug build as my
> > Release build tree is a bit out of date at the moment. Also all of the
> > CMake files appear to be in
> > ParaView-3.7.0-Linux-x86_64/lib/paraview-3.7/CMake/ and all of the vtk
> > libs are in in ParaView-3.7.0-Linux-x86_64/lib/paraview-3.7/. So this
> > is really puzzling. Have you tried doing this from a fresh clean
> > build?
>
> I just tried it again (from a fresh build directory and with
> GENERATE_FILTERS_DOCUMENTATION:BOOL=ON instead of "make
> HTMLDocumentation") and it looks a fair bit better. I suspect my
> previous problems might have been from mixing build and install
> directories.
>
> Using cpack, I no long have monster binaries, just that the VPIC lib
> seems to have gone missing:
>
>paraview-real: error while loading shared libraries: libVPIC.so:
>cannot open shared object file: No such file or directory
>
> ... but it is also getting missed for the "make install" target too, so
> the problem is elsewhere. As a stop-gap, sync'ing the library from the
> build directory did the trick.
>
>
> Apart from the inconvenience of using cpack (I really just want to
> create an installed version and not a tar.gz that I have to subsequently
> unpack and rename the directories to suit my own conventions), I'm a
> disconcerted by that fact that the cpack variant also seems to miss
> installing a fair number of files (see attached diff from ls -1R
> outputs).
>
> Apart from various missing headers, the resulting cpack'ed installation
> doesn't work for building plugins later on since it is missing
> vtkWrapClientServer.
>
> make[2]: *** No rule to make target
> `paraview-3.7.0/bin/vtkWrapClientServer', needed by ...
>
>
> The installation with "make install" did work though.
>
>
> This seems to be the current status:
> - use separate build and install directories!
> - use "make install" -- cpack misses too many files and is too clumsy
> for a local install.
> - GENERATE_FILTERS_DOCUMENTATION should work, but doesn't.
> - "make HTMLDocumentation" doesn't seem to work either
>
>
> These tests were made against this commit level:
>
> commit a75e52603fe6c70b36a6a6523f962fc598919a63
> Author: KWSys Robot 
> Date:   Fri Mar 12 05:01:10 2010 +
>
>KWSys Nightly Date Stamp
>
>
>
>
> /mark
>
>
> DISCLAIMER:
> This electronic transmission (and any attachments thereto) is intended
> solely for the use of the addressee(s). It may contain confidential or
> legally privileged information. If you are not the intended recipient of
> this message, you must delete it immediately and notify the sender. Any
> unauthorized use or disclosure of this message is strictly prohibited.
> Faurecia does not guarantee the integrity of this transmission and shall
> therefore never be liable if the message is altered or falsified nor for any
> virus, interception or damage to your system.
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] New version of the "supercomputer" tutorial available

[Takuya OSHIMA]

The wiki is now updated. thanks!

Takuya

From: Utkarsh Ayachit 
Subject: Re: [Paraview] New version of the "supercomputer" tutorial available
Date: Tue, 16 Mar 2010 09:54:29 -0400

> Thanks great. You can indeed create a login on the Wiki and update it.
> 
> Utkarsh
> 
> On Tue, Mar 16, 2010 at 4:47 AM, Takuya OSHIMA
>  wrote:
> > Hi,
> >
> > It may have taken a bit too long, but we are pleased to inform that we
> > have finished the Japanese translation of The ParaView Tutorial for
> > ParaView 3.6 and it is now publicly available.
> >
> > http://oshima.eng.niigata-u.ac.jp/ParaViewTutorial-jp.pdf
> >
> > We heard that the previous translation (the SC08 version) was used not
> > only by indivisuals but also for in-house teachings in some industrial
> > companies. Hence we believe that the translation also helps to enlarge
> > the community as well.
> >
> > Many thnaks to Kenneth Moreland for the nice tutorial and providing
> > the LaTeX sources and images.
> >
> > p.s.
> > Am I allowd to create an account and update the wiki
> > http://paraview.org/Wiki/The_ParaView_Tutorial
> > or can I ask to somebody?
> >
> > Takuya
> >
> > Takuya OSHIMA, Ph.D.
> > Faculty of Engineering, Niigata University
> > 8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN
> >
> > From: "Moreland, Kenneth" 
> > Subject: [Paraview] New version of the "supercomputer" tutorial available
> > Date: Fri, 18 Sep 2009 14:49:22 -0600
> >
> >> Hi folks,
> >>
> >> I just wanted to let everyone know that there is a new version of the 
> >> "supercomputer" tutorial available on the Wiki.  Because the tutorial is 
> >> fairly general purpose, I've actually taken supercomputing out of the name 
> >> and simply call it The ParaView Tutorial.
> >>
> >> http://www.paraview.org/Wiki/The_ParaView_Tutorial
> >>
> >> Changes for this version of the tutorial include:
> >>
> >>
> >>  *   Updated for ParaView version 3.6.
> >>  *   Exercises broken into smaller chunks.
> >>  *   Added introduction to Python scripting.
> >>
> >> In the past, readers have asked for the source materials of the document, 
> >> mainly to perform translations.  I have included a link to the Wiki page 
> >> where you can download the LaTeX source and images.  As before, anyone who 
> >> wishes to make a translation is encouraged to do so.
> >>
> >> Enjoy,
> >>
> >> -Ken
> >>
> >>          Kenneth Moreland
> >>     ***      Sandia National Laboratories
> >> ***
> >> *** *** ***  email: kmo...@sandia.gov
> >> **  ***  **  phone: (505) 844-8919
> >>     ***      web:   http://www.cs.unm.edu/~kmorel
> >>
> > ___
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at 
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at: 
> > http://paraview.org/Wiki/ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.paraview.org/mailman/listinfo/paraview
> >
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] pvpython and f2py

[Eric E. Monson]

Hey Greg,

Thanks for passing along that info. I had forgotten the PPF had a spot for 
extra PYTHONPATH entries, and that's a good point about behavior under separate 
client/server.

So, Peter, if you're doing this from pvpython instead of the GUI, the 
ProgrammableFilter has a PythonPath property that you can set, too, that I had 
never noticed before Greg mentioned this.

Talk to you later,
-Eric

On Mar 15, 2010, at 7:20 PM, Weirs, V Gregory wrote:

> 
> Another wrinkle is that the PYTHONPATH the programmable filter sees is on the 
> server machine and not the client. So your streamfunc.so has to be on the 
> server machine. If you are running the builtin server it won’t matter, but it 
> is still useful information for the thread’s sake. 
> 
> Also, you might put the PYTHONPATH in the text box at the bottom of the 
> properties panel of the programmable filter.
> 
> Greg
> 
> 
> On 3/15/10 4:55 PM, "Eric E. Monson"  wrote:
> 
> Hey Peter,
> 
> Maybe the problem is that the PYTHONPATH that the programmable filter knows 
> doesn't contain your module? 
> 
> Try adding at the beginning of your Programmable Filter:
> 
> import sys
> sys.path.append('/Dir/of/your/library')
> 
> so it can see things in your library directory and see if your import 
> statement works after that.
> 
> I don't know the "real" way, offhand, to include new directories in the 
> PYTHONPATH of the programmable filter (i.e. I don't know if the PYTHONPATH 
> environment variable affects the PPF).
> 
> -Eric
> 
> 
> On Mar 15, 2010, at 6:41 PM, Peter Brady wrote:
> 
> Hi Eric,
> 
> I'm use Fedora 11 64-bit.  I tried a few more things so maybe this will help. 
>  Using f2py gives me a .so file (streamfunc.so) which I can then import in a 
> pvpython script using:
> 
> import streamfunc
> 
> My problem is that I have a programmable filter which needs this module but 
> when I import it in my programmable filter script I get the error:
> 
> ImportError: No module named streamfunc
> 
> So it seems the problem is with the programmable filter and not with pvpython 
> itself.
> 
> 
> On Mon, Mar 15, 2010 at 3:28 PM, Eric E. Monson  wrote:
> Hey Peter,
> 
> What platform are you using and how are you trying to import the .so file? On 
> my Mac, any of the VTK libraries (my own or original VTK) which are wrapped 
> in Python end up as .so files, and they load just fine. What is python saying 
> when it "doesn't seem to recognize" them?
> 
> Talk to you later,
> -Eric
> 
> 
> On Mar 15, 2010, at 5:44 PM, Peter Brady wrote:
> 
> > Hello all,
> >
> > I need to perform some computations on my data and for speed reasons I 
> > would like to use fortran to accomplish this.  Using pvpython I can get the 
> > data I need, and using f2py I can wrap my fortran subroutine but I can only 
> > get f2py to create a .so file which pvpython doesn't seem to recognize when 
> > I try to import it as a module.  Can someone tell me how to either:
> >
> > 1.  Get pvpython to recognize the .so file created by f2py or
> >
> > 2.  Use f2py to generate a .py file instead of a .so file
> >
> > Thanks in advance,
> >
> > Peter.
> > ___
> > Powered by www.kitware.com  
> >
> > Visit other Kitware open-source projects at 
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at: 
> > http://paraview.org/Wiki/ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.paraview.org/mailman/listinfo/paraview
> 
> 
> 
> 

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] packaging branded problem

[Utkarsh Ayachit]

Good catch. We have a fix for it. Dave should have it committed soon.

Utkarsh

p.s. you guys have been really great (and patient) at helping us
identify and iron out these build/install issues. Thanks!

On Tue, Mar 16, 2010 at 10:25 AM, Eric E. Monson  wrote:
> Hey all,
>
> I'm having trouble today packaging my branded app on 64-bit Ubuntu. I'm just 
> trying to run ccmake to configure, I have  BUILD_SHARED: ON, but it has 
> trouble when I turn CMAKE_SKIP_RPATH:ON. It seems to be having trouble 
> expanding ParaView_SOURCE_DIR on line 172 of ParaViewMacros.cmake, giving me 
> this error during configure stage:
>
> CMake Error: File /Servers/Executables/pv-forward.c.in does not exist.
>
>  CMake Error at 
> /home/emonson/Programming/ParaView_cvs/ParaView3/CMake/ParaViewMacros.cmake:172
>  (CONFIGURE_FILE):
>   configure_file Problem configuring file
>  Call Stack (most recent call first):
>   
> /home/emonson/Programming/ParaView_cvs/ParaView3/CMake/ParaViewBranding.cmake:263
>  (add_executable_with_forwarding2)
>   MSI_Strip3/CMakeLists.txt:48 (build_paraview_client)
>
> Any clue whether this is something I have set up wrong, or is it a bug? I 
> rebuilt paraview yesterday with a new build of Qt, so I'm not sure if I 
> screwed something up since this used to work fine.
>
> (CVS 2010-03-15 ParaView, Qt 4.6.2 from source, ffmpeg, CMake 2.6-patch 4)
>
> Thanks,
> -Eric
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Input Editor - Cramped Input Port Selection

[Utkarsh Ayachit]

Thought others might be interested as well: the mockup was created
using Balsamiq Mocups
http://www.balsamiq.com/products/mockups

Utkarsh

On Tue, Mar 16, 2010 at 6:11 AM, Christian Werner
 wrote:
> By the way, how did you draw this neat mockup? It looks like it's generated
> but when looking more closely you can spot irregular lines and such that
> indicate that it's done by hand... But if it's done by hand then it must
> have taken you some time... I am impressed... :)
>
> Utkarsh Ayachit wrote:
>>
>> I agree, the pipeline preview is confusing and for the most part
>> useless. Unless people object, I'd vote for removing it as well.
>>
>> Attached is a sample mockup. In case of filters like Append which have
>> single input port, but multiple input connections, the use can type in
>> a comma separated list of the inputs in the input field or select
>> multiple items using the pipeline browser in the dialog.
>>
>> Utkarsh
>>
>> On Mon, Mar 15, 2010 at 11:22 AM, Christian Werner
>>  wrote:
>>
>>>
>>> As a user, may I present three suggestions, two of which should be very
>>> easy
>>> and still yield an improvement.
>>>
>>> 1) remove the Pipeline Preview: This may be rude because it's somehow
>>> nice.
>>> But then again, you cannot change what happens to the pipeline anyway.
>>> Also,
>>> I don't think one would change his mind about the selection of the inputs
>>> just because the Pipeline Preview shows something unsuspected. Most of
>>> the
>>> time the user knows what he is doing and wants to quickly and easily
>>> select
>>> his inputs. The actual layout works against this intend. The Pipeline
>>> Preview can be included again once a nice layout is found.
>>>
>>> 2) hide the Pipeline Preview and make it visible if the user wants to
>>>
>>> 3) change the layout such that the inputs are shown on top and let QT
>>> manage
>>> the form's height. You normally don't use so many inputs, so this  most
>>> probably would never lead to problems.
>>>
>>>
>>> Best regards,
>>> Christian
>>>
>>> Paul Edwards wrote:
>>>

 One simple fix would be to make sure that the preview window isn't
 selectable.  A lot of my users get confused thinking one box is for
 the input and the other as the source.

 Regards,
 Paul

 On 12 March 2010 19:10, Utkarsh Ayachit 
 wrote:


>
> I cannot agree more. I am going to take a stab and fixing this before
> 3.8. We've just had too many complaints about this dialog to keep on
> delaying this.
>
> Utkarsh
>
> On Fri, Mar 12, 2010 at 2:00 PM, Christian Werner
>  wrote:
>
>
>>
>> Hello!
>>
>> I wonder why the input port selection is so cramped in the input
>> editor.
>> It
>> is really bad that you cannot actually read out the selections you
>> make
>> without moving the scrollbar. Then, after scrolling, you cannot change
>> the
>> other input without scrolling back. This really steals your time. On
>> the
>> other hand there is that pipeline preview which is nice to see but
>> honestly
>> I'd instantly trade it away for a better overview on my inputs. I have
>> attached a picture that shows the situation on my PC.
>>
>> By the way, doesn't anyone have any idea about my last issue? (no
>> cell/point
>> data in imported ITK volumes):
>>
>>
>>>
>>> "Create Cell or Point Data out of Image"
>>>
>>>
>>
>> Best regards,
>> Christian
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.paraview.org/mailman/listinfo/paraview
>>
>>
>>
>>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
>
>>>
>>>
>>> 
>>>
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Input Editor - Cramped Input Port Selection

[Utkarsh Ayachit]

I am not sure why there's a problem. In your case, your filters have 2
input ports. e.g. in the stream tracer case,  referring to the mockup,
INPUT1 will be called "Input" while INPUT2 will be called
"ArbitrarySource" or "Source" as the case may be. Both of which
allowing the user to only add  1 item in the input box next to them.

Utkarsh

On Tue, Mar 16, 2010 at 4:23 AM, Jérôme  wrote:
> My 2 cents on this :
> It seems to me that the input list is provided in alphabetical order. In my
> case I have a lot of custom plugins that take 2 inputs, one being
> vtkImageData
> and the other a vtkPolyData (such a stream tracer with custom source).
> Depending on wich is the 'principal' input, the default input setting of
> this
> panel have non-corresponding type. For instance, the Image input is set
> to an existing PointSet.
>
> I don't know if I am clear enough, but maybe you can try with the stream
> tracer
> with custom source: in the current configuration, there is no problem. But I
> am
> quite sure that if you rename the 2nd input "Source" to "ArbitrarySource" in
> the
> filters.xml, you will understand this tiny problem.
>
> Jerome
>
> 2010/3/16 Christian Werner 
>>
>> I vote yes for the mockup!
>>
>> Utkarsh Ayachit wrote:
>>>
>>> I agree, the pipeline preview is confusing and for the most part
>>> useless. Unless people object, I'd vote for removing it as well.
>>>
>>> Attached is a sample mockup. In case of filters like Append which have
>>> single input port, but multiple input connections, the use can type in
>>> a comma separated list of the inputs in the input field or select
>>> multiple items using the pipeline browser in the dialog.
>>>
>>> Utkarsh
>>>
>>> On Mon, Mar 15, 2010 at 11:22 AM, Christian Werner
>>>  wrote:
>>>

 As a user, may I present three suggestions, two of which should be very
 easy
 and still yield an improvement.

 1) remove the Pipeline Preview: This may be rude because it's somehow
 nice.
 But then again, you cannot change what happens to the pipeline anyway.
 Also,
 I don't think one would change his mind about the selection of the
 inputs
 just because the Pipeline Preview shows something unsuspected. Most of
 the
 time the user knows what he is doing and wants to quickly and easily
 select
 his inputs. The actual layout works against this intend. The Pipeline
 Preview can be included again once a nice layout is found.

 2) hide the Pipeline Preview and make it visible if the user wants to

 3) change the layout such that the inputs are shown on top and let QT
 manage
 the form's height. You normally don't use so many inputs, so this  most
 probably would never lead to problems.


 Best regards,
 Christian

 Paul Edwards wrote:

>
> One simple fix would be to make sure that the preview window isn't
> selectable.  A lot of my users get confused thinking one box is for
> the input and the other as the source.
>
> Regards,
> Paul
>
> On 12 March 2010 19:10, Utkarsh Ayachit 
> wrote:
>
>
>>
>> I cannot agree more. I am going to take a stab and fixing this before
>> 3.8. We've just had too many complaints about this dialog to keep on
>> delaying this.
>>
>> Utkarsh
>>
>> On Fri, Mar 12, 2010 at 2:00 PM, Christian Werner
>>  wrote:
>>
>>
>>>
>>> Hello!
>>>
>>> I wonder why the input port selection is so cramped in the input
>>> editor.
>>> It
>>> is really bad that you cannot actually read out the selections you
>>> make
>>> without moving the scrollbar. Then, after scrolling, you cannot
>>> change
>>> the
>>> other input without scrolling back. This really steals your time. On
>>> the
>>> other hand there is that pipeline preview which is nice to see but
>>> honestly
>>> I'd instantly trade it away for a better overview on my inputs. I
>>> have
>>> attached a picture that shows the situation on my PC.
>>>
>>> By the way, doesn't anyone have any idea about my last issue? (no
>>> cell/point
>>> data in imported ITK volumes):
>>>
>>>

 "Create Cell or Point Data out of Image"


>>>
>>> Best regards,
>>> Christian
>>>
>>> ___
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>>
>>>
>>>
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source p

Re: [Paraview] packaging branded problem

[Dave Partyka]

Hi Eric, try now. I have moved that file into ParaView\CMake (as it is only
used by ParaViewMacros.cmake) and just added the missing install rule for
it. Let me know if it still gives the error.

On Tue, Mar 16, 2010 at 11:13 AM, Utkarsh Ayachit <
utkarsh.ayac...@kitware.com> wrote:

> Good catch. We have a fix for it. Dave should have it committed soon.
>
> Utkarsh
>
> p.s. you guys have been really great (and patient) at helping us
> identify and iron out these build/install issues. Thanks!
>
> On Tue, Mar 16, 2010 at 10:25 AM, Eric E. Monson 
> wrote:
> > Hey all,
> >
> > I'm having trouble today packaging my branded app on 64-bit Ubuntu. I'm
> just trying to run ccmake to configure, I have  BUILD_SHARED: ON, but it has
> trouble when I turn CMAKE_SKIP_RPATH:ON. It seems to be having trouble
> expanding ParaView_SOURCE_DIR on line 172 of ParaViewMacros.cmake, giving me
> this error during configure stage:
> >
> > CMake Error: File /Servers/Executables/pv-forward.c.in does not exist.
> >
> >  CMake Error at
> /home/emonson/Programming/ParaView_cvs/ParaView3/CMake/ParaViewMacros.cmake:172
> >  (CONFIGURE_FILE):
> >   configure_file Problem configuring file
> >  Call Stack (most recent call first):
> >
> /home/emonson/Programming/ParaView_cvs/ParaView3/CMake/ParaViewBranding.cmake:263
> >  (add_executable_with_forwarding2)
> >   MSI_Strip3/CMakeLists.txt:48 (build_paraview_client)
> >
> > Any clue whether this is something I have set up wrong, or is it a bug? I
> rebuilt paraview yesterday with a new build of Qt, so I'm not sure if I
> screwed something up since this used to work fine.
> >
> > (CVS 2010-03-15 ParaView, Qt 4.6.2 from source, ffmpeg, CMake 2.6-patch
> 4)
> >
> > Thanks,
> > -Eric
> >
> > ___
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.paraview.org/mailman/listinfo/paraview
> >
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Input Editor - Cramped Input Port Selection

[Jérôme]

Then I was right : I was not clear enough!

First, I talked about the current panel, not your mockup. I agree with
those who enthousiastic.
Second, the problem I noted on the multiple-input-port panel is that
the input are not ordered by index, but by name. Changing "Source"
to "ArbirtraySource" in the filters.xml for streamer with custom source
will change the order the inputs appear. Well, I know, if the name are
well-chosen, it is not a problem.

Now, let's take this pipeline:

builtin
   |
   |---Wavelet
   ||
   |Gradient
   |
   | --- PointSource

If you want to initialize a stream tracer in the Gradient at each point
of PointSource, you have to select Gradient, then choose filter ->
Stream tracer with custom source. The inputs panel is shown, with
the Input field being already set to the selected 'Gradient'. What you
have to do is to set the Source to PointSource from the pipeline. Well...
Attached is a screenshot of this procedure, but Source is named
ArbitrarySource. The Gradient is set as ArbitrarySource, and Input field
is not set.

I hope I am clearer now!

Jerome




2010/3/16 Utkarsh Ayachit 

> I am not sure why there's a problem. In your case, your filters have 2
> input ports. e.g. in the stream tracer case,  referring to the mockup,
> INPUT1 will be called "Input" while INPUT2 will be called
> "ArbitrarySource" or "Source" as the case may be. Both of which
> allowing the user to only add  1 item in the input box next to them.
>
> Utkarsh
>
> On Tue, Mar 16, 2010 at 4:23 AM, Jérôme  wrote:
> > My 2 cents on this :
> > It seems to me that the input list is provided in alphabetical order. In
> my
> > case I have a lot of custom plugins that take 2 inputs, one being
> > vtkImageData
> > and the other a vtkPolyData (such a stream tracer with custom source).
> > Depending on wich is the 'principal' input, the default input setting of
> > this
> > panel have non-corresponding type. For instance, the Image input is set
> > to an existing PointSet.
> >
> > I don't know if I am clear enough, but maybe you can try with the stream
> > tracer
> > with custom source: in the current configuration, there is no problem.
> But I
> > am
> > quite sure that if you rename the 2nd input "Source" to "ArbitrarySource"
> in
> > the
> > filters.xml, you will understand this tiny problem.
> >
> > Jerome
> >
> > 2010/3/16 Christian Werner 
> >>
> >> I vote yes for the mockup!
> >>
> >> Utkarsh Ayachit wrote:
> >>>
> >>> I agree, the pipeline preview is confusing and for the most part
> >>> useless. Unless people object, I'd vote for removing it as well.
> >>>
> >>> Attached is a sample mockup. In case of filters like Append which have
> >>> single input port, but multiple input connections, the use can type in
> >>> a comma separated list of the inputs in the input field or select
> >>> multiple items using the pipeline browser in the dialog.
> >>>
> >>> Utkarsh
> >>>
> >>> On Mon, Mar 15, 2010 at 11:22 AM, Christian Werner
> >>>  wrote:
> >>>
> 
>  As a user, may I present three suggestions, two of which should be
> very
>  easy
>  and still yield an improvement.
> 
>  1) remove the Pipeline Preview: This may be rude because it's somehow
>  nice.
>  But then again, you cannot change what happens to the pipeline anyway.
>  Also,
>  I don't think one would change his mind about the selection of the
>  inputs
>  just because the Pipeline Preview shows something unsuspected. Most of
>  the
>  time the user knows what he is doing and wants to quickly and easily
>  select
>  his inputs. The actual layout works against this intend. The Pipeline
>  Preview can be included again once a nice layout is found.
> 
>  2) hide the Pipeline Preview and make it visible if the user wants to
> 
>  3) change the layout such that the inputs are shown on top and let QT
>  manage
>  the form's height. You normally don't use so many inputs, so this
>  most
>  probably would never lead to problems.
> 
> 
>  Best regards,
>  Christian
> 
>  Paul Edwards wrote:
> 
> >
> > One simple fix would be to make sure that the preview window isn't
> > selectable.  A lot of my users get confused thinking one box is for
> > the input and the other as the source.
> >
> > Regards,
> > Paul
> >
> > On 12 March 2010 19:10, Utkarsh Ayachit  >
> > wrote:
> >
> >
> >>
> >> I cannot agree more. I am going to take a stab and fixing this
> before
> >> 3.8. We've just had too many complaints about this dialog to keep on
> >> delaying this.
> >>
> >> Utkarsh
> >>
> >> On Fri, Mar 12, 2010 at 2:00 PM, Christian Werner
> >>  wrote:
> >>
> >>
> >>>
> >>> Hello!
> >>>
> >>> I wonder why the input port selection is so cramped in the input
> >>> editor.
> >>> It
> >>> is really bad that you cannot actually read out the 

Re: [Paraview] Use existing texture map for 3D surface

[Eric E. Monson]

Hey Christian,

Something like this should work:

# =
pdi = self.GetPolyDataInput()
pdo = self.GetPolyDataOutput()

numPts = pdi.GetPoints().GetNumberOfPoints()
Uarray = pdi.GetPointData().GetArray('U')
Varray = pdi.GetPointData().GetArray('V')

tc = vtk.vtkDoubleArray()
tc.SetNumberOfComponents(2)
tc.SetNumberOfTuples(numPts)
tc.SetName('TCoords')

for ii in range(numPts):
  Uval = Uarray.GetTuple1(ii)
  Vval = Varray.GetTuple1(ii)
  tc.SetTuple2(ii,Uval,Vval)

pdo.ShallowCopy(pdi)
pdo.GetPointData().AddArray(tc)
pdo.GetPointData().SetActiveTCoords('TCoords')
# =

-Eric


On Mar 16, 2010, at 9:37 AM, Utkarsh Ayachit wrote:

> Christian,
> 
> Sorry I've been meaning to write up a quick  script for you. For
> starters take a look at:
> 
> http://www.paraview.org/Wiki/Python_Programmable_Filter
> http://www.paraview.org/Wiki/Python_recipes
> 
> Here's the algorithm:
> * Create a new vtkDoubleArray (or another vtkDataArray subclass) with
> 2 components and number of tuples = number of points.
> * Get access the to two input arrays you want to use an texture coordinates.
> * Iterate over each value in the two array and insert them as the two
> components in the new array
> * Set the new array as the TCoords in the output's point data.
> 
> Utkarsh
> 
> On Tue, Mar 16, 2010 at 6:38 AM, Dressler, Christian
>  wrote:
>> Hi Utkarsh,
>> 
>> could you give me some hints or catchwords how to realize that filter? 
>> Perhaps a link to tutorial you recommend?
>> 
>> 
>> Best,
>> 
>> Christian
>> 
>> -Ursprüngliche Nachricht-
>> Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
>> Gesendet: Freitag, 12. März 2010 16:13
>> An: Dressler, Christian
>> Cc: paraview@paraview.org
>> Betreff: Re: [Paraview] Use existing texture map for 3D surface
>> 
>> The problem is that the uv array needs to be marked as "Texture"
>> attribute for the PointData. You can write a PythonProgrammableFilter
>> which generate an output with the Texture coords setup correctly. Let
>> me know if you need help with that. Also remember this filter will
>> have to combine the two "u" and "v" arrays produced by
>> vtkTableToPoints into a single array with 2 components.
>> 
>> Utkarsh
>> 
>> On Fri, Mar 12, 2010 at 10:05 AM, Dressler, Christian
>>  wrote:
>>> Hi Eric,
>>> 
>>> Unfortunately this does not work. Neither for the point cloud, nor for the 
>>> surface. It does only work after generating a map by paraview, but this is 
>>> the wrong map.
>>> 
>>> I also tried to rename the columns header the way paraview does, but it did 
>>> not work. I am looking for an option similar to the "table to points 
>>> filter", where I am asked which column has which meaning.
>>> 
>>> Thanks,
>>> 
>>> Christian
>>> 
>>> 
>>> -Ursprüngliche Nachricht-
>>> Von: Eric E. Monson [mailto:emon...@cs.duke.edu]
>>> Gesendet: Freitag, 12. März 2010 15:54
>>> An: Dressler, Christian
>>> Cc: paraview@paraview.org
>>> Betreff: Re: [Paraview] Use existing texture map for 3D surface
>>> 
>>> Hey Christian,
>>> 
>>> If your data already has valid texture coordinates, highlight your surface 
>>> in the Pipeline Browser. You should be able to go to the Display tab of the 
>>> Object Inspector and in the Color section there is an Apply Texture combo 
>>> box that should not be grayed-out if everything is ready for texturing. If 
>>> you pull down to Load... it will let you load your texture image and you 
>>> should see it on your surface.
>>> 
>>> Let us know if you have problems,
>>> -Eric
>>> 
>>> --
>>> Eric E Monson
>>> Duke Visualization Technology Group
>>> 
>>> 
>>> On Mar 12, 2010, at 7:51 AM, Dressler, Christian wrote:
>>> 
 
 Hi,
 
 I am trying to reconstruct data generated by a surface scanner with 
 paraview. The data is structured as xyzuv arrays. I managed to calculate 
 the surface by using the filters "Table to points" and "Delaunay 2D".
 
 But I could not figure out, how to apply the texture to the surface. The 
 uv-coordinates have the same format as the maps generated by the paraview 
 texture filters (normalized position of bitmap).
 
 How can I make paraview using my own texture map?
 
 
 Best,
 
 Christian
 
 Dipl.-Ing. Christian Dressler
 Research Associate  | Working Group - S-DICOM Solutions
 
 Universität Leipzig | Faculty of Medicine
 Innovation Center Computer Assisted Surgery (ICCAS)
 Semmelweisstr. 14
 D - 04103 Leipzig
 Germany
 
 phone  +49 (0) 341 97 - 12018
 fax+49 (0) 341 97 - 12009
 christian.dress...@medizin.uni-leipzig.de
 http://www.iccas.de/?id=430
 
 
 ___
 Powered by www.kitware.com
 
 Visit other Kitware open-source projects at 
 http://www.kitware.com/opens

Re: [Paraview] Use existing texture map for 3D surface

[Dressler, Christian]

Thanks a lot! The code worked on the first go!

Thank you very much for saving me that much time!

Best,

Christian

-Ursprüngliche Nachricht-
Von: Eric E. Monson [mailto:emon...@cs.duke.edu] 
Gesendet: Dienstag, 16. März 2010 17:13
An: Utkarsh Ayachit
Cc: Dressler, Christian; paraview@paraview.org
Betreff: Re: [Paraview] Use existing texture map for 3D surface

Hey Christian,

Something like this should work:

# =
pdi = self.GetPolyDataInput()
pdo = self.GetPolyDataOutput()

numPts = pdi.GetPoints().GetNumberOfPoints()
Uarray = pdi.GetPointData().GetArray('U')
Varray = pdi.GetPointData().GetArray('V')

tc = vtk.vtkDoubleArray()
tc.SetNumberOfComponents(2)
tc.SetNumberOfTuples(numPts)
tc.SetName('TCoords')

for ii in range(numPts):
  Uval = Uarray.GetTuple1(ii)
  Vval = Varray.GetTuple1(ii)
  tc.SetTuple2(ii,Uval,Vval)

pdo.ShallowCopy(pdi)
pdo.GetPointData().AddArray(tc)
pdo.GetPointData().SetActiveTCoords('TCoords')
# =

-Eric


On Mar 16, 2010, at 9:37 AM, Utkarsh Ayachit wrote:

> Christian,
> 
> Sorry I've been meaning to write up a quick  script for you. For
> starters take a look at:
> 
> http://www.paraview.org/Wiki/Python_Programmable_Filter
> http://www.paraview.org/Wiki/Python_recipes
> 
> Here's the algorithm:
> * Create a new vtkDoubleArray (or another vtkDataArray subclass) with
> 2 components and number of tuples = number of points.
> * Get access the to two input arrays you want to use an texture coordinates.
> * Iterate over each value in the two array and insert them as the two
> components in the new array
> * Set the new array as the TCoords in the output's point data.
> 
> Utkarsh
> 
> On Tue, Mar 16, 2010 at 6:38 AM, Dressler, Christian
>  wrote:
>> Hi Utkarsh,
>> 
>> could you give me some hints or catchwords how to realize that filter? 
>> Perhaps a link to tutorial you recommend?
>> 
>> 
>> Best,
>> 
>> Christian
>> 
>> -Ursprüngliche Nachricht-
>> Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
>> Gesendet: Freitag, 12. März 2010 16:13
>> An: Dressler, Christian
>> Cc: paraview@paraview.org
>> Betreff: Re: [Paraview] Use existing texture map for 3D surface
>> 
>> The problem is that the uv array needs to be marked as "Texture"
>> attribute for the PointData. You can write a PythonProgrammableFilter
>> which generate an output with the Texture coords setup correctly. Let
>> me know if you need help with that. Also remember this filter will
>> have to combine the two "u" and "v" arrays produced by
>> vtkTableToPoints into a single array with 2 components.
>> 
>> Utkarsh
>> 
>> On Fri, Mar 12, 2010 at 10:05 AM, Dressler, Christian
>>  wrote:
>>> Hi Eric,
>>> 
>>> Unfortunately this does not work. Neither for the point cloud, nor for the 
>>> surface. It does only work after generating a map by paraview, but this is 
>>> the wrong map.
>>> 
>>> I also tried to rename the columns header the way paraview does, but it did 
>>> not work. I am looking for an option similar to the "table to points 
>>> filter", where I am asked which column has which meaning.
>>> 
>>> Thanks,
>>> 
>>> Christian
>>> 
>>> 
>>> -Ursprüngliche Nachricht-
>>> Von: Eric E. Monson [mailto:emon...@cs.duke.edu]
>>> Gesendet: Freitag, 12. März 2010 15:54
>>> An: Dressler, Christian
>>> Cc: paraview@paraview.org
>>> Betreff: Re: [Paraview] Use existing texture map for 3D surface
>>> 
>>> Hey Christian,
>>> 
>>> If your data already has valid texture coordinates, highlight your surface 
>>> in the Pipeline Browser. You should be able to go to the Display tab of the 
>>> Object Inspector and in the Color section there is an Apply Texture combo 
>>> box that should not be grayed-out if everything is ready for texturing. If 
>>> you pull down to Load... it will let you load your texture image and you 
>>> should see it on your surface.
>>> 
>>> Let us know if you have problems,
>>> -Eric
>>> 
>>> --
>>> Eric E Monson
>>> Duke Visualization Technology Group
>>> 
>>> 
>>> On Mar 12, 2010, at 7:51 AM, Dressler, Christian wrote:
>>> 
 
 Hi,
 
 I am trying to reconstruct data generated by a surface scanner with 
 paraview. The data is structured as xyzuv arrays. I managed to calculate 
 the surface by using the filters "Table to points" and "Delaunay 2D".
 
 But I could not figure out, how to apply the texture to the surface. The 
 uv-coordinates have the same format as the maps generated by the paraview 
 texture filters (normalized position of bitmap).
 
 How can I make paraview using my own texture map?
 
 
 Best,
 
 Christian
 
 Dipl.-Ing. Christian Dressler
 Research Associate  | Working Group - S-DICOM Solutions
 
 Universität Leipzig | Faculty of Medicine
 Innovation Center Computer Assisted Surgery (ICCAS)
 Semmelweisstr. 14
 D - 04103 Leipzig
 Germany
 
 ph

[Paraview] Second try re:Question about volume viz algorithm(s)

[Comer Duncan]

Not having heard back, I am trying this submission again.  Please help.

I have two questions related to volume visualization in Paraview and VTK.

1. I would like to know more about the algorithm that is used in Paraview to
do volume viz.  I have used Paraview to viz a cartesian grid data set with
reaonable success.  I can not seem to locate in the documentation much at
all about just which algorithm is being used.  And how come there is a need
to stuff the data through tetrahedralize first?

2. I have recently taken a look at the vtk examples for volume viz.  They
are nice.  However, I decided to take a look at modifying SimpleRayCast.py
to viz my 31^3 data set i doubles but seem to find that the routine which
does the heavy lifting does not take doubles.  What do I need to do first to
make use of this example?

Thanks very much for your help.

Comer
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

[Paraview] FFMPEG swscale required?

[Eric E. Monson]

Hello,

I had to rebuild ParaView on my 64-bit Ubuntu (9.10) system yesterday. Today 
when I remembered I needed to turn on FFMPEG, I switched 
VTK_USE_FFMPEG_ENCODER: ON and ran into a cmake error during config:

CMake Error: The following variables are used in this project, but they are set 
to NOTFOUND.
 Please set them or make sure they are set and tested correctly in the CMake 
files:
 FFMPEG_swscale_LIBRARY (ADVANCED)
 linked by target "vtkIO" in directory 
/home/emonson/Programming/ParaView_cvs/ParaView3/VTK/IO

I'm using the old FFMPEG sources from the VTK site that I compiled a couple 
months ago, and it was working back then. CMake was able to find the libraries 
I have okay:

FFMPEG_INCLUDE_DIR   /usr/local/include/ffmpeg  
  
FFMPEG_avcodec_LIBRARY   /usr/local/lib/libavcodec.so   
   
FFMPEG_avformat_LIBRARY  /usr/local/lib/libavformat.so  
   
FFMPEG_avutil_LIBRARY/usr/local/lib/libavutil.so

Is it just not auto-detecting that I'm using the old FFMPEG? Has there been a 
change recently that might cause this, or do you think I might have something 
configured wrong? 

The only other difference in this build was I started using Qt 4.6.2 I compiled 
from source rather than the package I can apt-get with Ubuntu. (CVS ParaView 
from today, CMake 2.6-patch 4)

Thanks,
-Eric

--
Eric E Monson
Duke Visualization Technology Group


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] 64-bit version for MacOS?

[Eric Nodwell]

Eric,

I have a couple of questions about building paraview with x86_64 architecture 
on OS-X:

1.  You recommend building Qt 4.6.2 from source, but there is a binary version 
build with x86_64 and Cocoa available from 
http://qt.nokia.com/downloads/mac-os-cpp (the file is 
qt-mac-cocoa-opensource-4.6.2.dmg) .  Is there any reason not to use this 
binary version of Qt instead of building Qt from source?

2. When configuring paraview 3.6.2, if I try to set VTK_USE_CARBON to OFF and 
VTK_USE_COCOA to ON, CMake just flips them back again when I hit Configure.  Is 
there any way to force this so that it can be built with Cocoa?

Thanks,
Eric


> Date: Tue, 16 Mar 2010 09:55:47 -0400
> From: "Eric E. Monson" 
> Subject: Re: [Paraview] 64-bit version for MacOS?
> To: Karen Lee 
> Cc: paraview@paraview.org
> Message-ID: <063acbec-89be-44b0-8ded-9273d3263...@cs.duke.edu>
> Content-Type: text/plain; charset=us-ascii
> 
> Hey Karen,
> 
> No, the 3.6.1 binary for Intel is i386 architecture. Like Mike said 
> yesterday, you'll have to build your own version of Qt 4.6.2 with x86_64 
> architecture and Cocoa, and then build ParaView from source against that Qt 
> build, itself with x86_64 arch, too.
> 
> I'm not sure if there are any issues with 64-bit ParaView Python support in 
> Leopard since for OS X 10.5 you can't get (as far as I know) a 64-bit python 
> executable...?
> 
> Talk to you later,
> -Eric

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] 64-bit version for MacOS?

[Utkarsh Ayachit]

3.6.2 will not work with Cocoa. You will have to use CVS ParaView.

On Tue, Mar 16, 2010 at 4:14 PM, Eric Nodwell  wrote:
> Eric,
>
> I have a couple of questions about building paraview with x86_64 architecture 
> on OS-X:
>
> 1.  You recommend building Qt 4.6.2 from source, but there is a binary 
> version build with x86_64 and Cocoa available from 
> http://qt.nokia.com/downloads/mac-os-cpp (the file is 
> qt-mac-cocoa-opensource-4.6.2.dmg) .  Is there any reason not to use this 
> binary version of Qt instead of building Qt from source?
>
> 2. When configuring paraview 3.6.2, if I try to set VTK_USE_CARBON to OFF and 
> VTK_USE_COCOA to ON, CMake just flips them back again when I hit Configure.  
> Is there any way to force this so that it can be built with Cocoa?
>
> Thanks,
> Eric
>
>
>> Date: Tue, 16 Mar 2010 09:55:47 -0400
>> From: "Eric E. Monson" 
>> Subject: Re: [Paraview] 64-bit version for MacOS?
>> To: Karen Lee 
>> Cc: paraview@paraview.org
>> Message-ID: <063acbec-89be-44b0-8ded-9273d3263...@cs.duke.edu>
>> Content-Type: text/plain; charset=us-ascii
>>
>> Hey Karen,
>>
>> No, the 3.6.1 binary for Intel is i386 architecture. Like Mike said 
>> yesterday, you'll have to build your own version of Qt 4.6.2 with x86_64 
>> architecture and Cocoa, and then build ParaView from source against that Qt 
>> build, itself with x86_64 arch, too.
>>
>> I'm not sure if there are any issues with 64-bit ParaView Python support in 
>> Leopard since for OS X 10.5 you can't get (as far as I know) a 64-bit python 
>> executable...?
>>
>> Talk to you later,
>> -Eric
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] 64-bit version for MacOS?

[Michael Jackson]

You will probably have to use ParaView from CVS "Head" in order to fix  
the "Carbon/Cocoa" thing. There is a quick patch you can do to a stock  
ParaView 3.6.2 to fix the problem if you want.  will have the necessary code.


The download from nokia should be just fine.

___
Mike Jackson  www.bluequartz.net
Principal Software Engineer   mike.jack...@bluequartz.net
BlueQuartz Software   Dayton, Ohio


On Mar 16, 2010, at 4:14 PM, Eric Nodwell wrote:


Eric,

I have a couple of questions about building paraview with x86_64  
architecture on OS-X:


1.  You recommend building Qt 4.6.2 from source, but there is a  
binary version build with x86_64 and Cocoa available from http://qt.nokia.com/downloads/mac-os-cpp 
 (the file is qt-mac-cocoa-opensource-4.6.2.dmg) .  Is there any  
reason not to use this binary version of Qt instead of building Qt  
from source?


2. When configuring paraview 3.6.2, if I try to set VTK_USE_CARBON  
to OFF and VTK_USE_COCOA to ON, CMake just flips them back again  
when I hit Configure.  Is there any way to force this so that it can  
be built with Cocoa?


Thanks,
Eric



Date: Tue, 16 Mar 2010 09:55:47 -0400
From: "Eric E. Monson" 
Subject: Re: [Paraview] 64-bit version for MacOS?
To: Karen Lee 
Cc: paraview@paraview.org
Message-ID: <063acbec-89be-44b0-8ded-9273d3263...@cs.duke.edu>
Content-Type: text/plain; charset=us-ascii

Hey Karen,

No, the 3.6.1 binary for Intel is i386 architecture. Like Mike said  
yesterday, you'll have to build your own version of Qt 4.6.2 with  
x86_64 architecture and Cocoa, and then build ParaView from source  
against that Qt build, itself with x86_64 arch, too.


I'm not sure if there are any issues with 64-bit ParaView Python  
support in Leopard since for OS X 10.5 you can't get (as far as I  
know) a 64-bit python executable...?


Talk to you later,
-Eric


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] 64-bit version for MacOS?

[Sean McBride]

On Tue, 16 Mar 2010 09:55:47 -0400, Eric E. Monson said:

>I'm not sure if there are any issues with 64-bit ParaView Python support
>in Leopard since for OS X 10.5 you can't get (as far as I know) a 64-bit
>python executable...?

In general, 64 bit support is pretty good in 10.5.x.  But it's much
better in 10.6.  And the upgrade is very cheap, unless you're on
PowerPC, in which case the upgrade is impossible. :(

If 64 bit is important to you, don't use 10.5.

-- 

Sean McBride, B. Eng s...@rogue-research.com
Rogue Researchwww.rogue-research.com 
Mac Software Developer  Montréal, Québec, Canada


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview