ParaView3:Distribution Checklist

From ParaQ Wiki

Jump to: navigation, search

Here's a checklist that needs to be followed to ensure that we don't end up with broken releases.

Contents

Branching Checklist

  • Check the version strings in the application (About dialog etc.), do they reflect the correct version?
  • Did you update the CVS head version when you branched?

Building Checklist

  • Are you building with Shared libraries enabled?
  • Ensure HTMLDocumentation target is explicitly built.
  • Ensure python is enabled.
  • Ensure Prism plugins are included in the tarball.
  • Ensure VTK_USE_QVTK_QTOPENGL:BOOL=ON
  • Ensure PARAVIEW_TESTING_WITH_PYTHON:BOOL=OFF
  • Try turning on PARAVIEW_INSTALL_DEVELOPMENT
    • perform a make install to see if there are any install rule issues.

Running Checklist

  • Does F1 work? Is help shown correctly?
  • Is documentation available for filters/sources etc.?
  • Verify QTOpenGL is working by creating a QT Plot.
    • Create Wavelet source
    • Filter -> Data Analysis -> Plot Over Line
  • Does python shell work? Check by importing paraview modules.
  • Are you sure in packaged python is being used and not the system python?
    • ./paraview -ldd | grep python
  • Ensure pvbatch/pvpython works. This needs separate check from python shell.
    • ./pvpython
    • >>>import paraview.simple
  • Ensure Prism plugins are in a directory that the plugin manager searches by default.


Workflow

  • Start ParaView
  • Wavelet, Volume Render
  • Python Shell (from client)
    • import sys
    • sys.path -- are all paths within the paraview install dir?
    • Cone()
    • Show()
    • Render()
  • About Dialog -- check the version strings.
  • Help
    • F1
    • Look at the lists for "Readers", "Writers", "Filters" etc. to ensure that they are indeed valid.
    • Create Sphere and check help for the Sphere using help button on Properties panel.
  • Plugins
    • Load all plugin shared libraries to ensure that they load correctly
    • VisTrails
      • Load VisTrails plugin
      • Create Sphere
      • Change Theta Resolution
      • Click around the VisTrails dialog to see that it undoes-redoes
  • Readers
    • Load delta.cgns
    • Load tire.silo
    • Load Scenario1_p1.xmf - tests Xdmf, hdf5 and zlib.
  • AutoMPI
    • Settings -> Enable Multi Core
    • Disconnect
    • Sphere
    • Process ID Scalars - If more than one core you should see multi color sphere.
Retrieved from "http://paraview.org/ParaView3/index.php/ParaView3:Distribution_Checklist"
Personal tools