Re: [Paraview] PYTHONPATH environmental variable

2015-06-18 Thread Timo Oster
Hi Felix,

I just happened upon the same problem yesterday. The solution was to add
the directory with the vkt shared objects into the PYTHONPATH. Those are
in .../site-packages/vtk. The .../site-packages/paraview/vtk is just a
mirror that includes the libraries from the top-level vtk directory.

Hope this helps.

Regards,

Timo
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] Connecting to Catalyst-Enabled Simulation Running on Remote Cluster

2015-05-20 Thread Timo Oster
libdyld.dylib 0x7fff8cbe75c9 start + 1
> [epsilon:07510] *** End of error message ***
> --
> mpirun noticed that process rank 0 with PID 7510 on node epsilon exited
> on signal 11 (Segmentation fault: 11).
> ------
> 
> So, i am unable to run Catalyst tests for now. They produces output
> *.vtm files (using writers in the pipeline) if i disable live
> visualization. Please let me know, if you have any suggestion.
> 
> Regards,
> 
> --ufuk
> 
> On 20/05/15 10:31, Timo Oster wrote:
>> Hi,
>>
>> I have indeed run into the problem with "Could not receive tag. 1". In
>> my case I had to make sure that the client and server versions were
>> exactly the same. When connecting, the vtkSocketCommunicators on client
>> and server exchange a version hash that must match. This hash is
>> generated while building ParaView. The file that is generated can be
>> found in your build directory under
>> VTK/Parallel/Core/vtkSocketCommunicatorHash.h. Check that your client
>> and server have the same hash value in this file.
>>
>> I am assuming that you have correctly set up an ssh tunnel between
>> client and server to enable the connection (ssh -L 1:localhost:1
>> user@server). The steps I take to run a in-situ case on a single remote
>> workstation are listed in my previous mail.
>>
>> BTW I am using the "trunk" version of ParaView from the git repository,
>> which is close to version 4.3.1, and I'm running Linux on both client
>> and server (different distributions).
>>
>> Regards,
>>
>> Timo
>>
>> On 05/19/2015 06:57 PM, u.utku.turunco...@be.itu.edu.tr wrote:
>>> Hi Timo,
>>>
>>> Have you ever tried to test Catalyst examples in your case.
>>>
>>> https://github.com/Kitware/ParaViewCatalystExampleCode
>>>
>>> I am also trying to run Catalyst examples but i could not. In my case, i
>>> am able to install Paraview (4.3.1) from source under Mac OS 10.10
>>> and the
>>> Catalys examples but when i try to run the examples i am getting error
>>> like,
>>>
>>> ERROR: In
>>> /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
>>>
>>> line 812
>>> vtkSocketCommunicator (0x7f86a52658e0): Could not receive tag. 1
>>>
>>> or
>>>
>>> ERROR: In
>>> /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/Common/System/vtkSocket.cxx,
>>>
>>> line 572
>>> vtkClientSocket (0x7fcefc939fe0): Socket error in call to send.
>>> Broken pipe.
>>>
>>> So, if you don't mind could you share the details of your work
>>> environment
>>> (OS, Paraview version, etc.) and the steps to run the in-situ
>>> example. So,
>>> that could also help me to find the source of the problem.
>>>
>>> Regards,
>>>
>>> --ufuk
>>>
>>>> Hi all,
>>>>
>>>> in an effort to enable live visualization of our simulation code, I
>>>> have
>>>> written a Catalyst adaptor for it. The live visualization is working
>>>> great when the ParaView client runs on the same machine as the
>>>> simulation, even when the simulation runs in parallel using mpi.
>>>>
>>>> Now I want to do live visualization of a simulation running on a remote
>>>> cluster. I am able to get this to work for the simulation running on
>>>> the
>>>> login node of the cluster:
>>>>
>>>> 1. Tunnel an ssh connection of port 1 to the cluster:
>>>>  ssh -L 1:localhost:1 server
>>>> 2. In the shell that opens, start a paraview server (in the background
>>>> with '&')
>>>> 3. Run the simulation with mpirun (simulation runs only on login node)
>>>> 4. Start my local ParaView client and connect to localhost:1 to
>>>> connect to the remote pvserver through the ssh tunnel
>>>> 5. In the client, connect to Catalyst (port 2)
>>>> 6. A provider for the simulation is created and the live visualization
>>>> works
>>>>
>>>> Now I want to do the same for simulations started on the remote cluster
>>>> via the batch job system. In this scenario, the parallel processes of
>>>> the simulation will run on different (randomly chosen) nodes on the
>>>> cluster. How do I go about getting a connec

