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/
>
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
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
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,
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:
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
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
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
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
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
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
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
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
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
14 matches
Mail list logo