Glad to ear that you managed to get something going. If you feel like
sharing your code, we might be able to provide some integration into
ParaView and/or ParaViewWeb proper.
Seb
On Sat, May 21, 2016 at 11:53 AM, Sven Kramer
wrote:
> Thank you, Seb,
> it seems like I am
btw, we just had similar problem that was entirely explained by vtk
writer attempting to gather a bunch of arrays to the root node. Utkarsh
found a way to disable that behavior. I wonder if you are hitting the same.
On 5/20/2016 4:36 PM, Gallagher, Timothy P wrote:
Well... not going so well.
If you can control which communicator Paraview uses, you might want to look at
using MPI_INTERCOMM_MERGE, which will take the union of the two disjoint sets
described by an intercommunicator. So with that, you would create a new
communicator that has all of your processors as members.
Paraview
Hello
Python calculator is the way to go here
inputs[0].PointData['flux1'] - inputs[1].PointData['flux2']
Beware of the order of the input, they will be ordered randomly by
paraview, but you can reorder them wia the python shell, or modify your
python-calculator script.
Mathieu Westphal
On
Thanks for the information. Currently, i am working on two component case
and the initial results show that grid and data information belong to each
model component must be accessible by all the MPI processes (defined in
global MPI_COMM_WORLD) in adaptor side. This makes the implementation very
ParaView newbie here ,and sorry to interrupt you for some problems i met.
I have been using two vtk input files which named t1 and t2 for example,
both input files contained only one dataset for CellData may called flux1
and flux2.
Exactly the structure and the data t1 and t2 got were same and