Re: [Paraview] Connecting to Catalyst-Enabled Simulation Running on Remote Cluster

2015-05-20 Thread Timo Oster
Hi,

I have indeed run into the problem with "Could not receive tag. 1". In
my case I had to make sure that the client and server versions were
exactly the same. When connecting, the vtkSocketCommunicators on client
and server exchange a version hash that must match. This hash is
generated while building ParaView. The file that is generated can be
found in your build directory under
VTK/Parallel/Core/vtkSocketCommunicatorHash.h. Check that your client
and server have the same hash value in this file.

I am assuming that you have correctly set up an ssh tunnel between
client and server to enable the connection (ssh -L 1:localhost:1
user@server). The steps I take to run a in-situ case on a single remote
workstation are listed in my previous mail.

BTW I am using the "trunk" version of ParaView from the git repository,
which is close to version 4.3.1, and I'm running Linux on both client
and server (different distributions).

Regards,

Timo

On 05/19/2015 06:57 PM, u.utku.turunco...@be.itu.edu.tr wrote:
> Hi Timo,
> 
> Have you ever tried to test Catalyst examples in your case.
> 
> https://github.com/Kitware/ParaViewCatalystExampleCode
> 
> I am also trying to run Catalyst examples but i could not. In my case, i
> am able to install Paraview (4.3.1) from source under Mac OS 10.10 and the
> Catalys examples but when i try to run the examples i am getting error
> like,
> 
> ERROR: In
> /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
> line 812
> vtkSocketCommunicator (0x7f86a52658e0): Could not receive tag. 1
> 
> or
> 
> ERROR: In
> /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/Common/System/vtkSocket.cxx,
> line 572
> vtkClientSocket (0x7fcefc939fe0): Socket error in call to send. Broken pipe.
> 
> So, if you don't mind could you share the details of your work environment
> (OS, Paraview version, etc.) and the steps to run the in-situ example. So,
> that could also help me to find the source of the problem.
> 
> Regards,
> 
> --ufuk
> 
>> Hi all,
>>
>> in an effort to enable live visualization of our simulation code, I have
>> written a Catalyst adaptor for it. The live visualization is working
>> great when the ParaView client runs on the same machine as the
>> simulation, even when the simulation runs in parallel using mpi.
>>
>> Now I want to do live visualization of a simulation running on a remote
>> cluster. I am able to get this to work for the simulation running on the
>> login node of the cluster:
>>
>> 1. Tunnel an ssh connection of port 1 to the cluster:
>> ssh -L 1:localhost:1 server
>> 2. In the shell that opens, start a paraview server (in the background
>> with '&')
>> 3. Run the simulation with mpirun (simulation runs only on login node)
>> 4. Start my local ParaView client and connect to localhost:1 to
>> connect to the remote pvserver through the ssh tunnel
>> 5. In the client, connect to Catalyst (port 2)
>> 6. A provider for the simulation is created and the live visualization
>> works
>>
>> Now I want to do the same for simulations started on the remote cluster
>> via the batch job system. In this scenario, the parallel processes of
>> the simulation will run on different (randomly chosen) nodes on the
>> cluster. How do I go about getting a connection from my local client to
>> the Catalyst instances running on those nodes?
>>
>> I imagine I will need to set up ssh tunnels from the nodes to the login
>> node where the pvserver is running. I've tried adding a ssh tunnel line
>> to the job script that is executed when the batch job starts. I've tried
>> forwarding and reverse-forwarding port 2 (ssh -L and ssh -R) to no
>> avail. The best I get is "ERROR: In
>> /.../ParaView_git/VTK/Common/System/vtkSocket.cxx, line 206
>> vtkServerSocket (0x18e0930): Socket error in call to bind. Address
>> already in use."
>>
>> My knowledge in networking and ssh is limited, so any pointers to how I
>> would go about this are greatly appreciated.
>>
>> Regards,
>>
>> Timo
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
> 
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


Re: [Paraview] Connecting to Catalyst-Enabled Simulation Running on Remote Cluster

2015-05-20 Thread Timo Oster
Hi Andy,

I have succeeded in getting it to work by starting a pvserver process on
every node alongside with the simulation instead of just one pvserver on
the login node. I then have a ssh tunnel from the worker nodes to the
login node, and from the login node to my local computer. This appears
to be rather resource-intensive though, and I wonder if there is a more
efficient way to do it. Is such a great number of pvservers really
needed? If somebody has any additional information, that would be very
helpful. Searching the internet for this question hasn't brought up much
helpful information yet.

Regards,

Timo

