Re: [Paraview] error in X86_64: libvtkalglib.so
Ricardo, Update your cvs and try again please. This is a new library that was missing install rules. It should be fixed. -berk On Tue, Dec 16, 2008 at 8:48 AM, Ricardo Reis rr...@aero.ist.utl.pt wrote: On Tue, 16 Dec 2008, Olesen, Mark wrote: Since bin/paraview finds paraview-real, it would seem that the lib/paraview-X.X directory is actually there. Did you attempt to install to the same directory as your build directory? This is where I've encounter the same problem before. No, I'm using a diferent dir and when I do make install he puts stuff there. If you just edit the CMAKE_INSTALL_PREFIX:PATH in CMakeCache.txt (in the build dir) and try 'make install' again. I have this in my CMAKE_INSTALL_PREFIX CMAKE_INSTALL_PREFIX:PATH=/usr/local/paraviewcvs.shared so this is not the problem, it seems... Should I atach my CMakeCache.txt ? Ricardo Reis 'Non Serviam' PhD student @ Lasef Computational Fluid Dynamics, High Performance Computing, Turbulence http://www.lasef.ist.utl.pt Cultural Instigator @ Rádio Zero http://www.radiozero.pt http://www.flickr.com/photos/rreis/ ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] error in X86_64: libvtkalglib.so
Hi Berk, While we're somewhat on the topic of installing, I would like to get some tips about the correct means of building/installing a portable version of paraview. I currently have make, make HTMLDocumentation, make install with the build directories and install directories being different (same issue as Ricardo). I would like to be able to move all the sources about later, but also need to retain the build directory (to build plugins at a later stage). Is it safe to have identical build/install directories? If I wish to move my files about after the initial compilation (eg from a local disk to an NFS-share), what is the best means of doing this without recompiling everything? I tried editing the *.cmake files to use environment variables. This helps find relocated things (I think), but also provokes an unnecessary remake. How do you go about bundling things like this? /mark Dr. Mark Olesen Principal Engineer Thermofluids Analysis EMCON Technologies Germany (Augsburg) GmbH Biberbachstr. 9 D-86154 Augsburg, GERMANY tel: +49 (821) 4103 - 862 fax: +49 (821) 4103 - 7862 -- Aufsichtsrat: Gary Strickland (Vors.) Geschäftsführung: Michael Bleidt (Vors.), Dr. Martin Funk, Martin Stüttem Eintrag: Registergericht Augsburg HRB 20757 -Original Message- From: Berk Geveci [mailto:berk.gev...@kitware.com] Sent: Tuesday, December 16, 2008 3:12 PM To: Ricardo Reis Cc: Olesen, Mark; paraview@paraview.org Subject: Re: [Paraview] error in X86_64: libvtkalglib.so Ricardo, Update your cvs and try again please. This is a new library that was missing install rules. It should be fixed. -berk On Tue, Dec 16, 2008 at 8:48 AM, Ricardo Reis rr...@aero.ist.utl.pt wrote: On Tue, 16 Dec 2008, Olesen, Mark wrote: Since bin/paraview finds paraview-real, it would seem that the lib/paraview-X.X directory is actually there. Did you attempt to install to the same directory as your build directory? This is where I've encounter the same problem before. No, I'm using a diferent dir and when I do make install he puts stuff there. If you just edit the CMAKE_INSTALL_PREFIX:PATH in CMakeCache.txt (in the build dir) and try 'make install' again. I have this in my CMAKE_INSTALL_PREFIX CMAKE_INSTALL_PREFIX:PATH=/usr/local/paraviewcvs.shared so this is not the problem, it seems... Should I atach my CMakeCache.txt ? Ricardo Reis 'Non Serviam' PhD student @ Lasef Computational Fluid Dynamics, High Performance Computing, Turbulence http://www.lasef.ist.utl.pt Cultural Instigator @ Rádio Zero http://www.radiozero.pt http://www.flickr.com/photos/rreis/ ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview This e-mail message and any attachments may contain legally privileged, confidential or proprietary Information, or information otherwise protected by law of EMCON Technologies, its affiliates, or third parties. This notice serves as marking of its Confidential status as defined in any confidentiality agreements concerning the sender and recipient. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Object Panel - Model Communication
Hey all, I'm programming a filter with a custom Object Panel, and I'm feeling a little bit lost about the ParaView architecture and code design. My great problem is the comunication between the Object Panel and the Model. I know I can't have a pointer to my vtkUnstructuredGrid displayed, 'cause they are not necessarily at the same machine or process. I also know that I'm able to send information to the model through properties, since I can get the vtkSMProxy in my panel. But what about the way back ? Is there a way to send information from the display view to the panel ? How can I display in a QTable, for instance, the nodes of my model which have some property equals to 1 ? Another problem is the Visualization Pipeline: is there a way to walk on it ? I mean, if I have a filter name, am I able to get the the filter no matter where it is in the Pipeline ? How to get, for instance, the ids of the nodes which are displayed after the application of a filter to the model ? Sorry for the mess with the questions. I hope I made it clear and someone can help me ! :) Regards, Rafael March. ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] error in X86_64: libvtkalglib.so
Hi Before it worked fine, now it doesn't. I've checked out paraview from cvs in two machines, one 32 bit, the other 64. Both Linux, debian, testing. I had done this before and everything worked fine. My options are MPI, PYTHON, shared libs on, and RPATH OFF. In the 32 bit machine everything works fine. In the 64 bit I get this message: /usr/local/paraviewcvs/lib/paraview-3.5/paraview-real: error while loading shared libraries: libvtkalglib.so: cannot open shared object file: No such file or directory Any ideas or needed output/logs to track and solve the problem? If I run paraview from the build directory everything works fine, if it runs from the directory were I installed it it fails with the above message. ideas? Ricardo Reis 'Non Serviam' PhD student @ Lasef Computational Fluid Dynamics, High Performance Computing, Turbulence http://www.lasef.ist.utl.pt Cultural Instigator @ Rádio Zero http://www.radiozero.pt http://www.flickr.com/photos/rreis/___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Not a valid QT plugin on windows
Hi all, I have two plugins for Paraview that used to work fine with ParaView 3.2 under linux (I used to build them at the same time as ParaView.) Now I am using Visual Studio and have compiled the plugins outside of paraview. I am able to generate dll for both the server and client plugins. (I had to switch the vtkIO_EXPORTS flag on to build the dlls) When I launch paraview, only the client side is loaded and when I try to load the server side it fails with the message : * is not a valid Qt plugin ... I have found some threads dealing with this but nothing that I can try. I have built ParaView and my plugins against the same version of Qt (4.4.3) Any help would be greatly appreciated. Jacques --- This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd. Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] error in X86_64: libvtkalglib.so
On Tue, 16 Dec 2008, Olesen, Mark wrote: Since bin/paraview finds paraview-real, it would seem that the lib/paraview-X.X directory is actually there. Did you attempt to install to the same directory as your build directory? This is where I've encounter the same problem before. No, I'm using a diferent dir and when I do make install he puts stuff there. If you just edit the CMAKE_INSTALL_PREFIX:PATH in CMakeCache.txt (in the build dir) and try 'make install' again. I have this in my CMAKE_INSTALL_PREFIX CMAKE_INSTALL_PREFIX:PATH=/usr/local/paraviewcvs.shared so this is not the problem, it seems... Should I atach my CMakeCache.txt ? Ricardo Reis 'Non Serviam' PhD student @ Lasef Computational Fluid Dynamics, High Performance Computing, Turbulence http://www.lasef.ist.utl.pt Cultural Instigator @ Rádio Zero http://www.radiozero.pt http://www.flickr.com/photos/rreis/___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] error in X86_64: libvtkalglib.so
Since bin/paraview finds paraview-real, it would seem that the lib/paraview-X.X directory is actually there. Did you attempt to install to the same directory as your build directory? This is where I've encounter the same problem before. If you just edit the CMAKE_INSTALL_PREFIX:PATH in CMakeCache.txt (in the build dir) and try 'make install' again. /mark This e-mail message and any attachments may contain legally privileged, confidential or proprietary Information, or information otherwise protected by law of EMCON Technologies, its affiliates, or third parties. This notice serves as marking of its Confidential status as defined in any confidentiality agreements concerning the sender and recipient. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Object Panel - Model Communication
To get back values from the server, you can use either information properties or information objects. Information properties are properites with information_only=1 set in the XML (eg. in Servers/ServerManager/Resources/rendering.xml the Camera proxy has CameraPositionInfo as an information property). Such properties need an InformationHelper which knows how to obtain the values from the server. For simple Get*() methods, you can use the SimpleDoubleInformationHelper/ or SimpleIntInformationHelper / etc. based on the type of the property. Complex information helpers can be written as well. Look at TimeStepsInformationHelper (vtkSMTimeStepsInformationHelper.h|cxx) as an example. Information objects are used to get data from server which cannot be simply put in a property for example information about the data object produced by a filter (vtkPVDataInformation). These are vtkPVInformation subclasses. You can create you own vtkPVInformation subclass that knows how to collect information and then serialize/deserialize it for transfer to the client from the server (if needed). To gather such information, one uses vtkProcessModule::GatherInformation(vtkIdType connectionID, vtkTypeUInt32 serverFlags, vtkPVInformation* info, vtkClientServerID id) where id is vtkSMProxy::GetID() returned for the proxy from which you want to collect the information. In your case, information property may be an easier solution -- if I understand your problem correctly. There is a pqServerManagerModel instance accessible as pqApplicationCore::instance()-getServerManagerModel() that can be used to access sources/filters their representations, views etc. Take a look at Qt/Core/pqServerManagerModel.h for the API. That should help you access the visualization pipeline. How to get, for instance, the ids of the nodes which are displayed after the application of a filter to the model ? Not sure I understand what you mean by that. Can you please elaborate? Utkarsh On Tue, Dec 16, 2008 at 6:38 AM, Rafael March rafaelmar...@yahoo.com wrote: Hey all, I'm programming a filter with a custom Object Panel, and I'm feeling a little bit lost about the ParaView architecture and code design. My great problem is the comunication between the Object Panel and the Model. I know I can't have a pointer to my vtkUnstructuredGrid displayed, 'cause they are not necessarily at the same machine or process. I also know that I'm able to send information to the model through properties, since I can get the vtkSMProxy in my panel. But what about the way back ? Is there a way to send information from the display view to the panel ? How can I display in a QTable, for instance, the nodes of my model which have some property equals to 1 ? Another problem is the Visualization Pipeline: is there a way to walk on it ? I mean, if I have a filter name, am I able to get the the filter no matter where it is in the Pipeline ? Sorry for the mess with the questions. I hope I made it clear and someone can help me ! :) Regards, Rafael March. ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] error in X86_64: libvtkalglib.so
Ricardo, As Berk mentions, install rules have been added. Can you say exactly when your had a checkout that was working and when you updated and it stopped working? I added vtkalglib to VTK 2008-12-04 15:57:36 GMT and added the install rule 2008-12-15 23:12:04 GMT. Depending on when things stopped working, I may have more to fix. Thanks, David On Tue, 2008-12-16 at 07:11 -0700, Berk Geveci wrote: Ricardo, Update your cvs and try again please. This is a new library that was missing install rules. It should be fixed. -berk On Tue, Dec 16, 2008 at 8:48 AM, Ricardo Reis rr...@aero.ist.utl.pt wrote: On Tue, 16 Dec 2008, Olesen, Mark wrote: Since bin/paraview finds paraview-real, it would seem that the lib/paraview-X.X directory is actually there. Did you attempt to install to the same directory as your build directory? This is where I've encounter the same problem before. No, I'm using a diferent dir and when I do make install he puts stuff there. If you just edit the CMAKE_INSTALL_PREFIX:PATH in CMakeCache.txt (in the build dir) and try 'make install' again. I have this in my CMAKE_INSTALL_PREFIX CMAKE_INSTALL_PREFIX:PATH=/usr/local/paraviewcvs.shared so this is not the problem, it seems... Should I atach my CMakeCache.txt ? Ricardo Reis 'Non Serviam' PhD student @ Lasef Computational Fluid Dynamics, High Performance Computing, Turbulence http://www.lasef.ist.utl.pt Cultural Instigator @ Rádio Zero http://www.radiozero.pt http://www.flickr.com/photos/rreis/ ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] error in X86_64: libvtkalglib.so
We are working on creating a separate install target that will install all development dependencies. Once that is done, you should be able to do something like make install_development and then use those files. -berk On Tue, Dec 16, 2008 at 9:26 AM, Olesen, Mark mark.ole...@emcontechnologies.com wrote: Hi Berk, While we're somewhat on the topic of installing, I would like to get some tips about the correct means of building/installing a portable version of paraview. I currently have make, make HTMLDocumentation, make install with the build directories and install directories being different (same issue as Ricardo). I would like to be able to move all the sources about later, but also need to retain the build directory (to build plugins at a later stage). Is it safe to have identical build/install directories? If I wish to move my files about after the initial compilation (eg from a local disk to an NFS-share), what is the best means of doing this without recompiling everything? I tried editing the *.cmake files to use environment variables. This helps find relocated things (I think), but also provokes an unnecessary remake. How do you go about bundling things like this? /mark Dr. Mark Olesen Principal Engineer Thermofluids Analysis EMCON Technologies Germany (Augsburg) GmbH Biberbachstr. 9 D-86154 Augsburg, GERMANY tel: +49 (821) 4103 - 862 fax: +49 (821) 4103 - 7862 -- Aufsichtsrat: Gary Strickland (Vors.) Geschäftsführung: Michael Bleidt (Vors.), Dr. Martin Funk, Martin Stüttem Eintrag: Registergericht Augsburg HRB 20757 -Original Message- From: Berk Geveci [mailto:berk.gev...@kitware.com] Sent: Tuesday, December 16, 2008 3:12 PM To: Ricardo Reis Cc: Olesen, Mark; paraview@paraview.org Subject: Re: [Paraview] error in X86_64: libvtkalglib.so Ricardo, Update your cvs and try again please. This is a new library that was missing install rules. It should be fixed. -berk On Tue, Dec 16, 2008 at 8:48 AM, Ricardo Reis rr...@aero.ist.utl.pt wrote: On Tue, 16 Dec 2008, Olesen, Mark wrote: Since bin/paraview finds paraview-real, it would seem that the lib/paraview-X.X directory is actually there. Did you attempt to install to the same directory as your build directory? This is where I've encounter the same problem before. No, I'm using a diferent dir and when I do make install he puts stuff there. If you just edit the CMAKE_INSTALL_PREFIX:PATH in CMakeCache.txt (in the build dir) and try 'make install' again. I have this in my CMAKE_INSTALL_PREFIX CMAKE_INSTALL_PREFIX:PATH=/usr/local/paraviewcvs.shared so this is not the problem, it seems... Should I atach my CMakeCache.txt ? Ricardo Reis 'Non Serviam' PhD student @ Lasef Computational Fluid Dynamics, High Performance Computing, Turbulence http://www.lasef.ist.utl.pt Cultural Instigator @ Rádio Zero http://www.radiozero.pt http://www.flickr.com/photos/rreis/ ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview This e-mail message and any attachments may contain legally privileged, confidential or proprietary Information, or information otherwise protected by law of EMCON Technologies, its affiliates, or third parties. This notice serves as marking of its Confidential status as defined in any confidentiality agreements concerning the sender and recipient. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Not a valid QT plugin on windows
Odd that only one of the two plugins get loaded. Perhaps the server plugin is
missing some symbols. Try running the depends program on it and make sure it
can find all of the dependent dlls. Also make sure that the server manager
initialization function is properly exported (I think it's called
@plugin_n...@_initialize).
You could also try wrapping the client and server code into the same plugin
(with checks to dump the client code when the GUI is not built). I have never
liked the idea of having separate client server plugins; they make loading
the plugin more cumbersome and confusing rather than helpful.
-Ken
On 12/16/08 10:54 AM, Jacques Papper jpap...@ara.co.uk wrote:
Hi all,
I have two plugins for Paraview that used to work fine with ParaView 3.2
under linux (I used to build them at the same time as ParaView.)
Now I am using Visual Studio and have compiled the plugins outside of
paraview. I am able to generate dll for both the server and client plugins.
(I had to switch the vtkIO_EXPORTS flag on to build the dlls)
When I launch paraview, only the client side is loaded and when I try to
load the server side it fails with the message : * is not a valid Qt
plugin ...
I have found some threads dealing with this but nothing that I can try.
I have built ParaView and my plugins against the same version of Qt (4.4.3)
Any help would be greatly appreciated.
Jacques
---
This email contains information that is private and confidential and is
intended only for the addressee. If you are not the intended recipient please
delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other
than the recipient, for system management and security reasons.
Aircraft Research Association Ltd. Registered in England, Registration No
503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB
196351245
___
ParaView mailing list
ParaView@paraview.org
http://www.paraview.org/mailman/listinfo/paraview
Kenneth Moreland
*** Sandia National Laboratories
***
*** *** *** email: kmo...@sandia.gov
** *** ** phone: (505) 844-8919
*** web: http://www.cs.unm.edu/~kmorel
___
ParaView mailing list
ParaView@paraview.org
http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] error in X86_64: libvtkalglib.so
Hi David On Tue, 16 Dec 2008, David Thompson wrote: As Berk mentions, install rules have been added. Can you say exactly when your had a checkout that was working and when you updated and it stopped working? I added vtkalglib to VTK 2008-12-04 15:57:36 GMT and added the install rule 2008-12-15 23:12:04 GMT. Depending on when things stopped working, I may have more to fix. Everything is working fine now :) Last time I checkout (and it didn't work) was last night I think. Ricardo Reis 'Non Serviam' PhD student @ Lasef Computational Fluid Dynamics, High Performance Computing, Turbulence http://www.lasef.ist.utl.pt Cultural Instigator @ Rádio Zero http://www.radiozero.pt http://www.flickr.com/photos/rreis/___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
