Anton, thanks for your trust!
I've created a merge request for VTK in order to use TBB instead of
sequential behavior when dealing with parallel code:
https://salsa.debian.org/science-team/vtk9/-/merge_requests/4
I would like to do the same for ParaView but the salsa repo is not sync
wit
Hi François,
thanks for a suggestion! I have added you to Debian Science Team on salsa.
Feel free to contribute!
Best regards
Anton
Am Do., 22. Apr. 2021 um 21:46 Uhr schrieb François Mazen :
> Hello,
>
> I'm wondering why VTK and ParaView are build with the "Sequential
Hello,
I'm wondering why VTK and ParaView are build with the "Sequential"
default backend for parallelization (vtkSMPTools backend)?
This makes ParaView run slower compared to official binary releases
from Kitware, which are built with Threaded Building Blocks (TBB).
Hence, any
visualization of 3D objects
with VTK
A python module for scientific visualization, analysis and animation
of 3D objects and point clouds based on VTK and numpy.
Intuitive and straightforward API which can be combined with VTK seamlessly in
a program, whilst mantaining access to the full range of
ot be used to build some apps on top of it.
There are some missing files (mostly cmake stuff) that break
compilation.
But the most annoying issue is that Paraview ships a specific version
of vtk > 6
and thus the requirement for python-vtk6 is wrong!!
Certainly that will need to be updated to pyt
some missing files (mostly cmake stuff) that break compilation.
But the most annoying issue is that Paraview ships a specific version of vtk > 6
and thus the requirement for python-vtk6 is wrong!!
To work around this, paraview can be built without much problem
provided we get rid of python-vt
On 2019-03-21 14:51, Drew Parsons wrote:
Hi Gert and other VTK keepers,
what's the state of VTK-8 for Debian?
The reason I ask is that I need a newer version of paraview to view
complex XDMF mesh data. I tried building the new paraview versions
(5.5, 5.6), but the amount of VTK pat
On 2019-03-21 14:59, Johannes Schauer wrote:
Hi Drew,
Quoting Drew Parsons (2019-03-21 07:51:24)
Hi Gert and other VTK keepers,
I'm by no means a VTK keeper but I guess you found me via:
https://lists.debian.org/150980836026.28076.14119532204188467883@localhost
I was trawling the re
Hi Gert and other VTK keepers,
what's the state of VTK-8 for Debian?
The reason I ask is that I need a newer version of paraview to view
complex XDMF mesh data. I tried building the new paraview versions
(5.5, 5.6), but the amount of VTK patching required (to build against
vtk6 or vtk
Hi Drew,
Quoting Drew Parsons (2019-03-21 07:51:24)
> Hi Gert and other VTK keepers,
I'm by no means a VTK keeper but I guess you found me via:
https://lists.debian.org/150980836026.28076.14119532204188467883@localhost
> what's the state of VTK-8 for Debian?
The packagin
> Am Donnerstag, den 22.03.2018, 18:11 +0100 schrieb Christophe Trophime:
>> >
>> >
>> Could we generate, as an alternative, VTK packages when building
>> ParaView?
>> From my experience it's feasable...
>> The only trouble, here , is with p
Am Donnerstag, den 22.03.2018, 18:11 +0100 schrieb Christophe Trophime:
> >
> >
> Could we generate, as an alternative, VTK packages when building
> ParaView?
> From my experience it's feasable...
> The only trouble, here , is with python plugins..
While this may
>
> We are aware of the issues with building VTK separately from ParaView.
> Unfortunately, this seems to be an issue inherent in the ParaView
> workflow. We've tried to separate them out before, and it hasn't worked
> well. We don't have the manpower to maint
rt of the packaging process for VTK 9 will
be getting these non-upstreamed patches into Debian, and making sure
that the latest versions that DO have our patches also get into Debian.
How do you handle copyright and licensing review? Do you look at every
single file manually, or do you have a s
Hello Kyle,
Am Mittwoch, den 21.03.2018, 22:10 +0100 schrieb Anton Gladky:
> > 4. VTK 5 and 6 are marked as "conflicting" with each other. Why is
> > this? The libraries and headers are name-mangled to allow multiple
> > versions of VTK to coexist. Is there another
Thanks Anton for CCing me. (I've worked quite a bit on the integration of
VTK7 into Debian.)
> > 1. In general, what were the biggest challenges you faced in packaging
VTK?
In my view, the hardest thing is to get new VTK versions through the
license check. That's because VTK
Hi Kyle,
thanks for your interest on DEB-VTK-packaging! It is always pleasure to have
a responsive upstream. I was involved into the packaging on VTK 6 and
partly VTK 5.
> 1. In general, what were the biggest challenges you faced in packaging VTK?
The most difficult challenge was to use sys
Hello all,
My name is Kyle, I work at Kitware, Inc. I am working on an official,
Kitware-supported Ubuntu package for the upcoming VTK 9, and my goal is
to get it accepted into the Ubuntu Universe repository. (Ideally, I
would like to get this into mainline Debian as well.) Rather than
Hi Gert,
thanks for the info and analysis! Well, to make a decision
we should firstly check how many packages are not able
to be built "out of box" with the new backend. Than we can
decide what to do with this rest of packages.
I do not like the idea to keep both versions of VTK par
> I wonder whether we could keep VTK-6 for projects using the old API
> and force VTK-7-only projects to use the new one? VTK-6 and VTK-7
> should be co-installable, right?
>
I think the language bindings are not co-installable, but those could
be dropped from the VTK-6 package.
-Gert
On Thu, 2017-04-06 at 10:27 +0200, Gert Wollny wrote:
> Hello all,
>
> I just drop this here for future reference.
Thanks for looking into it and summarizing your findings.
> I've experimented a bit with VTK-7.1 and among other, minor issues I
> came across the problem t
Hello all,
I just drop this here for future reference.
I've experimented a bit with VTK-7.1 and among other, minor issues I
came across the problem that VTK now defaults to, and, hence,
encourages the use of, a new renderer backend, called OpenGL2 that
requires an OpenGL 3.2 context. Th
;>:
> >
> > I will try to find some time to send an email around to the team this
> > weekend.
>
> Hi Ghis,
>
> Did you ever get around to this? If so, what was the team reaction? Any
> estimate on when vtk7/python3-vtk7/python-vtk7 packages might appea
he default switches.
> >
> > If nobody voices another opinion I'd prepare an upload that does
> > just that for libvtk6-dev.
>
> You can surely do it. The only question, whether it really makes
> sense to do it now, if we do not want to start the transition
> pr
that does just
> that for libvtk6-dev.
You can surely do it. The only question, whether it really makes sense
to do it now, if we do not want to start the transition process, doing
source uploads for all vtk-dependent packages. I would do it before
we prepare vtk7. But it is up to you.
&g
Hello,
I've added debian-science to the CC because VTK is group maintained
within this group.
Am Mittwoch, den 19.10.2016, 09:16 +0200 schrieb nkr:
> I got you email address from the libvtk6-dev page. I want to suggest
> creating a virtual-package for vtk library (vtk-dev or
u...@debian.org (Aaron M. Ucko) writes:
> Ole Streicher writes:
>
>> I am currently packaging a Qt/C++ program (dpuser+qfitsview [1]) that
>> requires VTK6, and I am curious of how I have to specify the include
>> path and the libraries.
>
> To the best of my knowle
Ole Streicher writes:
> I am currently packaging a Qt/C++ program (dpuser+qfitsview [1]) that
> requires VTK6, and I am curious of how I have to specify the include
> path and the libraries.
To the best of my knowledge, the only build system VTK supports cleanly
is CMake, which I unde
Hi,
I am currently packaging a Qt/C++ program (dpuser+qfitsview [1]) that
requires VTK6, and I am curious of how I have to specify the include
path and the libraries.
The current version of libvtk6-dev in unstable/testing is 6.2.0, which
uses as include path
/usr/include/vtk-6.2/
and the
kend.
>>
>> Hi Ghis,
>>
>> Did you ever get around to this? If so, what was the team reaction? Any
>> estimate on when vtk7/python3-vtk7/python-vtk7 packages might appear on
>> the horizon? VTK 7 has so many improvements, would love to see it
>> packaged.
&g
.com>>:
>
> I will try to find some time to send an email around to the team this
> weekend.
Hi Ghis,
Did you ever get around to this? If so, what was the team reaction? Any
estimate on when vtk7/python3-vtk7/python-vtk7 packages might appear on
the horizon? VTK 7 has so many impr
Hi,
I'm testing out the vtk 5.8.0 (uploaded to experimental, currently in
the NEW queue)
built by Matheiu, using it to build visit 2.3.2.
visit currently expects to find its libraries in /usr/lib/vtk-5.8; in
this directory
there are already a bunch of .so links to the same .so libra
On Thu, Sep 8, 2011 at 11:30 AM, Mathieu Malaterre
wrote:
> hi,
>
> On Tue, Sep 6, 2011 at 7:36 PM, wrote:
>> Dear Mathieu,
>>
>> Uploading the package to experimental is blocked by lintian errors
>>
>>
>> Reject Reasons:
>> python-vtk: linti
hi,
On Tue, Sep 6, 2011 at 7:36 PM, wrote:
> Dear Mathieu,
>
> Uploading the package to experimental is blocked by lintian errors
>
>
> Reject Reasons:
> python-vtk: lintian output: 'package-installs-python-bytecode
> usr/lib/python2.6/dist-packages/vtk/__helper
Dear Mathieu,
Uploading the package to experimental is blocked by lintian errors
Reject Reasons:
python-vtk: lintian output: 'package-installs-python-bytecode
usr/lib/python2.6/dist-packages/vtk/__helper.pyc', automatically rejected
package.
python-vtk: lintian output: 'package-
Dear all,
I would like to start working on VTK package, in particular the VTK
5.8.0 release. As seen recently VTK package is becoming a beast to
maintain, as such I would like to move this package over to
debian-science-maint, and add myself as Uploader (and also switch
DM-Upload to Yes
On Mon, Sep 5, 2011 at 11:49 AM, Mathieu Malaterre
wrote:
> Is anyone tempted to make an upload of VTK 5.8.0 to experimental ? I
> did push my package on my personal webspace
>
> https://alioth.debian.org/~malat-guest/vtk/
Just for clarification, whoever is doing the NMU should of c
Hi,
On Mon, Sep 5, 2011 at 12:22 PM, Alastair McKinstry
wrote:
> Building your vtk 5.8.0 fails for me on i386:
>
> [ 48%] Building CXX object IO/CMakeFiles/vtkIO.dir/vtkXYZMolReader.cxx.o
> [ 48%] Building CXX object
> IO/CMakeFiles/vtkIO.dir/vtkZLibDataCompressor.cxx.o
> [
On 2011-09-05 10:49, Mathieu Malaterre wrote:
On Sat, Sep 3, 2011 at 12:21 PM, Mathieu Malaterre
wrote:
On Fri, Sep 2, 2011 at 7:42 PM, Mathieu Malaterre
wrote:
vtk 5.8 has been uploaded to my public space on vasks:
https://alioth.debian.org/~malat-guest/vtk/
I could not push to mentors
On Sat, Sep 3, 2011 at 12:21 PM, Mathieu Malaterre
wrote:
> On Fri, Sep 2, 2011 at 7:42 PM, Mathieu Malaterre
> wrote:
>> vtk 5.8 has been uploaded to my public space on vasks:
>>
>> https://alioth.debian.org/~malat-guest/vtk/
>>
>> I could not push to mentors
On Fri, Sep 2, 2011 at 7:42 PM, Mathieu Malaterre
wrote:
> vtk 5.8 has been uploaded to my public space on vasks:
>
> https://alioth.debian.org/~malat-guest/vtk/
>
> I could not push to mentors for some reason. This is a /minimal/
> package, I did not turn any new option on
1 at 4:35 AM, Steve M. Robbins wrote:
>>> >> I think the rest of this thread got off onto a tangent. In my mind,
>>> >> the germane question is not why Paraview embeds a patched VTK source
>>> >> tree but, rather: why is the paraview binary package now i
On Thu, Sep 01, 2011 at 10:58:33AM +0200, Mathieu Malaterre wrote:
> Meanwhile could someone please NMU vtk-5.6 with the proper
> fix and fix for lintian.
I will do an NMU that overrides the lintian errors, which will unblock
VTK and give us time to properly deal with the embedded lib
thread got off onto a tangent. In my mind,
>> >> the germane question is not why Paraview embeds a patched VTK source
>> >> tree but, rather: why is the paraview binary package now installing
>> >> the VTK tools like vtkWrapPython?
>> > Indeed, that'
uestion is not why Paraview embeds a patched VTK source
> >> tree but, rather: why is the paraview binary package now installing
> >> the VTK tools like vtkWrapPython?
> > Indeed, that's the actual issue. Thanks Steve.
> >
> >> Why does a running pa
aging as simple as possible. I prefer to escape "overpatching",
> > because it complicates a maintainance.
>
> Well, in the Debian packaging world, we are not doing it the easy way but the
> best way...
Agreed.
> And, here,
> the best way would be to drop VTK from Pa
omplicates a maintainance.
Well, in the Debian packaging world, we are not doing it the easy way but the
best way... And, here,
the best way would be to drop VTK from Paraview sources. I know it is a
lot of works at first but it is the way to go.
> I am afraid, that replacing the vtk is not an
Le jeudi 17 février 2011 à 15:18 +0100, Mathieu Malaterre a écrit :
> Dear all,
>
> I would like to integrate ActiViz.NET (VTK C# layer) as a new
> package for debian-science. Would this sound like the right place ?
Sure!
> Both Activiz.NET and mummy have been uploaded
Dear all,
I would like to integrate ActiViz.NET (VTK C# layer) as a new
package for debian-science. Would this sound like the right place ?
Both Activiz.NET and mummy have been uploaded to mentors as a
temporary location.
Thanks for comments,
--
Mathieu
--
To UNSUBSCRIBE, email to
On Sun, May 23, 2010 at 11:56 AM, Mathieu Malaterre
wrote:
> Hi,
>
> For some reason when compiling VTK (from the paraview package), VTK
> fails to compile and trigger an ICE in gcc:
>
> [ 34%] Building CXX object
> VTK/Hybrid/CMakeFiles/vtkHybrid.dir/vtkThinPlateSplin
Hi,
For some reason when compiling VTK (from the paraview package), VTK
fails to compile and trigger an ICE in gcc:
[ 34%] Building CXX object
VTK/Hybrid/CMakeFiles/vtkHybrid.dir/vtkThinPlateSplineTransform.o
/build/buildd-paraview_3.6.2-4-ia64-AgrR6s/paraview-3.6.2/VTK/Hybrid
e AFAIK. I did not check but I am pretty
> sure MPI option is ON.
Ok. I did check paraview is being build with -DPARAVIEW_USE_MPI:ON
And again in the CMakeListstxt:
SET(PARAVIEW_USE_MPI OFF CACHE BOOL "Build ParaView with MPI support")
SET(VTK_USE_MPI ${PARAVIEW_USE_MPI} CACHE INTERN
On Sun, Nov 1, 2009 at 4:47 AM, A. Maitland Bottoms wrote:
> Mathieu Malaterre writes:
> > I have added a couple of bugs, I'd like to get fixed for VTK 5.4.
>
> These weren't to bad to fix:
> Bug#552341: python-vtk: Suggest mayavi2 instead of removed mayavi
>
Mathieu Malaterre writes:
> I have added a couple of bugs, I'd like to get fixed for VTK 5.4.
These weren't to bad to fix:
Bug#552341: python-vtk: Suggest mayavi2 instead of removed mayavi
Bug#552343: vtk-doc: Remove md5 doxygen generated files
Bug#552352: libvtk5.2: Please turn VTK
Maitland,
On Thu, Oct 22, 2009 at 9:33 AM, Mathieu Malaterre
wrote:
> Maitland,
>
> On Wed, Aug 26, 2009 at 5:25 AM, A. Maitland Bottoms
> wrote:
>> Denis Barbier writes:
>> > 3. What is needed to have vtk 5.4 uploaded?
>>
>> I've brought some
Maitland,
On Wed, Aug 26, 2009 at 5:25 AM, A. Maitland Bottoms wrote:
> Denis Barbier writes:
> > 3. What is needed to have vtk 5.4 uploaded?
>
> I've brought some of the good things from the 5.2 branch into
> the 5.4 branch. I'll build and upload for experim
This is a follow up on:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549203
Once the boost graph parallel package will be uploaded, one will be
able to compile VTK 5.4 taking advantage of the new Titan toolkit (*).
Packaging file can be found here:
http://gdcm.svn.sourceforge.net/svnroot
57 matches
Mail list logo
