Simplifying Remote Visualization for HPC sites: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
(Created page with 'Currently ParaView uses pvsc files for configuring connecting to servers. Although powerful, it's really complicated for site-maintainers to use them. The goal of this page is to…') |
No edit summary |
||
| Line 3: | Line 3: | ||
* SSH-enabled ParaView | * SSH-enabled ParaView | ||
: Martin et. al have an article talking about avoiding ssh-tunneling, instead directly using ssh to talk to pvserver. We should see how we can support that. | : Martin et. al have an article talking about avoiding ssh-tunneling, instead directly using ssh to talk to pvserver. We should see how we can support that. | ||
* We need to distribute pvsc files for all common HPC sites which supports submitting jobs etc. using the native job manager. | |||
* An mac/linux, we can directly assume a local ssh client is present. However, on windows we may need to distribute an ssh client which should be easily replaceable by custom ssh client. | |||
Revision as of 13:15, 29 April 2010
Currently ParaView uses pvsc files for configuring connecting to servers. Although powerful, it's really complicated for site-maintainers to use them. The goal of this page is to consolidate ideas so that we that it's possible for users to simply download ParaView and then submit jobs to any of the major supercomputing sites and visualize their datasets.
- SSH-enabled ParaView
- Martin et. al have an article talking about avoiding ssh-tunneling, instead directly using ssh to talk to pvserver. We should see how we can support that.
- We need to distribute pvsc files for all common HPC sites which supports submitting jobs etc. using the native job manager.
- An mac/linux, we can directly assume a local ssh client is present. However, on windows we may need to distribute an ssh client which should be easily replaceable by custom ssh client.