On 05/19/2015 05:09 PM, Andy Bauer wrote:
> Hi Timo,
> 
> There's a couple of steps that need to be added when connecting to a
> Catalyst-enabled simulation that's been run through a batch job on a
> cluster. This "should" be the same as just running pvserver through a
> batch job and connecting to that. The basics are that there's an
> executable/script that runs on the login node that the batch job
> connects to. Your GUI connects to the login node and has the ports
> forwarded properly through the executable/script to your pvserver. Now
> if your pvserver is running on the login node then it will have to use
> the above connection mechanism to connect to your Catalyst-enabled
> simulation. There may be some emails or something on the wiki that has
> information on the connection executable/script but I haven't tried any
> of that in several years so I'm not sure where it would be. Maybe
> someone else will chime in that's done this more recently than me.
> 
> Good luck and let us know how it goes.
> 
> Andy
> 
> On Mon, May 18, 2015 at 8:48 AM, Timo Oster  <mailto:timo.os...@ovgu.de>> wrote:
> 
> Hi all,
> 
> in an effort to enable live visualization of our simulation code, I have
> written a Catalyst adaptor for it. The live visualization is working
> great when the ParaView client runs on the same machine as the
> simulation, even when the simulation runs in parallel using mpi.
> 
> Now I want to do live visualization of a simulation running on a remote
> cluster. I am able to get this to work for the simulation running on the
> login node of the cluster:
> 
> 1. Tunnel an ssh connection of port 1 to the cluster:
> ssh -L 1:localhost:1 server
> 2. In the shell that opens, start a paraview server (in the background
> with '&')
> 3. Run the simulation with mpirun (simulation runs only on login node)
> 4. Start my local ParaView client and connect to localhost:1 to
> connect to the remote pvserver through the ssh tunnel
> 5. In the client, connect to Catalyst (port 2)
> 6. A provider for the simulation is created and the live
> visualization works
> 
> Now I want to do the same for simulations started on the remote cluster
> via the batch job system. In this scenario, the parallel processes of
> the simulation will run on different (randomly chosen) nodes on the
> cluster. How do I go about getting a connection from my local client to
> the Catalyst instances running on those nodes?
> 
> I imagine I will need to set up ssh tunnels from the nodes to the login
> node where the pvserver is running. I've tried adding a ssh tunnel line
> to the job script that is executed when the batch job starts. I've tried
> forwarding and reverse-forwarding port 2 (ssh -L and ssh -R) to no
> avail. The best I get is "ERROR: In
> /.../ParaView_git/VTK/Common/System/vtkSocket.cxx, line 206
> vtkServerSocket (0x18e0930): Socket error in call to bind. Address
> already in use."
> 
> My knowledge in networking and ssh is limited, so any pointers to how I
> would go about this are greatly appreciated.
> 
> Regards,
> 
> Timo
> ___
> Powered by www.kitware.com <http://www.kitware.com>
> 
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
> 
> 
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


[Paraview] Connecting to Catalyst-Enabled Simulation Running on Remote Cluster

2015-05-18 Thread Timo Oster
Hi all,

in an effort to enable live visualization of our simulation code, I have
written a Catalyst adaptor for it. The live visualization is working
great when the ParaView client runs on the same machine as the
simulation, even when the simulation runs in parallel using mpi.

Now I want to do live visualization of a simulation running on a remote
cluster. I am able to get this to work for the simulation running on the
login node of the cluster:

1. Tunnel an ssh connection of port 1 to the cluster:
ssh -L 1:localhost:1 server
2. In the shell that opens, start a paraview server (in the background
with '&')
3. Run the simulation with mpirun (simulation runs only on login node)
4. Start my local ParaView client and connect to localhost:1 to
connect to the remote pvserver through the ssh tunnel
5. In the client, connect to Catalyst (port 2)
6. A provider for the simulation is created and the live visualization works

Now I want to do the same for simulations started on the remote cluster
via the batch job system. In this scenario, the parallel processes of
the simulation will run on different (randomly chosen) nodes on the
cluster. How do I go about getting a connection from my local client to
the Catalyst instances running on those nodes?

I imagine I will need to set up ssh tunnels from the nodes to the login
node where the pvserver is running. I've tried adding a ssh tunnel line
to the job script that is executed when the batch job starts. I've tried
forwarding and reverse-forwarding port 2 (ssh -L and ssh -R) to no
avail. The best I get is "ERROR: In
/.../ParaView_git/VTK/Common/System/vtkSocket.cxx, line 206
vtkServerSocket (0x18e0930): Socket error in call to bind. Address
already in use."

My knowledge in networking and ssh is limited, so any pointers to how I
would go about this are greatly appreciated.

Regards,

Timo
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview