Hello David,
Somewhat related to the above topic, this issue would also be important for the
3.10.1 update.
http://paraview.org/Bug/view.php?id=11893
/mark
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitwa
Is there currently any particular OpenFOAM dataset being used for testing? If
so, I could convert it into the compact-face format.
Otherwise the dataset from Takuya (cavity tutorial I think) should be okay -
there are no license issues.
> I have a dataset contributed by Mark but am not sure abo
> This has been applied to release and master.
Perfect! Thanks David and Takuya.
Sorry I still didn't have time to compile and test it myself.
/mark
DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended solely
for the use of the addressee(s). It may contain confid
Hi Bastian,
> I am just wondering what this patch is good for?
It handles the case where 'faces' are written in a form similar to that used by
CompactListList, which can be more efficient in some cases.
/mark
DISCLAIMER:
This electronic transmission (and any attachments thereto) is intended s
When is 3.10 slated for release?
I have a patch from Takuya OSHIMA for handling a compact face format in
OpenFOAM. It would be very important to get this in before the next release.
What tests are needed and what is the time-frame to squeezing in this type of
change before the 3.10 release?
/ma
>
> hg clone https://pau...@bitbucket.org/pauloh/pyevtk
After cloning the repository, I don't find any of the C source files.
$ hg status -A
C .hgtags
C MANIFEST
C README.txt
C dev.py
C setup.py
C src/LICENSE
C src/__init__.py
C src/cevtk.pyx
C src/examples/__init__.py
C src/examples/group.py
C
> I added a feature request : http://public.kitware.com/Bug/view.php?id=10045
> Mark - hopefully someone will add this for you in the near future.
Thanks David.
Adding it myself and submitting a patch would also be possible, but perhaps in
Jan.
In the meantime I just converted it from obj to vtk
riginal Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: Monday, November 09, 2009 1:25 PM
> To: Olesen, Mark
> Cc: ParaView; vtk-develop...@vtk.org
> Subject: Re: [Paraview] Improving vtkDataArraySelection ...
> and a question of the general
> Forwarding this to the vtk-developer's list.
>
> Utkarsh
Thanks, does this mean that I should subscribe and post there, or just
cross-post from here (Paraview)?
/mark
> -- Forwarded message --
> From: Mark Olesen
> Date: Wed, Nov 4, 2009 at 10:21 AM
> Subject: [Paraview] Imp
Is it safe to assume that the github Kitware/ParaView repository will be around
for a while?
/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, o
Hi Takuya,
> // 1. If one is happy with only updating the active view
> if(this->view()) // may be null if no active view is present
>{
>this->view()->render();
>}
> // 3. All views including irrelevant ones may be rendered by
> pqApplicationCore::instance()->render();
Both of t
On a related tangent to the rendering issue:
What method is needed to get the 3d view window to refresh.
I have a customized reader panel with a few Qt checkboxes.
When I select, for example, "Add Labels", the slot sends it to the server
manager and it is correctly updated.
However, the text label
> Tada, all works. So there's definately some problem with NVidia
> Drivers + OpenMPI1.2.x
We've had a number of problems with some of the newer nvidia drivers and some
commercial software (crashes, mouse events getting lost, etc).
We hadn't any luck with any of the newer 185 driver series, bu
> > To my knowledge Theora is free of any formal trouble, and sufficient
> > quality to be proposed for a default encoder for any platform, not?
> >
> > -- Dominik
>
> The problem probably is that ParaView is BSD-style licensed, while
> Ogg/Theora is LGPL'ed.
The FAQ claims BSD-style licensing:
> Would someone please tell me if Paraview supports HW (OpenGL)
> acceleration and how to enable it.
Sure it supports OpenGL. You just need to have the appropriate hardware
drivers working.
Assuming you are using Linux (you didn't say which OS you have), check
these things:
# see which libraries
> I had an OpenGL related problem building ParaView 3.5 and 3.6. I'm
> running
> OpenSUSE 11.1, 2.6.27.23-0.1, x86_64, with NVIDIA version 185.18.14
> drivers
> and OpenGL which came from NVIDIA's repository, i.e. here
We had many problems with the 185 series (keyboard lockup, lost mouse,
etc. se
> I've been having trouble for weeks getting ParaView to work. I've
> finally gotten a build that loads and seems to work well until I try
> to load an openFOAM casefile. In ParaView, I open the file
> (casename.foam) and then it asks for a reader because the program
> doesn't know how to read the
> I just tried that and it is now giving me a segmentation fault... I am
> using the following line:
> file.write(reinterpret_cast(size), 4);
The segfault isn't surprising. If you obtain the address of the variable
first, I suspect you'll be much happier:
int size;
file.write(reinterpret_cas
I'm noticing some very odd behaviour when using the OpenFOAM
library-based reader (the one that is part of OpenFOAM, not the one
shipped with VTK).
The reader uses SetNumberOfOutputPorts(2), with port 0 corresponding to
normal cell-based volume/point data and port 1 corresponding to any
Lagrangian
> > a_0.vtk
> > a_60.vtk
> > a_360.vtk
> > a_660.vtk
> > a_960.vtk
> >
> > The numbers about is in seconds from OpenFOAM simulation. I load
> > the files into paraview-3.4.0. I am able to to animation and plot
> > transient data.
> > However, the time step indicates 0, 1, 2, 3, 4 instead of the r
After 5.4 is released, can we expect (hope) for a move from CVS to git
or subversion?
/mark
-Original Message-
From: paraview-boun...@paraview.org
[mailto:paraview-boun...@paraview.org] On Behalf Of Bob Obara
Sent: Monday, January 19, 2009 8:13 PM
To: vtk-develop...@public.kitware.com
> We actually have an internal git that tracks the ParaView cvs. Some us
> (including me) has been using it for a while now. It is not totally
> issue free (mostly due to the cvs-git bridge) so we don't plan to make
> it public. I suspect that we will move to svn at one point and
> possibly provid
> 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.
This will be a very welcome addition. The hard-coded paths in the cmake
files a
fü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@para
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 CMakeCach
I've been thinking about this for quite some time, but the website(s)
being down prompted me to finally post it.
I know that Paraview and VTK have been using cvs for a very long time,
but perhaps it might be time to consider migrating to a more modern
source code management (SCM) system - for exam
> How about using EnSight format? There we can use separate files to
> store mesh data and variable data
Okay, but if you have particles be aware of this bug:
http://vtk.org/Bug/view.php?id=7453
/mark
This e-mail message and any attachments may contain
legally privileged, confidential or proprie
MarkMail (www.markmail.org) has imported the Paraview/VTK mailing lists
into their archive, search, index and database system. It seems like a
good way to search the mailing lists.
To search all of the lists, this URL can be used:
http://markmail.org/search/?q=list:vtk%20list:paraview
To limit
28 matches
Mail list logo