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
Pyt
g properly and I am getting the data as
> expected.
>
>
> For future reference, should I always just pass the time in? Or are the
> possibly other, unintended side effects from that as well to watch out for?
>
>
> Thanks again,
>
>
> Tim
>
>
>
urns it off/disables it when the pipeline is built and
> there is no surface at that contour level?
>
>
> Thanks,
>
>
> Tim
>
>
> --
> *From:* Andy Bauer
> *Sent:* Monday, February 13, 2017 10:56 AM
> *To:* Gallagher, Timothy P
>
Oops, datadescription.GetTime() instead of datadescription.GetCurrentTime().
On Mon, Feb 13, 2017 at 10:56 AM, Andy Bauer wrote:
> Hi Tim,
>
> Try adding in the current time to the UpdatePipeline() calls, e.g.
> *.UpdatePipeline(datadescription.GetCurrentTime())
>
> It&#x
Hi Tim,
Try adding in the current time to the UpdatePipeline() calls, e.g.
*.UpdatePipeline(datadescription.GetCurrentTime())
It's tough to tell with RequestDataDescription() missing but I assume that
DoCoProcessing() is getting called when you want, correct?
Let me know if that doesn't solve th
Hi Dan,
You an uncheck the All Scalars option in the Threshold filter and that may
give you want you want.
Other options include using the Spreadsheet view and sorting by the column
of your interested array (selection in the Spreadsheet view is linked with
the 3D view). You can also use the Find
think was
> possible). I know there's several things that could probably be done better
> in it, but it works for me at the moment.
>
>
> Thanks again!
>
>
> Tim
>
>
> --
> *From:* Andy Bauer
> *Sent:* Tuesday, February 7, 201
tiple surfaces and
> would like to only save the data files when the surface appears.
>
>
> Is there a way to turn on/off the writers through the coprocessor.Pipeline
> object, or maybe through arguments to WriteData?
>
>
> As always, thanks for your help.
>
>
> T
stributes the data. But, looking at the block
> VTK files that are written out, they all contain the same value of Area so
> I think a global reduction is done in the filter and all blocks have the
> total values. I could be wrong though.
>
>
> Thanks again,
>
>
> Tim
>
&
Hi Tim,
The short answer is that you need to do
coprocessor.Pipeline.flameArea.UpdatePipeline() before checking for the
area. You also may need to use MPI to do the global sum or broadcast of the
value since I think that value will either just have local values or maybe
just the proper global val
I should only need one that demonstrates the problem.
On Fri, Feb 3, 2017 at 5:54 AM, sinan shabib wrote:
> Hi Andy,
>
> Could you please tell me, which data set you need ?
> Because it´s big data.
> I´m doing (Ensight 6) format.
>
> Greetings.
>
>
> Andy Bauer sc
>
> Is it a bug or VTK has been corrupted or something else ?
>
> Thanks in advance.
>
>
>
>
>
> Andy Bauer schrieb am 16:00 Donnerstag,
> 2.Februar 2017:
>
>
> Maybe I didn't understand what you were trying to do. Can you be a bit
> more specific?
ith data-visualization (data are read but not
> visualized).
>
>
>
> Andy Bauer schrieb am 19:02 Dienstag, 31.Januar
> 2017:
>
>
> Hi,
>
> Please keep the discussion on the mailing list so that anyone can
> participate (also, stuff gets lost in my Inbox too).
.
>
>
>
> Is there any previous thread where I can find out more about the
> simulation + catalyst linking to a parallel server?
>
>
>
> Best regards,
>
> Simon
>
>
>
> *From:* Andy Bauer [mailto:andy.ba...@kitware.com]
> *Sent:* Donnerstag, 26.
Can you share your data set? It will be difficult to diagnose without that
information.
Also, I'd strongly suggest upgrading to ParaView 5.2 instead of just the
release candidate.
On Tue, Jan 31, 2017 at 7:52 AM, sinan shabib via ParaView <
paraview@paraview.org> wrote:
> Hi all,
>
> I´m using
Hi,
The gradient of unstructured data sets will work on cell data. Have you
tried that?
Note though that ParaView/VTK only allows fields to be associated with
either points or cells, not interfaces between cells (e.g. faces in 3D and
edges in 2D).
On Thu, Jan 26, 2017 at 8:09 AM, Christoph Grüni
Hi,
Currently the Live functionality only works when ParaView is built with
Python bindings. My suggestion would be to build ParaView yourself. That
should be much easier than trying to put in a C++ pipeline that can deal
with the Live functionality properly.
As for building ParaView, you may wan
nodes (and thus cannot have cells either), then it should probably not
> participate in writing the Exodus dataset. You could create an MPI
> subcontroller without the rank 0 process and have the writer use that.
>
> > At this point I'm thinking it's better to modify the reade
plied that python calculator to my original "unstructured
>> grid" data set everything worked fine (so it is not about missing python
>> support!), but if I did the procedure as above, applying the "python
>> calculator" on the extracted data, I always got a messa
;...
>
> Regards,
> Cornelis
>
> PS: Why do I never see my own posts to the paraview mailing list? Is this
> a bug or a feature or something I am doing wrong?
>
> 2017-01-17 0:57 GMT+01:00 Andy Bauer :
>
>> This can be done through either the calculator or python
ecified. Maybe there just isn't a good
solution here based on the format requirements. I'll test out modifying the
reader though and see what happens...
>
> David
>
> >
> > On Fri, Jan 13, 2017 at 2:59 PM, Andy Bauer
> wrote:
> > Hi Ken,
> >
>
13, 2017 at 2:59 PM, Andy Bauer wrote:
> Hi Ken,
>
> Thanks for the input.
>
> There is an explicit check in the writer to see if there are any points
> before writing out point data. I took that check out and am hitting a
> NetCDF error that the "num_nodes" dimensio
dus point and cell arrays if no
> grid points or cells exist. The writer is probably making a shortcut and
> skipping that if there is no actual data.
>
>
>
> -Ken
>
>
>
> *From:* ParaView [mailto:paraview-boun...@paraview.org] *On Behalf Of *Andy
> Bauer
> *Sent:*
Hi,
I'm trying out the ExodusII writer in parallel and had some questions about
how it should work in general when there isn't any data on process 0.
Currently what happens in ParaView is that a file for each process is
written out but the file corresponding to process 0 doesn't have any grid
info
HI Zhang,
That has been done with PyFR with Catalyst doing everything on the GPU. I
see some stuff at https://github.com/vincentlab/PyFR-Catalyst that may be a
good starting point for you.
I don't quite know if Catalyst is ready for general use at this point on
GPUs (it may be but I haven't done
Hi Joe,
I haven't seen this issue or heard anyone else with something like this.
Are you running pvbatch in serial? If you share a python script which
demonstrates the issue it may be an easy issue to track down.
There are some slight differences between pvpython and pvbatch. My guess
would be th
hat the bug was present also on Kitware
> binaries. I could repeat it on my windows pc and on my fellow workers linus
> systems.
>
> Best regards,
> Jyrki
>
> ------
>
> *From: *"Scott, W Alan"
> *To: *"Andy Bauer" , "Jyrki Ho
Hi Jyrki,
Thanks for the report. I can replicate this issue that the second selection
takes significantly longer with PV 5.2 on my machine. Would you mind
adding this in as an issue? You can do that at
https://gitlab.kitware.com/paraview/paraview/issues.
Thanks,
Andy
On Thu, Jan 5, 2017 at 9:23
bit weird. If i am doing something
> wrong, please let me know.
>
> Also, i did not modify the default config settings of the GUI and if you
> want me to check any specific option, please let me know.
>
> Thank for your help,
> Regards,
>
> --ufuk
>
> On 02/01/2017
er of *Output to
> Cinema *or *Output rendering components i.e. views, *I could not get the
> live visualization, and of course no picture is generated. But what's the
> function of the *Live Visualization *option?
>
> All of the above are situations in the PV 4.4.0 in the client-ser
Hi Ufuk,
I'm not sure what is causing the difference. I'm guessing not all of the
information for the view is saved in the state. Any chance that you're
using different versions of ParaView for the GUI and Catalyst generated
images? I see that the Python script is specifying that it was generated
Hi,
The Catalyst examples have been moved to the ParaView source repo. I'd
recommend using the newest version of ParaView as well as Catalyst since
there have been a lot of improvements since PV 4.4.
For the CxxFullExample, if you've built it with Catalyst enabled you can
run it as you've done a
If you want the seeds to move my suggestion would be to use a programmable
source that generates those seeds and then use the Stream Tracer With
Custom Source filter. This does require knowing the how the seeds change
with time a priori. If you want the seeds to advect with the flow you could
try t
There are two parts to this issue. The first is that that
vtkMPICommunicator for PV 4.3.1 won't communicate data that is over 2^31
bytes of data. This is fixed in PV 5.2. The other issue is due to MPI
having a limit of 2^31 objects to be communicated in a single shot. This is
MPI's API in that the
Any chance that you have a different grid that you're adding the field to?
What happens if you print out the number of point data arrays before you
add the grid?
On Mon, Dec 12, 2016 at 7:22 AM, Ufuk Utku Turuncoglu (BE) <
u.utku.turunco...@be.itu.edu.tr> wrote:
> Hi Andy,
>
> I tested code with
Are the fields uniquely named? That would be my first guess. Other than
that, what are the names of the fields? Some names are specially handled in
which case they may be hidden in the ParaView GUI.
On Fri, Dec 9, 2016 at 8:23 AM, Ufuk Utku Turuncoglu (BE) <
u.utku.turunco...@be.itu.edu.tr> wrote
t for a
> different PV version. A simple $ export PV_PLUGIN_PATH="" did the trick.
> Thanks again!
>
> Cheers,
> Martin
>
>
> Am 02.12.2016 um 14:59 schrieb Andy Bauer:
>
> This sounds like maybe something with your PV config. Try running with the
> --dr flag
This sounds like maybe something with your PV config. Try running with the
--dr flag to disable reading in your config file.
Cheers,
Andy
On Dec 2, 2016 5:38 AM, "Martin Reitzle" <
martin.reit...@itlr.uni-stuttgart.de> wrote:
> Hello everyone,
>
> I am running into a strange issue and hope someo
You can use the Process Id Scalars to examine the data distribution and
maybe see if something funky is going on there. In parallel there's also a
helper array which you can pseudo-color by to see the partitioning but I
don't remember the name of that array.
You could also try doing something like
You may need to set things like your PYTHONPATH and LD_LIBRARY_PATH in the
programmable source itself instead of in the environment you're running
ParaView from. For example:
import sys
sys.path.append("/home/me/mypy")
Remember that the programmable source runs the script on the server.
On Fri,
Hi Yvan,
I just tried doing something similar with my build of the latest git
revision of PV and didn't have any problems with exporting.
Could you try running paraview with the "-dr" flag to disable your
registry? Maybe something in there is causing problems.
If that doesn't fix the issue, coul
ry to upgrade the Nvidia
> library but i just want to be sure.
>
> Thanks for your help,
> Regards,
>
> --ufuk
>
>
> On 02/11/16 17:49, Andy Bauer wrote:
>
> Hi Ufuk,
>
> I haven't heard of any issues like this. Do you get similar behavior on
> the
Hi,
To add to Cory's feedback -- installers and source code are available for
the 5.2 release candidate if you'd like to try it out and see if it's
fixed. If it's not fixed and you let us know ASAP, we may be able to get it
fixed in time for the 5.2 release. You can get the release candidate and
p
Hi Ufuk,
I haven't heard of any issues like this. Do you get similar behavior on the
machine when running ParaView with a separate, connected pvserver?
If you have an NVIDIA card you may be able to use their EGL libs for
offscreen rendering (i.e. no x-windows needed). See the blog post at
https:/
it a shot. I'm doing this on some SGI and Cray machines, I don't know
> if that has special ways to do this like you mentioned exists at NERSC.
>
>
> Thanks,
>
>
> Tim
>
>
> --
> *From:* Andy Bauer
> *Sent:* Tuesday, Octo
Hi Tim,
This may be better to do as an in transit set up. This way the processes
would be independent. Through Catalyst I'd worry about all of the processes
waiting on the global rank 0 doing work before all of the other Catalyst
ranks return control to the simulation. Depending on the system you'
The following should work:
- Gradient of Unstructured Data Set
- Extract Surface
- Generate Surface Normals
- Calculator filter to compute the wall shear stress from the gradient
and the surface normals.
On Fri, Oct 21, 2016 at 11:55 PM, Fande Kong wrote:
> Still have hard time
I'm not sure I understand your use case entirely but I think what you want
is to use the Threshold filter. You may want to use it on the 3D object or
maybe on just the streamlines.
On Fri, Oct 14, 2016 at 2:15 AM, Ge Heim via ParaView wrote:
> Hello everybody,
>
> I'm relatively new to ParaView
Hi Ben,
I wasn't aware of the transparent background -- thanks!
This leads to one question though: any idea why this option isn't available
under the Save Screenshot Options when saving a screenshot? Changing the
color palette can be done in the GUI under Edit->Settings->Color Palette
which gets
same way: If I highlight the
> calculator and do Save Data, ParaView saves everything, not just the
> calculator result. What can I do to just save the calculator result?
>
>
>
> Thank you,
>
>
>
> Matthias
>
>
>
>
>
> *Von:* Andy Bauer [mailto:andy.ba..
Do you have the Slice filter highlighted in the GUI when you save the data
set? That's the proper way to just save out the results from that filter
and not the others. Also, you can use the Pass Arrays filter to selectively
choose which arrays you want to pass through the pipeline.
On Mon, Sep 26,
Hi Matthieu,
That makes complete sense. I've thought about putting in a C++ Catalyst
pipeline in the main source code that could be used to just write out the
data at some prescribed file name and frequency but haven't forced myself
to do it. It gets slightly more complicated when dealing with mul
Hi Matthieu,
You can indeed use Catalyst without Python. There are two examples in the
Examples/Catalyst subdirectory of the source tree to do that. They are
CxxVTKPipelineExample and CxxPVSMPipelineExample. I wouldn't recommend this
method as the Python route is much simpler. Several people have
d one of my problems. Thanks a lot. Here is another one.
>
> Is it possible to convert to ASCI or other text file and record the Run
> Selection Query results or plotted curves?
>
> Your help will be appreciated.
>
> Boris
>
>
>
> *From:* Boris Jagrine
> *Sent:*
Hi Rick,
This CMake script is for the superbuild, correct?
That's definitely the way to go for OS Mesa as it builds the proper version
of OS Mesa for you. The superbuild stuff is at
https://gitlab.kitware.com/paraview/paraview-superbuild.
Chris, if you have an NVIDIA card with a fairly new drive
DOPENGL_glu_LIBRARY:PATH=/home/neal/software/Mesa/build/lib64/libGLU.so
> \
>
> -DVTK_OPENGL_HAS_OSMESA:BOOL=ON \
>
> -DOSMESA_INCLUDE_DIR:PATH=/home/neal/software/Mesa/build/include \
>
> -DOSMESA_LIBRARY:PATH=/home/neal/software/Mesa/build/lib64/libOSMesa.so
> /home/ne
Hi Chris,
It sounds like you didn't properly build ParaView with offscreen rendering.
Can you share your CMakeCache.txt from your build? I'm guessing VTK_USE_X,
VTK_USE_OFFSCREEN or some other thing didn't get set properly.
Andy
On Mon, Sep 12, 2016 at 1:36 PM, Christopher Neal
wrote:
> Hi al
l
> vtkPVCatalyst-pv5.1.dll
> vtkCommon-pv5.1.dll
> Do I have to change some options in the cmake.sh script to include
> those libs?
> 2.) Do I have to install Paraview too, or is the Catalyst version I just
> installed sufficient to run the example?
Hi Boris,
ParaView actually forces the same color scale for all pseudo-colored
objects in the render view, as long as the fields selected have the same
name (and possibly type). So in short answer, yes what you want is possible
and should be done automatically.
In the upper right corner of the vi
rapTclInit-pv5.1
> vtkGUISupportQtCxxTests vtkWrapTcl-pv5.1
> vtkH5detect
>
> When I try to find CxxFullExample in the build/ directory:
>
> find -name CxxFullExample
>
> Nothing is found. The sources for the examples are in the source as you
> mentioned,
I don't know if this functionality is supported through the Python API. If
not I don't think it would be too much effort to add it in.
On Wed, Aug 31, 2016 at 9:43 AM, Luigi Calori wrote:
> We would like to automate the opening of catalyst connection inside
> Paraview standalone by providing a p
Hi,
The examples have been moved into the ParaView source tree at
/Examples/Catalyst. This makes it easier to test the examples and
keep them in sync with the PV source. You can still compile them separately
and individually if you want to.
On my Linux machine, when I build ParaView master (a bit
Look at the discussion at
http://markmail.org/search/?q=paraview+luigi+calori#query:paraview%20luigi%20calori+page:1+mid:i5dxviq6va7simyi+state:results
for the current state of the art for not exporting all variables from the
adaptor.
Catalyst can output data extracts. It's in the Writers menu onc
Hi Jean,
I'm guessing you missed the vtkCPInputDataDescription::SetWholeExtent()
method in your adaptor. Catalyst runs like "pvbatch -sym", i.e. each
process runs the script and we avoid MPI reduce operations to process 0.
This results in process 0 (the process that writes out the meta xml file)
n
Can you share your Python script? Also, I would suggest using the
gridwriter.py script to see what Catalyst is getting as your data set
input. It may be different than what your normal simulation output is.
Best,
Andy
On Mon, Aug 22, 2016 at 3:09 PM, Luigi Calori wrote:
> We are trying to add s
>
> Any hints will be really appreciated.
>
> Best regards
> Luigi
>
>
>
>
> On 18/08/2016 03:23, Andy Bauer wrote:
>
> Hi,
>
> This is possible but at this point requires custom coding the Python
> script to specify which fields are needed. T
Hi,
This is possible but at this point requires custom coding the Python script
to specify which fields are needed. This should be done during the
RequestDataDescription() call. You can use vtkCPInputDataDescription's
IsFieldNeeded() and IsFieldPointData() methods to specify what's needed in
the P
Hi,
This is the classic 80% / 20% software problem where 80% of the users only
use 20% of the capabilities but each 20% is significantly different.
As for creating your own Catalyst edition, that is definitely possible.
There's some information at
http://www.paraview.org/Wiki/Generating_Catalyst_
Hi Jim,
In ParaView there is only field values associated with points and cells. If
by face data you mean data associated with 2D cells then Cory's email is
the correct one. If by face values you mean field data associated with a
face of a 3D cell, ParaView does not currently support that. If it's
Hi Chris,
Are you trying to build from a Catalyst edition or directly from the full
ParaView source? I want to make sure that we're going in the proper
direction when trying to fix this problem.
Thanks,
Andy
On Fri, Aug 5, 2016 at 1:15 PM, Utkarsh Ayachit wrote:
> Ben,
>
> Can you take a look
Can you share your Python script? Another thought is that your Python
script was added to each process instead of the subset of processes that
are supposed to do the calculation on it. For example, the Python script
that is supposed to generate the image should only be added through a
vtkCPPythonSc
I'm guessing that the edition you're working with doesn't have that filter.
Is vtkPVArrayCalculator.h in the source directory of your Catalyst edition?
Note that for the Catalyst examples you can build them individually by
pointing CMake to each individual directory.
On Wed, Jul 27, 2016 at 6:04
at the Catalyst editions can be compiled separately
> from Paraview i.e. I do not need to have a version of Paraview compiled in
> order to compile a Catalyst edition. Is this correct?
>
> Thank you,
>
> Chris
>
>
>
> *From: *Andy Bauer
> *Date: *Friday, July 22,
Hi Chris,
You can get the Catalyst editions source code at
http://www.paraview.org/download/ by just selecting Catalyst editions for
Type of Download. If you're just getting started though I would recommend
doing a build of ParaView without the GUI. Yes this will require learning a
bit of CMake (s
o the fact that I use quadratic triangles, the
> filter GradientOfUnstructuredDataSet should works after the use of the
> filter PointDataToCellData ? But it does not still work.
>
> Best
>
> Stéph
>
>
> Le 14/07/2016 20:17, Andy Bauer a écrit :
>
> Hi,
>
> It looks like gradients
Hi,
It looks like gradients aren't getting computed properly for quadratic
triangles. A quick work around is to use the tesselate filter to subdivide
the quadratic triangles while converting them to linear triangles. The
gradient of unstructured data filter should work after that. I'll add in a
b
tline of the
> appropriate approach to get me started?
>
> Thanks a lot.
>
> On Wed, Jul 13, 2016 at 9:18 AM Andy Bauer wrote:
>
>> Hi Ethan,
>>
>> The issue here is that unstructured grids (which is what you have here)
>> doesn't support non-conf
ould help me figure out how to make nice streamlines with this kind of
> data.
>
> Cheers,
>
> Ethan Alan
>
> On Tue, Jul 12, 2016 at 4:08 PM Andy Bauer wrote:
>
>> Hi Ethan,
>>
>> I'm not sure updating to a newer version of ParaView will help here but
7;m using a newish version of paraview (4.4.0) but I'll try on 5.0 soon.
> Also, I'm not sure that this is important, but he elements are VTK Voxels,
> not hexahedra.
>
> Thanks for your help,
>
> On Tue, Jul 12, 2016 at 2:30 PM Andy Bauer wrote:
>
>> Hi Ethan,
>
Hi Ethan,
I've been able to use streamlines with a general multiblock data set that
uses blanking. This may be slightly different than your data set but I
don't see why it shouldn't work for you.
Are the streamlines terminating near the interfaces between different
leaves of the octree grid? If y
has figures that might show a bit more of what I am trying to achieve.
>
>
> If you need any additional information please let me know!
>
> Thanks in advance for any kind of hint or help!!
>
>
> Best wishes,
>
> Asaad
> --
> *Von:* A
Can you share your dataset and specific information on what you're trying
to do in ParaView?
Cheers,
Andy
On Mon, Jul 11, 2016 at 3:53 AM, Sellmann, Kai Asaad <
asaad.sellm...@rwth-aachen.de> wrote:
> Dear Paraview Community,
> I have succeded to import my FEM Data (Nodal Coordinates, Element
Hi Alan,
How about using the Extract Location filter using the interpolate at point
for the mode and then do a Plot Selection Over Time after selecting that
point?
Thanks for asking the question -- I didn't know about the Extract Location
filter until I tried answering this! I was originally thin
Hi,
Glad to hear that this is working for you and thanks for sharing how you
did it! This is definitely a corner case that few Catalyst users/developers
will ever care about so I'm glad that the Catalyst API is flexible enough
to handle this.
Best,
Andy
On Sun, Jun 19, 2016 at 4:07 AM, wrote:
Hi Ufuk,
I can think of two potential fixes:
- Use the vtkCPProcessor:: Initialize(vtkMPICommunicatorOpaqueComm&
comm) method to initialize each process with the proper MPI communicator.
Note that vtkMPICommunicatorOpaqueComm is defined in
vtkMPICommunicator.cxx. A similar example to
Hi Tim,
If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good at
finding VTK objects that aren't deleted properly. You should be able to run
this with a small amount of calls to Catalyst as well. If you try this and
want help understanding the output (if an object like a vtkUnstruct
mechanics code to our fluid
> dynamics
> > solver for example. It sounds like that is similar to what is being done
> > here.
> >
> >
> > How that would interact with coprocessing is beyond my knowledge though.
> > It does sound like an interesting problem a
Hi,
I'm a bit confused. MPI_COMM_WORLD is the global communicator and as far as
I'm aware, can't be modified which means there can't be two different
communicators.
Catalyst can be set to use a specific MPI communicator and that's been done
by at least one code (Code_Saturne). I think they have a
emplate does exactly -- I believe that was something you
> had added when you took a look at our code awhile back. But it doesn't seem
> to matter for what we're doing now.
>
>
> It feels good to close the ticket in our tracker about getting
> coprocessing on Crays -- it
) to just let
> it add attributes without manually calling add_attribute() each time?
>
>
> Tim
>
>
> --
> *From:* ParaView on behalf of Gallagher,
> Timothy P
> *Sent:* Monday, May 9, 2016 5:13 PM
> *To:* Andy Bauer
>
> *Cc
STALLPATH}/osmesa/lib/libOSMesa.so" \
> ./ParaViewSuperbuild
>
>
> and all of the other PARAVIEW* options seemed to pass through properly
> when the superbuild made paraview. Any ideas why that option didn't pass
> through?
>
>
> Thanks -- I knew it had to b
Hi Tim,
Is the PV directory you're pointing to a build directory or an install
directory? If it's an install directory you'll need to enable
PARAVIEW_INSTALL_DEVELOPMENT_FILES. Other than that, my suggestion would be
to try linking one of the Catalyst examples from
https://github.com/Kitware/ParaV
Hi,
Are you generating the Catalyst script with PV built with the OpenGL2
backend and then linking with a version of Catalyst built with the OpenGL1
backend? I'd guess that this is the problem.
To isolate the issue further, you can do a Python trace in the GUI to see
if you get the same issue whe
Hi,
That option is only shown in the advanced settings of the Properties dialog
box. To get those settings, click on the Gear button right under the
Question mark button. Please let me know if this doesn't solve your issue.
Best,
Andy
On Wed, Apr 27, 2016 at 3:33 AM, Seong Mo Yeon
wrote:
> In
Hi,
Did you use the same version of ParaView to generate the script and for
your Catalyst build? If not, you'll want to do that. Also, you may want to
try generating the script in the PV GUI with a version of ParaView that's
using the OpenGL and NOT OpenGL2 rendering backend.
If none of that fixe
Hi Sean,
I don't know the answer since I don't deal with that many different
unstructured grid file formats when reading data into PV. As far as I know,
we don't mark too carefully which unstructured grid readers can partition
data in parallel. My best advice for this is just to try it reading
dif
3d field (same as step 3). The
> co-processing code hands with white screen and does not produce the output.
>
> So, it seems that the combination of Contour and vector visualization
> affects the co-processing. Anyway, do you have similar experience in
> co-processing?
>
> Reg
Hi Ufuk,
I would suggest testing out some of the Catalyst examples which are in the
source code under the Examples/Catalyst subdirectory. I would also suggest
creating Catalyst scripts from data sets generated through Catalyst output
instead of the NetCDF files. There are two example scripts for t
e this:
>
>
>
> coprocess.DoLiveVisualization(datadescription, “localhost”, 2)
>
>
>
> Do I have to call DoLiveVisualization differently when running across
> multiple nodes? Do I need to set the host differently maybe? Or is the
> problem more likely to be at m
er to the sim. If there's firewalls then it may be a bit more
complex connection. I don't know to what level/size data this has been
pushed to.
>
>
> Thank you for the information regarding AMR grids – it sounds like this
> approach will work for my application.
>
>
&g
101 - 200 of 774 matches
Mail list logo
