[Paraview] Newbie question

[Berk Geveci]

I can guess what the problem is. When paraview is compiled with mpich
(the version I use is 1.2.5), sometimes you have to run it using the
full path.

ParaView tries to locate the tcl/tk files when it is run. To do this,
it makes a system call to get the location of the executable and
performs a search relative to this location. If paraview is compiled
with mpich, MPI_Init() for some reason screws up how the function to
get the location of the executable works. As a result, paraview
searches starting from the wrong location. There are three ways to fix
this problem: 1. always execute paraview with the full path (creating
an alias works well) 2. always execute paraview with mpirun -np 1
<paraview> 3. cd to where the paraview executable is and start
paraview from there.

This does not happen if paraview is not compiled with mpich.

-Berk

On 2/22/06, Kent Eschenberg <eschenbe at psc.edu> wrote:
> Very interesting. Those variables are not set on my Redhat Fedora Core 4
> system yet Paraview works.
>
> Kent
>
> >> In addition you may have to set your enviroment variables 'TCL_LIBRARY'
> >> and 'TCLLIBPATH'. 'TCL_LIBRARY' should be set to the location of
> >> init.tcl - something like:
> >> TCL_LIBRARY=/usr/local/ParaView/lib/paraview-2.2/TclTk/lib/tcl8.4/
> >>
> > The above appears to have fixed the issue. I set both the environment
> > variables to /usr/share/tcl/tcl8.4 (on this Suse 10.0 box) and at least
> > as much as I had tired previously seems to work.
>
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>