- Works the same in Explorer (tested only on 6.0) and Netscape (tested only on Netscape 7.0 and Mozilla 1.3.1), but does not work in Opera (6.01) ***************************************************************************** */ if (document.images) { // tests for image support trilinos_title_normal = new Image(310, 55); trilinos_title_normal.src = "../../../packages/common/webroot_common/trilinos_title_normal.png"; trilinos_title_over = new Image(310, 55); trilinos_title_over.src = "../../../packages/common/webroot_common/trilinos_title_over.png"; sandia_normal = new Image(180, 29); sandia_normal.src = "../../../packages/common/webroot_common/sandia_normal.png"; sandia_over = new Image(180, 29); sandia_over.src = "../../../packages/common/webroot_common/sandia_over.png"; trilinos_normal = new Image(183, 100); trilinos_normal.src = "../../../packages/common/webroot_common/trilinos_normal.png"; trilinos_over = new Image(183, 100); trilinos_over.src = "../../../packages/common/webroot_common/trilinos_over.png"; } // if (document.images) //-->
|
PyTrilinos Documentation for Trilinos Release 8.0There are a number of ways to obtain PyTrilinos documentation. You should start with the Tutorial page and consult the Frequently Asked Questions page for any initial questions. Running python interactively, you can use the help() or dir() functions on PyTrilinos modules, classes, methods or objects. Within a UNIX shell, you can run pydoc on any class in the PyTrilinos hierarchy. If the python documentation strings do not provide sufficient information, then you should consult this documentation, specifically the Differences Between C++ and Python Implementations pages. If the class or method you are interested in does not appear within these pages, then use the C++ documention, as the C++ and python interfaces are kept analogous whenever possible.
PyTrilinos PrerequisitesTo build PyTrilinos, you must have the following installed:
Building PyTrilinosTo build PyTrilinos for release 8.0 and in the development branch, configure Trilinos with the --enable-pytrilinos option. If you wish to specify a specific python to compile against, use --with-python=path. For releases 6.0 and 7.0, PyTrilinos is properly enabled with the option --enable-python[=path] when you run configure. This will enable the python wrappers for every Trilinos package that supports them. If, for some reason, you wish to disable the python wrappers for a particular package, you may use --disable-package-python, where you substitute the package name for package. PyTrilinos python modules are compiled shared objects. If these shared libraries are linked against static libraries, it can cause problems. One problem is that the run-time typing employed by the Teuchos::ParameterList class can get confused if a parameter is set by one package and then evaluated by the Teuchos package. Other problems crop up under MPI builds where cross-package inheritance is not recognized properly. For these reasons, PyTrilinos needs to re-link static Trilinos libraries as shared before linking the python extension modules. This requirement is universal for release 8.0 and in the development branch, and is required for MPI builds in release 7.0. PyTrilinos takes care of this automatically, although the procedure is rather ad-hoc, and only supported currently for Linux and Mac OS X. Other platforms will link against static Trilinos libraries, and risk the problems described above. If you desire a port to a specific platform, send email to pytrilinos-users@software.sandia.gov. If you build PyTrilinos under Linux or Darwin under the development branch or release 7.0 with MPI, and you wish to test the PyTrilinos modules prior to installing Trilinos, the python test scripts will not be able to find these new shared libraries and will fail. To correct this, you must set an environment variable so that the shared libraries can be found. Under LINUX, this environment variable is LD_LIBRARY_PATH. Under Darwin, this environment variable is DYLD_LIBRARY_PATH. The value that needs to be added to this environment variable is BUILD/package/PyTrilinos/src where BUILD should be replaced with the path to your Trilinos build directory. If other path(s) are already specified in this environment variable, simply separate multiple paths with a colon (:). Furthermore, for MPI you may need to tell mpirun to export this environment variable in order to use it: mpirun -x LD_LIBRARY_PATH -np 4 testVector.py -t Known Issues
Differences Between C++ and Python Implementations
Current PyTrilinos Modules and Wrapped Header Files
|
|
||
| ||||