[Paraview] stereo wall configuration
Moreland, Kenneth
kmorel at sandia.gov
Tue Jul 8 14:59:53 EDT 2008
Try "-display :0.1".
-Ken
On 7/8/08 10:15 AM, "Patrick Shinpaugh" <shpatric at vt.edu> wrote:
> Only the client is displaying on :0.0 and nothing on :0.1. I didn't see
> a -display option when I ran pvserver with --help but I tried it anyway.
> Both -display=:0.1 and --display=:0.1 resulted in the usage information
> being printed out rather than starting the pvserver.
>
> Thinking back on it, I did see a dialog box the first time I got the
> client to connect to the server which said something about a bad X
> connection. Unfortunately, subsequent attempts to read the message fail
> because the dialog box appears and disappears almost immediately (no
> okay button) - nothing is shown in the output window to specify what
> error may have occurred and nothing shows on the command line where the
> pvserver or paraview client were run except "Client connected.".
>
> If there is a bad X connection, there should not be as I can simply run
> `DISPLAY=:0.1 xterm` from a terminal in :0.0 and an xterm will appear in
> :0.1. I do have the Composite extension disabled which is necessary to
> run active stereo (PV built with this->StereoType =
> VTK_STEREO_CRYSTAL_EYES;) and the xorg.conf does have Option "Stereo"
> "3" for screen 1 and is not present for screen 0. Also, I can run active
> stereo in other applications such as VMD with the visual being displayed
> on the :0.1 display.
>
> Any other suggestions would be greatly appreciated.
>
> Thanks,
> Pat
>
>
> Moreland, Kenneth wrote:
>> Is pvserver creating a window on the first screen? It could be that the
>> DISPLAY environment is not being set right. That would probably be a bug in
>> the pvx file processing, but you should be able to get around it by passing
>> a -display flag to the pvserver program.
>>
>> -Ken
>>
>>
>> On 7/7/08 1:19 PM, "Patrick Shinpaugh" <shpatric at vt.edu> wrote:
>>
>>
>>> Hi,
>>> I upgraded from ParaView-2.6.1 to ParaView-3.2.2 on our stereo wall
>>> (CentOS linux built with openmpi). After updating our command line
>>> script and adding a default_servers.pvsc file I am finally able to
>>> connect to the pvserver running on localhost. Unfortunately, it is not
>>> creating a window on the :0.1 screen. Any idea what I might be doing
>>> wrong? Or is there an easier way to render on the second screen? We want
>>> a client on screen 0 and a full screen window on screen 1 which used to
>>> work in PV-2.6.1. Stereo 3 is enabled in X for the screen 1 not on the
>>> screen 0. Pertinent files shown below (note - the lines commented with #
>>> showing the filename are not part of the actual files):
>>>
>>> *********************************************
>>>
>>> # /usr/local/bin/paraview-wall
>>> export
>>> LD_LIBRARY_PATH=/usr/local/qt-4.2.3/lib:/usr/lib/openmpi/1.2.5-gcc/lib:$LD_L
>>> IB
>>> RARY_PATH
>>> mpirun -np 1 pvserver /etc/paraview/wall.pvx &
>>> sleep 5
>>> /usr/local/paraview/bin/paraview --server=localhost --stereo
>>> /etc/paraview/wall.pvx
>>>
>>> *********************************************
>>>
>>> # /etc/paraview/wall.pvx
>>> <?xml version="1.0" ?>
>>> <pvx>
>>> <Process Type="client" />
>>> <Process Type="server" >
>>> <Machine Name="localhost"
>>> Environment="DISPLAY=:0.1"
>>> LowerLeft="-1.0 -1.0 -1.0"
>>> LowerRight="1.0 -1.0 -1.0"
>>> UpperLeft="-1.0 1.0 -1.0" />
>>> </Process>
>>> </pvx>
>>>
>>> *********************************************
>>>
>>> # /usr/local/paraview/lib/paraview-3.2/default_servers.pvsc
>>> <Servers>
>>> <Server name="localhost" resource="cs://localhost:11111">
>>> <ManualStartup/>
>>> </Server>
>>> </Servers>
>>>
>>>
>>> Thanks,
>>> Pat
>>>
>>> --
>>> Patrick Shinpaugh
>>> Virginia Tech
>>> UVAG System Administrator/Programmer
>>> 540-231-2054
>>>
>>> _______________________________________________
>>> ParaView mailing list
>>> ParaView at paraview.org
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>>
>>
>>
>>
>>
>
> --
> Patrick Shinpaugh
> Virginia Tech
> UVAG System Administrator/Programmer
> 540-231-2054
>
>
More information about the ParaView
mailing list