Re: [Paraview] issue about deformed and misplaced color bars ...
Ufuk, In any case, both issues are now fixed in `master` and should be available in the next release candidate. Utkarsh On Fri, Feb 17, 2017 at 12:05 PM, Utkarsh Ayachit < utkarsh.ayac...@kitware.com> wrote: > Ufuk, > > I believe the issue you're running into is https://gitlab.kitware.com/ > paraview/paraview/issues/17197, more so than the one your pointed. > > I have a fix for 17197 on the way: https://gitlab.kitware. > com/paraview/paraview/merge_requests/1393 > > Utkarsh > > On Fri, Feb 17, 2017 at 4:39 AM, wrote: > >> Hi, >> >> I was using Catalyst with 5.2 and the color bars are shown as tiny and >> also misplaced when it is compared with ParaView output. I also checked it >> with 5.3RC1 and the issue is still in there. So, is there any plan to fix >> it in 5.3. There ware also discussion about it in the mail list and it >> seems that it is related with following issue but aim not sure. >> >> https://gitlab.kitware.com/paraview/paraview/issues/17113 >> >> Regards, >> >> --ufuk >> >> >> >> ___ >> 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 >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] Import a four-dimensional array and "slice" one dimension to plot in 3D
Fred, A reader plugin would be perfectly reasonable. Distributing a plugin may not be easier than distributing the programmable source file, though, because it needs to be built with the same tools as the ParaView binary. We don't have a ParaView SDK to build against, so you would have to build and distribute both ParaView and your plugin to other folks. It's possible, but a fair amount of work. > - I seem unable to import a few python packages that I know I can > import in a usual python command. More of the standard python packages will be included in 5.3.0, due out early March 2017. A number were not included in 5.2.0. The Programmable Source also provides a way to add to the PYTHONPATH variable if you need to point to other Python modules. Compatibility caveats apply, though. Another option to consider: make an XML plugin out of your Programmable Source. See https://blog.kitware.com/easy-customization-of-the-paraview-python-programmable-filter-property-panel/ for details. With this approach, you could distribute an XML file that others load through the Plugin Manager. Any recent version of ParaView would be able to load it - you wouldn't need to build your own ParaView to distribute with it. HTH, Cory On Fri, Feb 17, 2017 at 12:31 PM, Frederic Perez wrote: > Thank you for this suggestion. > > I have been looking at programmable sources, and although they are new > to me, I think I have found a few issues for my objective: > - I seem unable to import a few python packages that I know I can > import in a usual python command. > - I can't find a way to have this programmable source saved as a file, > so that other people can use it. > - If people want to have more flexibility using my programmable > source, they need to get their hands in the code, which is precisely > what I am trying to avoid. > > Are there solutions to these issues? Or should I simply go make a > plugin, instead of a programmable source? > > Cheers > Fred > > > > 2017-02-16 15:09 GMT+01:00 Cory Quammen : >> Hi Fred, >> >> Nothing built-in comes to mind to handle 4D data this way, but you >> could potentially write a Programmable Source to read the file and do >> the slicing. This would be similar to writing an external program to >> extract a 3D hyperplane, but you could at least refine the hyperplane >> definition within the Programmable Source and update the results >> "live" in ParaView. >> >> HTH, >> Cory >> >> On Wed, Feb 15, 2017 at 5:10 PM, Frederic Perez >> wrote: >>> Hi all, >>> >>> Is there a way to import (any format) a 4D array in paraview, then to >>> slice one of the dimensions (i.e. use only one 3D hyperplane), and >>> plot the remaining 3D array with paraview's volume rendering? >>> >>> I know I could manipulate the data to make it 3D before using it in >>> Paraview, but I was looking for a way to do this directly. >>> >>> Cheers >>> Fred >>> ___ >>> 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 >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. ___ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] Import a four-dimensional array and "slice" one dimension to plot in 3D
Thank you for this suggestion. I have been looking at programmable sources, and although they are new to me, I think I have found a few issues for my objective: - I seem unable to import a few python packages that I know I can import in a usual python command. - I can't find a way to have this programmable source saved as a file, so that other people can use it. - If people want to have more flexibility using my programmable source, they need to get their hands in the code, which is precisely what I am trying to avoid. Are there solutions to these issues? Or should I simply go make a plugin, instead of a programmable source? Cheers Fred 2017-02-16 15:09 GMT+01:00 Cory Quammen : > Hi Fred, > > Nothing built-in comes to mind to handle 4D data this way, but you > could potentially write a Programmable Source to read the file and do > the slicing. This would be similar to writing an external program to > extract a 3D hyperplane, but you could at least refine the hyperplane > definition within the Programmable Source and update the results > "live" in ParaView. > > HTH, > Cory > > On Wed, Feb 15, 2017 at 5:10 PM, Frederic Perez > wrote: >> Hi all, >> >> Is there a way to import (any format) a 4D array in paraview, then to >> slice one of the dimensions (i.e. use only one 3D hyperplane), and >> plot the remaining 3D array with paraview's volume rendering? >> >> I know I could manipulate the data to make it 3D before using it in >> Paraview, but I was looking for a way to do this directly. >> >> Cheers >> Fred >> ___ >> 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 >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. ___ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] issue about deformed and misplaced color bars ...
Ufuk, I believe the issue you're running into is https://gitlab.kitware.com/paraview/paraview/issues/17197, more so than the one your pointed. I have a fix for 17197 on the way: https://gitlab.kitware.com/paraview/paraview/merge_requests/1393 Utkarsh On Fri, Feb 17, 2017 at 4:39 AM, wrote: > Hi, > > I was using Catalyst with 5.2 and the color bars are shown as tiny and > also misplaced when it is compared with ParaView output. I also checked it > with 5.3RC1 and the issue is still in there. So, is there any plan to fix > it in 5.3. There ware also discussion about it in the mail list and it > seems that it is related with following issue but aim not sure. > > https://gitlab.kitware.com/paraview/paraview/issues/17113 > > Regards, > > --ufuk > > > > ___ > 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 > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
Ben/Fabian I just did another quick test and it looks like the PVSB 5.2 build on my OS X 10.9 system that this flag was required to get the build to work: -DCMAKE_OSX_SDK="macosx10.9” and this one was apparently optional and not required: -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/M acOSX.platform/Developer/SDKs/MacOSX10.9.sdk” Thanks for your help. Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -Original Message- From: Ben Boeckel Reply-To: "ben.boec...@kitware.com" Date: Friday, February 17, 2017 at 7:57 AM To: Rick Angelini Cc: Fabian Wein , ParaView Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? On Fri, Feb 17, 2017 at 12:43:17 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cmake was complaining about CMAKE_OSX_SDK not being set … > I’m not sure if I needed to set both variables, but I recalled seeing >this > in a mail thread, so I just set it! 8-) Ah, then you just set it to what you had. That's fine :) . I just saw "10.9" and assumed you were setting it to an older version. --Ben smime.p7s Description: S/MIME cryptographic signature ___ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] issue about deformed and misplaced color bars ...
Hi Ufuk, I'm not sure if this fix will make it into the 5.3 release. We'll try but we have a pretty hard deadline for the release. As a workaround, while Trace is not capturing the movement the Python state does. You can use that information to set the desired values in your Catalyst Python script. The example from my Python state is: rTDataLUTColorBar = GetScalarBar(rTDataLUT, renderView1) rTDataLUTColorBar.Position = [0.30443396226415076, 0.7281124807395994] rTDataLUTColorBar.Position2 = [0.43027, 0.1201] rTDataLUTColorBar.Orientation = 'Horizontal' rTDataLUTColorBar.Title = 'RTData' rTDataLUTColorBar.ComponentTitle = '' rTDataLUTColorBar.TitleFontSize = 16 rTDataLUTColorBar.LabelBold = 1 rTDataLUTColorBar.LabelItalic = 1 rTDataLUTColorBar.LabelFontSize = 16 Currently there's an issue with the LabelFontSize. I've entered a gitlab issue at https://gitlab.kitware.com/paraview/paraview/issues/17194 Thanks for checking on this. Best, Andy On Fri, Feb 17, 2017 at 4:39 AM, wrote: > Hi, > > I was using Catalyst with 5.2 and the color bars are shown as tiny and > also misplaced when it is compared with ParaView output. I also checked it > with 5.3RC1 and the issue is still in there. So, is there any plan to fix > it in 5.3. There ware also discussion about it in the mail list and it > seems that it is related with following issue but aim not sure. > > https://gitlab.kitware.com/paraview/paraview/issues/17113 > > Regards, > > --ufuk > > > > ___ > 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 > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] Automating contour isosurface values in parallel Catalyst Python script
Glad to hear!
Also, thanks for replying to the list.
On Fri, Feb 17, 2017 at 4:50 AM, wrote:
>
> Hi Andy and Joachim,
>
> I adapted Andy's suggestions, and my script is now both slightly simpler
> (no mpi4py or numpy dependencies) and works on both machines.
>
> PS. I cc'd the ParaView mailing list, since I started this thread on it,
> and forgot "reply to all" in one of my own responses...
>
> Thanks again for the help, and best regards,
>
> Yvan
>
> - Mail original -
> De: "Andy Bauer"
> À: "Yvan Fournier" , "Joachim Pouderoux" <
> joachim.pouder...@kitware.com>
> Envoyé: Jeudi 16 Février 2017 16:15:03
> Objet: Re: [Paraview] Automating contour isosurface values in parallel
> Catalyst Python script
>
>
>
> Hi Yvan,
>
> I inlined some answers below...
>
> Best,
> Andy
>
> ps. I cc'ed Joachim since it looks like you meant to cc him but did not.
>
>
>
>
>
>
>
> On Thu, Feb 16, 2017 at 6:25 AM, < yvan.fourn...@free.fr > wrote:
>
>
> Hi Andy and Joachim,
>
> Thanks for your answers. I suspected I would need a solution of this sort.
>
> I prefer computing the min and max myself rather than adapting a Catalyst
> edition, as I often use full/default ParaView with OSMesa instead of
> Catalyst Editions (I only got a "standard" base + Python + extensions...
> edition working very recently; with older versions of the editions, some
> filter was always missing and I could not use Python scripts generated by
> the Coprocessing Generator plugin).
>
>
>
> I generally just use the full PV version also. It is only when I need to
> be very light on memory that I switch to the Catalyst editions. Others have
> noted that the Catalyst editions are easier to build on HPC systems though
> and prefer that route.
>
>
>
>
> I made good progress, and now have a solution which works with a 1 or
> 2-week-old build from the master branch, using numpy, but does not work on
> a build with ParaView 5.1.2 on an older machine due to missing features:
>
> - "from paraview.vtk.numpy_interface.algorithms import *" fails,
> complaining it does not find numpy and tells me to check it was installed
> properly (it is installed, though might have been installed after the
> ParaView build)
>
>
>
> I do not know about this issue as I have not seen it before and was not
> involved with the integration. Maybe Joachim knows. Otherwise I would
> suggest going back to the PV mailing list.
>
>
>
>
> - using:
> controller = coprocessing.vtkCompositeMultiProcessContro
> ller.GetGlobalController()
> if controller and controller.IsA("vtkMPIController") and
> controller.GetNumberOfProcesses()
> > 1:
> from mpi4py import MPI
> comm = vtkMPI4PyCommunicator.ConvertToPython(controller.GetCommunicator())
>
>
>
>
> In cases like this I just use:
>
> import vtk
>
> controller = vtk.vtkMultiProcessController.GetGlobalController()
>
> c.AllReduce(, , , vtk.vtkCommunicator.MAX_OP)
>
>
> to get the max values. vtkCommunicator has the named constants for
> operations. The "global" communicator will be the one that Catalyst uses
> which may be a subcommunicator of MPI_COMM_WORLD. I'm not sure if mpi4py
> will be over the Catalyst MPI processes or all of them. Also, you may want
> to try "from paraview import vtk" instead of just "import vtk". Less VTK
> Python stuff should be imported then but it may be missing something you
> want. I don't use vtkMPI4PYCommunicator so I cannot say how well that
> should work for your needs.
>
>
>
>
> I have a "NameError: global name 'vtkMPI4PyCommunicator' is not defined"
> message
>
> In my earlier tests, I tried simply using the AllReduce() method from the
> controller, with vtkArrays, but I was stuck on finding the correct value
> for the last argument, which seems to be an integer describing the
> collective reduction operation (I need min and max). But I was unable to
> find any examples for this in Python, (whether Googling for examples or
> printing dict() and (help() of various Python objects).
> The documentation only specifies some methods may not be available in
> Python...
>
> Are there named constants describing those operations in the Python
> wrappers of vtkMPIController ?
> I assume I could find the integer values in the C++ documentation/sources,
> but I would rather have named constants for readability and in case of
> future changes.
> I guess using the vtkMPIController would slightly simplify the code and
> reduce dependancy to some external Python modules.
>
> Thanks for the help, and best regards,
>
> Yvan
>
> - Mail original -
> De: "Andy Bauer" < andy.ba...@kitware.com >
> À: "Joachim Pouderoux" < joachim.pouder...@kitware.com >
> Cc: "Yvan Fournier" < yvan.fourn...@free.fr >, "ParaView" <
> paraview@paraview.org >
> Envoyé: Mardi 14 Février 2017 21:27:06
> Objet: Re: [Paraview] Automating contour isosurface values in parallel
> Catalyst Python script
>
>
>
>
>
>
> Hi Yvan,
>
> Another option is just to compute it yourself. The reason that the global
> min and max aren't know in Catalyst is
Re: [Paraview] PVSB 5.2: missing modules and plugins after "make install"
On Fri, Feb 17, 2017 at 13:17:37 +, Michel Rasquin wrote: > Has anybody already tested successfully PVSB 5.2 from the install > directory without loosing plugins and other module down the road? Oh, running from the install directory? That's not really fully supported. The reason is that we have 3 places ParaView ends up during the superbuild: - the build tree - the install tree - the package Getting it to work in all three on all platforms is not really feasible, so we prioritize them as: - the package (because this has to work) - the build tree (so that tests can be run) - the install tree It is best to make the package (ctest -R cpack-paraview-TGZ) and then either run from _CPack_Packages/... or extract the generated tarball somewhere else and run that. There is also `make install`, which should also work just fine (it basically just does the packaging step to a given directory and then doesn't actually make the package). --Ben ___ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] PVSB 5.2: missing modules and plugins after "make install"
Hi Cory and Ben, After your email, I updated my PVSB 5.2 version, recompiled from a clean build directory and reinstalled to a fresh directory. Unfortunately, I can still observe the same behavior as before so the latest changes you mentioned in your email did not fix this issue. If this can help, my new sha key is ba573eace90abaeb79247e570ff4509a54e75b76. Has anybody already tested successfully PVSB 5.2 from the install directory without loosing plugins and other module down the road? Thanks. Best regards, Michel From: Ben Boeckel Sent: Monday, February 13, 2017 3:23:41 PM To: Cory Quammen Cc: Michel Rasquin; paraview@paraview.org Subject: Re: [Paraview] PVSB 5.2: missing modules and plugins after "make install" On Sat, Feb 11, 2017 at 17:48:27 -0500, Cory Quammen wrote: > Will updating to the current superbuild master address the missing > plugins issue Michel is seeing? It looks like there have been some > minor changes on plugin handling in linux since > 4ec37480a6f1ad39c9aa3168c2f0e6a1b0147b16. Yes, it's possible. If you look at the output of the packaging step, there is probably some set of system libraries being pulled into the package which should not be there. --Ben ___ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
On Fri, Feb 17, 2017 at 12:43:17 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cmake was complaining about CMAKE_OSX_SDK not being set … > I’m not sure if I needed to set both variables, but I recalled seeing this > in a mail thread, so I just set it! 8-) Ah, then you just set it to what you had. That's fine :) . I just saw "10.9" and assumed you were setting it to an older version. --Ben ___ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
Cmake was complaining about CMAKE_OSX_SDK not being set … I’m not sure if I needed to set both variables, but I recalled seeing this in a mail thread, so I just set it! 8-) Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -Original Message- From: Ben Boeckel Reply-To: "ben.boec...@kitware.com" Date: Thursday, February 16, 2017 at 4:00 PM To: Rick Angelini Cc: Fabian Wein , ParaView Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? On Thu, Feb 16, 2017 at 16:53:55 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Fabian - thank you - that was enough of a hint to get me over the hump. > Switched my build to qt5 AND based on some information from a previous > email thread, I added the following to my CMAKE command: > > -DCMAKE_OSX_SDK="macosx10.9" \ > >-DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/ >M > acOSX.platform/Developer/SDKs/MacOSX10.9.sdk" That shouldn't be necessary for Qt5 (though if it works, that's great). --Ben smime.p7s Description: S/MIME cryptographic signature ___ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] Automating contour isosurface values in parallel Catalyst Python script
Hi Andy and Joachim,
I adapted Andy's suggestions, and my script is now both slightly simpler (no
mpi4py or numpy dependencies) and works on both machines.
PS. I cc'd the ParaView mailing list, since I started this thread on it, and
forgot "reply to all" in one of my own responses...
Thanks again for the help, and best regards,
Yvan
- Mail original -
De: "Andy Bauer"
À: "Yvan Fournier" , "Joachim Pouderoux"
Envoyé: Jeudi 16 Février 2017 16:15:03
Objet: Re: [Paraview] Automating contour isosurface values in parallel Catalyst
Python script
Hi Yvan,
I inlined some answers below...
Best,
Andy
ps. I cc'ed Joachim since it looks like you meant to cc him but did not.
On Thu, Feb 16, 2017 at 6:25 AM, < yvan.fourn...@free.fr > wrote:
Hi Andy and Joachim,
Thanks for your answers. I suspected I would need a solution of this sort.
I prefer computing the min and max myself rather than adapting a Catalyst
edition, as I often use full/default ParaView with OSMesa instead of Catalyst
Editions (I only got a "standard" base + Python + extensions... edition working
very recently; with older versions of the editions, some filter was always
missing and I could not use Python scripts generated by the Coprocessing
Generator plugin).
I generally just use the full PV version also. It is only when I need to be
very light on memory that I switch to the Catalyst editions. Others have noted
that the Catalyst editions are easier to build on HPC systems though and prefer
that route.
I made good progress, and now have a solution which works with a 1 or
2-week-old build from the master branch, using numpy, but does not work on a
build with ParaView 5.1.2 on an older machine due to missing features:
- "from paraview.vtk.numpy_interface.algorithms import *" fails, complaining it
does not find numpy and tells me to check it was installed properly (it is
installed, though might have been installed after the ParaView build)
I do not know about this issue as I have not seen it before and was not
involved with the integration. Maybe Joachim knows. Otherwise I would suggest
going back to the PV mailing list.
- using:
controller =
coprocessing.vtkCompositeMultiProcessController.GetGlobalController()
if controller and controller.IsA("vtkMPIController") and
controller.GetNumberOfProcesses() > 1:
from mpi4py import MPI
comm = vtkMPI4PyCommunicator.ConvertToPython(controller.GetCommunicator())
In cases like this I just use:
import vtk
controller = vtk.vtkMultiProcessController.GetGlobalController()
c.AllReduce(, , , vtk.vtkCommunicator.MAX_OP)
to get the max values. vtkCommunicator has the named constants for operations.
The "global" communicator will be the one that Catalyst uses which may be a
subcommunicator of MPI_COMM_WORLD. I'm not sure if mpi4py will be over the
Catalyst MPI processes or all of them. Also, you may want to try "from paraview
import vtk" instead of just "import vtk". Less VTK Python stuff should be
imported then but it may be missing something you want. I don't use
vtkMPI4PYCommunicator so I cannot say how well that should work for your needs.
I have a "NameError: global name 'vtkMPI4PyCommunicator' is not defined"
message
In my earlier tests, I tried simply using the AllReduce() method from the
controller, with vtkArrays, but I was stuck on finding the correct value for
the last argument, which seems to be an integer describing the collective
reduction operation (I need min and max). But I was unable to find any examples
for this in Python, (whether Googling for examples or printing dict() and
(help() of various Python objects).
The documentation only specifies some methods may not be available in Python...
Are there named constants describing those operations in the Python wrappers of
vtkMPIController ?
I assume I could find the integer values in the C++ documentation/sources, but
I would rather have named constants for readability and in case of future
changes.
I guess using the vtkMPIController would slightly simplify the code and reduce
dependancy to some external Python modules.
Thanks for the help, and best regards,
Yvan
- Mail original -
De: "Andy Bauer" < andy.ba...@kitware.com >
À: "Joachim Pouderoux" < joachim.pouder...@kitware.com >
Cc: "Yvan Fournier" < yvan.fourn...@free.fr >, "ParaView" <
paraview@paraview.org >
Envoyé: Mardi 14 Février 2017 21:27:06
Objet: Re: [Paraview] Automating contour isosurface values in parallel Catalyst
Python script
Hi Yvan,
Another option is just to compute it yourself. The reason that the global min
and max aren't know in Catalyst is that it requires communication but many
times the value isn't needed so in order to make Catalyst more efficient it
doesn't compute that value for you automatically. In the Python scripts you can
import mpi4py or import vtk and use the vtkMultiProcessController to do the
global operation. Note th
[Paraview] issue about deformed and misplaced color bars ...
Hi, I was using Catalyst with 5.2 and the color bars are shown as tiny and also misplaced when it is compared with ParaView output. I also checked it with 5.3RC1 and the issue is still in there. So, is there any plan to fix it in 5.3. There ware also discussion about it in the mail list and it seems that it is related with following issue but aim not sure. https://gitlab.kitware.com/paraview/paraview/issues/17113 Regards, --ufuk ___ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] ParaView 5.3.0 Release Candidate 1 binaries are available for download
Hi, Yes the issue was related with make version. Actually, I was using pretty old one (cmake/3.5.2) and after upgrading it to cmake/3.7.2, the error is gone. Thanks for your help, --ufuk ___ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
