Hi,
Can you share the dataset? feel free to email the file directly to me
if the datasize is hitting the mailing list limits.
Utkarsh
On Tue, Mar 1, 2016 at 11:07 AM, hadrien calmet wrote:
> Hello everyone,
>
> When I open the xmf file (metadata of my .h5) PV5.0 crash !
I don't think it works that way. I'd guess scipy has compiled code
that needs to built. It's be easiest to just build ParaView from
source and make it use the system python. That way you can then
install Python packages locally using your linux distribution and
those will be available within
Ivan,
Alas this is not currently supported in ParaView. ParaView doesn't
have a CGNS writer yet.
Utkarsh
On Tue, Feb 23, 2016 at 6:25 AM, Ivan Schrooyen
wrote:
> Hello
>
> I have tried to submit this topic to the mailing list but did not have any
> answer...
>
> I am
That is indeed a bug: http://www.paraview.org/Bug/view.php?id=15593
It's on the list of items to be fixed soon.
Utkarsh
On Wed, Mar 9, 2016 at 12:10 AM, hengxing pan wrote:
> Hi,all
> I got an error when I saved the screen shot of comparative render view .
> Does anyone
> Can the PV 'Find Data…' command be used to search attribute data of type
> string?
Alas, no. string arrays are currently not supported by "Find Data".
Utkarsh
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
install, I'd say having it included in 5.0.1 is
> less critical.
>
> Thanks
> joe
>
> Sent from my iPhone
>
>> On Mar 8, 2016, at 10:10 PM, Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
>> wrote:
>>
>> Thanks, Joe. How critical is it for this cha
Add `-DBUILD_TESTING:BOOL=OFF` to you cmake command line. That'll
disable the downloading of test datasets and void this error.
Utkarsh
On Thu, Mar 10, 2016 at 1:41 PM, Halter, Jon wrote:
> I'm trying to configure ParaView for use with OSMesa. I've successfully
> built OSMesa
This merge request should address this issue:
https://gitlab.kitware.com/vtk/vtk/merge_requests/1320
Once it's tested, reviewed etc. it'll be merged and I'll have it
updated in ParaView release 5.0.1 as well.
Utkarsh
On Wed, Mar 9, 2016 at 9:47 AM, Utkarsh Ayachit
<utkarsh.ayac...@kitware.
<antech...@gmail.com> wrote:
> Utkarsh Ayachit,
>
> Hello. Did you try the trick with EnSight geometry file reader? Thanks.
>
>
> 2016-03-03 17:51 GMT+03:00 Utkarsh Ayachit <utkarsh.ayac...@kitware.com>:
>>
>> > About test file. It's simple, IMHO. Generate an
ank you,
> Andy
>
> On Thu, Dec 17, 2015 at 1:05 PM, Utkarsh Ayachit
> <utkarsh.ayac...@kitware.com> wrote:
>>
>> Frank,
>>
>> First of all, thanks for all your exhausting testing, it's greatly
>> appreciated!
>>
&g
You're using a mix of advanced & simple API which is causing this
issue. Change your code as follows:
from paraview.simple import Show,Render
from paraview.simple import OpenDataFile
from paraview.simple import IsoVolume
reader = OpenDataFile("/home/metal-machine/Desktop/11.vts")
I think what you want is "Analglyph", however I noticed that it's not
exposed in the Save Screenshot dialog. What you can do is this:
1. Start ParaView with as
./bin/paraview --stereo --stereo-type=Anaglyph
2. Then when you choose "Save Screenshot" don't change the "Stereo Type".
On Fri,
Andrew/ Sam,
Thanks for exploring this as much as you did. I am afraid the issue is
not _FILE_OFFSET_BITS flag, however. As far as I can tell, the flag
gets set "globally" when CMake determinees during configure time that
"large file support" is possible. To follow the code here's how it
works:
> Just to chime in, a new vector graphics backend is implemented for OpenGL2
> and should be available in the new release.
To further clarify this statement, these changes won't be available in
ParaView 5.0.1, but the next significant release which will be 5.1
slated for Fall 2016.
> This makes me wonder when to use paraview.servermanager.LoadState?
> Should the example
> (http://www.paraview.org/Wiki/ParaView/Python/Loading_and_saving_state) be
> changed to use paraview.simple.LoadState?
There's really no reason to directly use servermanager.LoadState
except for advanced
> Do I have to download a different version to have the fix you made?
This change is not merged into the repository yet and hence not
available in 5.0.1 patch release as well. I was hoping someone would
get a change to review/test it before merging it.
Utkarsh
Folks,
ParaView 5.0.1-RC1 is now available for download[1]. For fixes that
went into this release, refer to the change log on bug tracker [2].
- The ParaView team
[1] http://www.paraview.org/download/
[2] http://www.paraview.org/Bug/changelog_page.php
> So, it seems that the two of you have been helpful in remedying my
> ignorance. Thanks.
Glad to help. I'd also suggested grabbing the free ParaVIew Guide PDF
to get a handle of some of the pipeline concepts in ParaView.
http://www.paraview.org/paraview-guide/
Utkarsh
Carson,
Can you share the data/script? I can dig in to see what could be
happening. BTW, Render() will never use LOD irrespective of
LODThreshold since Render() always triggers full-res render aka
StillRender.
Another thing to try is to run with "-dr" in both cases: pvpython and
ParaVIew GUI +
Adnrew,
Do you have a sample dataset to share to reproduce this issue?
Thanks
Utkarsh
On Fri, Feb 26, 2016 at 1:26 AM, Andrew wrote:
> Hello. We use Ansys CFX in our work but the standard post-processor CFD-Post
> consumes one of Ansys licenses while Paraview is free. So I
Sorry I cannot reproduce this. Can you attach sample scripts to
demonstrate what you're seeing? You can try with one of the sample
datasets that can be downloaded from paraview.org, if you need a time
varying dataset. Also what version of ParaView are you using?
On Thu, Feb 25, 2016 at 10:52 AM,
Cynthia,
Have you had the a look at the ParaView Guide?
http://www.paraview.org/paraview-guide/
It explains the concepts of filters and the data analysis pipelines
used in ParaView.
> So, firstly – If I read in a csv series of images, one image/file per moment
> in time, when I run a filter, the
Just set libGLU to empty. If I am not mistaken, it's optional (only
needed for some testing and GMV reader from VisItBridge which you can
disable).
On Wed, Feb 17, 2016 at 2:26 PM, Ganesh Vijayakumar
wrote:
> Hello,
>
> I'm trying to install Paraview-v5.0.0 with OS
hecking with my user regarding a dataset
> that can be shared. I will get back to you as soon as I hear from them,
> likely off list.
>
> Thanks
> joe
>
>> On Feb 11, 2016, at 1:28 PM, Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
>> wrote:
>>
>>
Livia,
I've put the script up as a code snippet on gitlab here:
https://gitlab.kitware.com/paraview/paraview/snippets/5
Utkarsh
On Tue, Feb 16, 2016 at 7:07 AM, wrote:
> Hi,
>
> It seems that it’s not possible to get the python_filter_generator.py
> script from
By, name of the dataset, do you mean name shown for the reader in the
pipeline browser? I am afraid there's no easy way of getting that name
from within a filter.
Utkarsh
On Fri, Feb 12, 2016 at 4:41 PM, Böttcher, Prof. Dr. Peter
wrote:
> I wrote a
Joe,
Do you have a sample dataset to share? It's possible there's a bug in
the multipage seek code when dealing with sub extents.
Utkarsh
On Thu, Feb 11, 2016 at 1:28 PM, Insley, Joseph A. wrote:
> Hi,
>
> I’ve been looking at loading tiffs as volumes using pv5.0 and am running
Vlad,
Since 4.0 is very old, can you try comparing with 4.4 as well? Let's
see if the slow down relates to changes to the rendering backend in
ParaView 5.0 or not.
Utkarsh
On Wed, Feb 10, 2016 at 9:56 PM, Liberman, Vladimir - 0881 - MITLL
wrote:
> I just upgraded from ver.
> I don't seem to be able to access properties in the VRPlugin from a Python
> source or filter. I can see other Plugins in the Python Shell (if I load the
> plugin before opening the shell for the first time), but only filter or
> source plugins. Is this related to the .xml file in some plugin
Awesome! Thanks for reporting back.
Utkarsh
On Mon, Feb 8, 2016 at 11:18 AM, Dennis Schridde <
dennis.schri...@uni-heidelberg.de> wrote:
> Hello again!
>
> I just wanted to report success: I built Mesa 11.2.0-devel-24ea81a myself,
> following the example of the Fedora specfile, but using
>
Folks,
Just wanted to let everyone know that we're working on a small patch
release of ParaView. For list of bug fixed/targeted for this patch release
is:
http://www.paraview.org/Bug/view_all_bug_page.php?filter=107037
The release should happen in month of Feb.
Utkarsh
I suspect OSMesa is not built with gallium/llvm driver and hence it's
failing to give a 3.2 context. I am a little rusty on where to find
info about Fedora packages. Can you check how the osmesa library is
being configured?
On Wed, Feb 3, 2016 at 12:19 PM, Dennis Schridde
Attached XML should do the trick. Load this as a plugin and then two
filters will be available ContinuousDilate3D and ContinuousErode3D.
On Mon, Feb 1, 2016 at 3:17 PM, Scott, W Alan wrote:
> Does anyone know the python (programmable filter, I suppose) needed to
> expose the
> Now I am trying to wrap up my algorithm into a filter class and thought that
> either RequestData() or RequestUpdateExtent() may be a good place to do it.
> Unfortunately the pipeline representation object is not available when I
> create the filter for the first time and press Apply. I also
32-bit windows binary...
> Thanks
>
> Kazuyoshi
>
> From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
> Subject: Re: [Paraview] ANN: ParaView 5.0.0 is available for download
> Date: Fri, 15 Jan 2016 08:08:48 -0500
>
>> No problem, I'll have the buil
As a side note, a ParaView 5.0.1 patch release is currently on the
charts for mid Feb. We'll get the OSPray issue fixed in that release.
Utkarsh
On Wed, Jan 27, 2016 at 8:15 PM, David E DeMarle
wrote:
> You might want to try a more recent version of pvOSPRay. Carson
As a side note, for changing coloring on representations, I'd suggest
using vtkSMPVRepresentationProxy::SetScalarColoring() [1] instead of
changing "ColorArrayName" directly. That takes care of setting up
lookup table etc. as ParaView would.
[1]
Dennis,
The ParaView Guide chapter 14 and this blog post
(http://kitware.com/blog/home/post/723) talks about how arrays on
composite datasets are treated. Anycase, attached is a script that's
better at finding the closest point and then computing the distance.
It uses a PointLocator to find the
A fix is being tested:
https://gitlab.kitware.com/paraview/paraview/merge_requests/585
I will generate new windows binaries once this lands.
Utkarsh
On Fri, Jan 22, 2016 at 10:14 AM, Utkarsh Ayachit
<utkarsh.ayac...@kitware.com> wrote:
> Looking into it. Seems like this is an i
> However this solution does not work for ProgrammableSource
> from paraview.simple import ProgrammableSource
> p=ProgrammableSource()
> p.Script = 'print(self.x)'
> p.RequestInformationScript = 'if "x" not in dir(self):\n self.x=12'
> UpdatePipeline()
> AttributeError: Attribute
Looking into it. Seems like this is an issue only for the non-mpi
ParaView binaries on Windows. A workaround for now is to use the MPI
version (ParaView-5.0.0-Qt4-OpenGL2-MPI-Windows-64bit). You will also
need to install MSMPI [1] separately to use the MPI enabled Windows
binaries, however.
[1]
Dennis,
Any sample dataset that you can share to try this on?
Utkarsh
On Fri, Jan 22, 2016 at 1:05 PM, Dennis Conklin
wrote:
> All,
>
>
>
> I have tried vtk.vtkKdTree before and never got the right answer, so before
> I write a bruteforce method I thought I should
> I agree that we should add a tag for it (note to Utkarsh ;) ).
Done.
https://gitlab.kitware.com/paraview/paraview-superbuild/tags
Utkarsh
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
response to Armin, I'd like to ask
> the continuation of win32 binary for a while (e.g. for 5.0.x
> releases).
> Sorry for my late response on the continuation; I overlooked
> the email about the dropping...
>
> Thanks,
> Kazuyoshi
>
> From: Utkarsh Ayachit <utkarsh.ay
Kazuyoshi,
Since there wasn't any response to an earlier email about dropping
Win32 binaries, we dropped them. We can certainly continue to build
them if there's a need for it -- and so it seems. Give us a few days
and I will have things setup to build the 32 bit binaries again.
Utkarsh
On Wed,
Try this, just run using pvbatch instead and pass the
"--use-offscreen-rendering" command line flag to it.
e.g. ./bin/pvbatch --use-offscreen-rendering /tmp/sample.py
Utkarsh
On Tue, Jan 12, 2016 at 11:53 AM, Borchi Leonardo
wrote:
> Hi to all,
>
>
>
> I would
n.com
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: 11. januar 2016 15:58
> To: Thomas Førde <thomas.fo...@ulstein.com>
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] using paraview with ompi and grid engine queue s
Folks,
ParaView 5.0.0 is now available for download[1]. Checkout the release
notes on the Kitware blog [2]. As always, we look forward to your
feedback [3].
Also stay tuned to the Kitware Blog [4] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
more!
Laboratory
> CISD/HPC Architectures Team
> Phone: 410-278-6266
>
>
>
>
> -Original Message-
> From: ParaView <paraview-boun...@paraview.org> on behalf of Rick Angelini
> <richard.c.angelini@mail.mil>
> Date: Friday, January 8, 2016 at 3:40 PM
>
> I notice however that the pictures are a bit more pixelated, specially on
> edges, I would assume this has something to do wiuth using osmesa instead of
> opengl, but can one correct this in one way or another.
I am not sure osmesa should be issue. Do you have an example image to
share that
artz Software, LLC
> [e]: mike.jack...@bluequartz.net
>
>> On Jan 7, 2016, at 11:35 AM, Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
>> wrote:
>>
>> Folks,
>>
>> ParaView 5.0.0-RC4 is now available for download [1]. Checkout the release
>>
Rick,
That sounds like this bug: http://www.paraview.org/Bug/view.php?id=15763
It was fixed 5.0.0.
Utkarsh
On Fri, Jan 8, 2016 at 3:31 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) wrote:
> In my original message, I attached the wrong cmake command
> Is this a problem related to my version of python 2.6?
Looks like you. You definitely need these components of ParaView to
get pvbatch working. Can you attach your CMakeCache again? Let's see
if that exposes some issue.
Thanks
Utkarsh
___
Powered
to it. That explains the linking issues.
Utkarsh
On Fri, Jan 8, 2016 at 9:49 AM, Thomas Førde <thomas.fo...@ulstein.com> wrote:
> Attached
>
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: 8. januar 2016 15:43
> To: Thomas Før
> As you suspect is was not enabled in the cmake.
I assume you're referring to the PARAVIEW_ENABLE_PYTHON flag? Yes,
that'd explain the pvbatch missing issue. However, I you seem to have
correctly enabled OSMesa support, so I am a little confused how you'd
be getting the X errors.
> But do I
Folks,
ParaView 5.0.0-RC4 is now available for download [1]. Checkout the release
notes on the Kitware blog [2].
- The ParaView team
[1] http://www.paraview.org/download/
[2] http://kitware.com/blog/home/post/998
___
Powered by www.kitware.com
Visit
Hard to say without the script you're trying to execute. In general,
pvbatch should have worked fine for your use-case too. If you have any
more info, that'd help.
Utkarsh
On Sun, Jan 3, 2016 at 8:45 AM, houssen wrote:
> Hello,
>
> I have a filter which writes some ACSII text
The following works in builtin (non-remote server) mode only.
global meta_data
meta_data =12
p = ProgrammableSource()
p.Script="""
global meta_data
print meta_data
"""
UpdatePipeline()
Output:
12
Utkarsh
checked. I tried explicitly unchecking the "Automatic Label Format" as you
> suggested, but it has no effect in this instance (as expected).
>
> Are you able to reproduce the effect from the attached state file?
>
> Thanks for your help, Bob
>
>
>
> On 29 December 20
Can you try unchecking the "Automatic Label Format" checkbox on the
"Edit Color Legend Parameters" dialog accessible from the "Color Map
Editor" panel? I think it's the label formatting that's causing the
issue.
Utkarsh
On Tue, Dec 29, 2015 at 4:07 PM, Bob Flandard wrote:
>
Folks,
ParaView 5.0.0-RC3 is now available for download[1]. Checkout the release
notes on the Kitware blog [2].
- The ParaView team
[1] http://www.paraview.org/download/
[2] http://kitware.com/blog/home/post/998
___
Powered by www.kitware.com
Visit
> Also, thank you for liaising with the OpenSWR team in order to check if they
> support or plan supporting OSMESA.
Frank, I am told that OpenSWR on Github should work with OSMesa. I
haven't tried it out myself, will give it a go once I get the a few
other issues ironed out. Just wanted to let
On Mon, Dec 21, 2015 at 9:13 AM, Aashish Chaudhary
wrote:
> Does this patch cleanly applies to all previous version of Mesa or only 11.1
> release? I am assuming that this patch existing in their current master?
Brian says "11.1, 11.0 and maybe earlier releases".
Since there were no objections voiced, we'll drop distributing 32-bit
Windows binaries for ParaView 5.0.
Thanks
Utkarsh
On Wed, Dec 16, 2015 at 4:20 PM, Utkarsh Ayachit <
utkarsh.ayac...@kitware.com> wrote:
> Folks,
>
> I am trying to see if there are any objections to dropping 3
Frank,
First of all, thanks for all your exhausting testing, it's greatly appreciated!
* OSMesa and MESA_GL_VERSION_OVERRIDE
Communicating with the Mesa team, we learnt that
MESA_GL_VERSION_OVERRIDE is a bad idea since it doesnt' really create
the specified OpenGL context. Thus if anything
Folks,
I am trying to see if there are any objections to dropping 32 bit
Windows binaries for the 5.0 release. We'll still distribute the 64
bit Windows binaries.
Thanks
Utkarsh
___
Powered by www.kitware.com
Visit other Kitware open-source projects
The issue is indeed that your OpenGL drivers are old. We're working on
something that will catch this and report it in a more graceful way.
Utkarsh
On Wed, Dec 16, 2015 at 3:12 PM, Fernando G. del Cueto wrote:
> Sadly it still crashes immediately after showing the splash
This page [1] is now accessible from here [2].
[1]
http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/EnvironmentVariables.html
[2] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/index.html
On Thu, Dec 10, 2015 at 3:51 AM, Joachim Pouderoux
Nothing that I am aware of. You could potentially write a filter that
coverts the cell type to an cell data attribute and then you could
threshold by that -- but that's not much different than what you're
already doing.
Utkarsh
On Tue, Dec 15, 2015 at 4:54 PM, Viktor Sip
I believe you're looking for:
data =inputs[0]
and not "input(0, 1)".
I'd also recommend reading the Chapter 13 from the ParaView Guide
(http://www.paraview.org/paraview-guide/). It covers this in detail.
Utkarsh
On Tue, Dec 15, 2015 at 9:39 AM, no name wrote:
>
Folks,
ParaView 5.0.0-RC2 is now available for download[1]. Checkout the release
notes on the Kitware blog [2].
As always, we look forward to your feedback [3].
Also stay tuned to the Kitware Blog [4] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
That's weird. Try running ParaView with "-dr" command line argument,
any difference?
Utkarsh
On Mon, Dec 14, 2015 at 2:02 PM, Fernando G. del Cueto wrote:
> Hi all,
>
> I'm having the hardest time finding a way of displaying labels in axes in
> Paraview 4.4.
>
> I'm attaching
> By the way, is there a way of getting the command line options? I tried
> --help, -h and didn't get anything.
-h should do the trick, but on Windows getting output on the terminal
is always weird -- someone more familiar than me with Windows can
elaborate.
So to be clear, if you run paraview
reen
> (both with 32bit and 64bit versions). That's why I defaulted back to 4.4
> :-/
>
> Fernando
>
>
> On Mon, Dec 14, 2015 at 1:52 PM, Utkarsh Ayachit
> <utkarsh.ayac...@kitware.com> wrote:
>>
>> Mind downloading the 5.0.0-RC1 and see if the labels show
> ./configure --enable-64-bit --enable-texture-float --enable-osmesa
> --disable-egl --disable-xorg --disable-xvmc --disable-opencl --disable-glx
> --disable-dri --disable-va --disable-shared-glapi --enable-gallium-llvm=no
> --with-gnu-ld --with-osmesa-bits=8 --disable-vdpau
>
> 2) It seems that the EPS, PDF, PS, and SVG are missing from Export Scene.
That is one of the regressions with the new rendering engine. Vector
graphics exporting cannot be supported in its current form. We have
plans to add a new implementation. In the meantime, use the 4.4
binaries. I am going
> However, I would remove them from the list if they will not be supported.
Good point. Aashish, any reason why they should not be removed? Are
they going to be added back eventually? Let me know and I can have it
fixed accordingly.
Utkarsh
___
Powered
Sergi,
The texture-based volume mapper is no longer supported in ParaView
after changes to the rendering engine. Maybe Aashish can elaborate on
the reasons why.
Utkarsh
On Mon, Nov 23, 2015 at 8:19 AM, Sergi Mateo Bellido
wrote:
> Hi,
>
> I tried to use the
Can you share the dataset to reproduce the bug? Thanks
Utkarsh
On Mon, Nov 23, 2015 at 10:17 AM, Sergi Mateo Bellido
wrote:
> Hi,
>
> I think that I found a bug in the smart volume rendering mode in Paraview
> 4.4.0 and 4.3.1 (I have not tried with older
Is this what you're looking for: http://www.kitware.com/blog/home/post/725
Utkarsh
On Fri, Nov 20, 2015 at 2:51 PM, Tim Gallagher wrote:
> Hi,
>
> I had an idea I would like to explore but I'm not sure the right way to do
> it. I have a 3D vtkMultiblockDataset that is
> I did notice PV is forcing the actor to be modified every time the LOD
> changes (which is a lot). Modifying the actor causes the VBO/IBOs to rebuild
> so it would be better not to do that unless you really need to and in this
> case I'm not sure why it is being done. Specifically I think it is
840 5522 office
> www.fnal.gov
> l...@fnal.gov
>
> Connect with us!
> Newsletter | Facebook | Twitter
>
>> On Tue, Nov 17, 2015 at 4:44 PM, Utkarsh Ayachit
>> <utkarsh.ayac...@kitware.com> wrote:
>> Ken, what Adam has is a multiblock dataset with fiel
Ken, what Adam has is a multiblock dataset with field data array named
"Color" (with certain blocks missing this array). Now when you color by
this array and then uncheck "Map Scalars", I get the attached images. I'd
contend that 5.0 with OpenGL2 rendering is correct. In 4.4 it would just
bleed
David,
I believe you're missing a pq3DWIdget::select() call after the showWigdte().
On Mon, Nov 9, 2015 at 10:15 AM, David Thompson
wrote:
> Hi all,
>
> I need to add some 3D widgets to a custom ParaView application. I've
> succeeded in creating a
I couldn't reproduce the issue on linux. Can you share the two CSV
files you're getting?
Utkarsh
On Tue, Nov 3, 2015 at 1:51 PM, David Ortley wrote:
> All,
>
> I've found a problem in Paraview that seems to be in every version from 4.2
> to current (4.4) which involves the
at works great and allows us to add a Goodyear-specific file to our
> readers here. That ReaderFactory is a very nice feature! This will not only
> be a help to our analysts, it will also tend to make more Paraview converts
> here!
>
> Dennis
>
> -Original Message
as no attribute
> 'CellData'
>
> Dennis
>
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: Thursday, October 22, 2015 5:15 PM
> To: Dennis Conklin <dennis_conk...@goodyear.com>
> Cc: Paraview (paraview@paraview.org) <paraview@p
Dennis,
> In my routine if I:
> 1. Do not declare any output (just accept the predefined output, which is
> set to vtkUnstructuredGrd). Then your print statements work but my program
> kills Paraview with a segmentation fault
I always change the output type using the Output Type property on
> 1. I really want this as a reader, that everyone can use.Is there some
> way to have the user enter a filename which is more elegant than having them
> edit the script? For instance, can the server-side xml plugin stuff be
> edited slightly to work with a Programmable source, so I
Dennis,
> Would it be more efficient make this a Programmable Filter instead (with no
> input?) so that I can use the CellData.append?
You should be able to do the following just fine in a Programmable Source too:
output.CellData.append()
Utkarsh
Ruggiero,
Try changing the tag to .
Utkarsh
On Thu, Oct 15, 2015 at 8:09 PM, Ruggiero Guida
wrote:
> Hi,
>
> I am trying to import the following colormap into Paraview 4.4 (binary
> version).
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> I keep receiving the
You can also use the "Python Calculator" with expression
"volume(inputs[0])" and the "Array Association" set to "Cell Data".
Utkarsh
On Fri, Oct 16, 2015 at 10:00 AM, Cory Quammen wrote:
> Hi Alan,
>
> This script for the Programmable Filter should compute cell volumes
Do you intend to write the data out as CSV? You can simply use the
CSVWriter as follows:
histogram1 =
SaveData('/tmp/sample.csv', proxy=histogram1)
Utkarsh
On Fri, Oct 16, 2015 at 11:23 AM, mohammadreza yaghoobi
wrote:
> Dear all,
>
> I'm trying
Dennis,
Do you have a sample dataset that you can share?
Utkarsh
On Thu, Oct 15, 2015 at 4:04 PM, Dennis Conklin
wrote:
> All,
>
>
>
> I have a Exodus multi-block dataset with some blocks that are truss elements
> (unstructured grid).Each truss represents a
Here's a fix that ensure that trace will capture "Ignore Time"
changes: https://gitlab.kitware.com/paraview/paraview/merge_requests/426
Utkarsh
On Wed, Oct 14, 2015 at 10:59 AM, Utkarsh Ayachit
<utkarsh.ayac...@kitware.com> wrote:
> Here's how:
>
> source = GetActiveSou
?
>
> Thanks,
> Eric
>
>> On Oct 7, 2015, at 12:07 PM, Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
>> wrote:
>>
>> One simpler option worth trying is to make ParaView totally ignore
>> timesteps from one of the readers. Simply right click on the
Ram,
Looks like you're playing back a testing xml. FYI, the testing XML is
not the intended to be used across multiple versions of ParaView since
they directly record UI clicks and events and they are likely to break
as the UI updates. You can try editing the XML to replace the failing
widget
What version of ParaView are you using? I couldn't reproduce the issue
with 4.4. Also, I had to remove the `config.SaveCameras` line in my
testing.
On Mon, Oct 12, 2015 at 9:47 AM, Laurent Spitaels wrote:
> Good morning,
>
> I wrote a macro which is able to start a trace and
One simpler option worth trying is to make ParaView totally ignore
timesteps from one of the readers. Simply right click on the reader in
the Pipeline Browser and check the "Ignore Time" checkbox. Now,
depending on the reader, the reader with "ignored time" will either
give the "closest" timestep
Have you tried using the "Extract Block" filter? You can use that to
extract out the block of interest.
Utkarsh
On Wed, Sep 30, 2015 at 11:36 AM, Dorier, Matthieu wrote:
> Hi,
>
> I have a parallel, Catalyst-enabled simulation exposing its data using a
> vtkMultiBlockDataSet.
>
501 - 600 of 3111 matches
Mail list logo