Commit b25070b5 authored by Mathieu Westphal's avatar Mathieu Westphal Committed by Kitware Robot

Merge topic 'docImprovements'

1b0daf14 Documentation imprvement to filedriver.py and build.md
Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
Acked-by: Nicolas Vuaille's avatarNicolas Vuaille <nicolas.vuaille@kitware.com>
Acked-by: David E. DeMarle's avatarDavid E. DeMarle <dave.demarle@kitware.com>
Merge-request: !3918
parents 4387fd1e 1b0daf14
Pipeline #160867 failed with stage
in 0 seconds
......@@ -62,7 +62,7 @@ To build ParaView developement version (usually refered as "master"), please run
git clone --recursive https://gitlab.kitware.com/paraview/paraview.git
mkdir paraview_build
cd paraview_build
cmake -GNinja -DPARAVIEW_ENABLE_PYTHON=ON -DPARAVIEW_USE_MPI=ON -DVTK_SMP_IMPLEMENTATION=TBB -DCMAKE_BUILD_TYPE=Release ../paraview
cmake -GNinja -DPARAVIEW_ENABLE_PYTHON=ON -DPARAVIEW_USE_MPI=ON -DVTK_SMP_IMPLEMENTATION_TYPE=TBB -DCMAKE_BUILD_TYPE=Release ../paraview
ninja
```
......@@ -74,7 +74,7 @@ cd paraview
git checkout tag
git submodule update --init --recursive
cd ../paraview_build
cmake -GNinja -DPARAVIEW_ENABLE_PYTHON=ON -DPARAVIEW_USE_MPI=ON -DVTK_SMP_IMPLEMENTATION=TBB -DCMAKE_BUILD_TYPE=Release ../paraview
cmake -GNinja -DPARAVIEW_ENABLE_PYTHON=ON -DPARAVIEW_USE_MPI=ON -DVTK_SMP_IMPLEMENTATION_TYPE=TBB -DCMAKE_BUILD_TYPE=Release ../paraview
ninja
```
......@@ -91,9 +91,8 @@ Double click on the paraview executable in the bin directory or run in the previ
* Download and install [git bash for windows][gitforwindows]
* Download and install [cmake][cmake-download]
* Download and install [Visual Studio 2015 Community Edition][visual-studio]
* Download and install [ninja-build][ninja]
* Download and install [Microsoft MPI][msmpi]
* Download and install [Intel TBB for windows][tbb]
* Download [ninja-build][ninja] and drop ninja.exe in C:/Windows/
* Download and install both msmpisetup.exe and msmpisdk.msi from [Microsoft MPI][msmpi]
* Download and install [Python for windows][pythonwindows]
#### Recover the source
......@@ -128,7 +127,7 @@ git submodule update --init --recursive
* Open VS2015 x64 Native Tools Command Prompt and run the following commands
```sh
cd C:\pv\pvb
cmake -GNinja -DPARAVIEW_ENABLE_PYTHON=ON -DPARAVIEW_USE_MPI=ON -DVTK_SMP_IMPLEMENTATION=TBB -DCMAKE_BUILD_TYPE=Release ..\pv
cmake -GNinja -DPARAVIEW_ENABLE_PYTHON=ON -DPARAVIEW_USE_MPI=ON -DVTK_SMP_IMPLEMENTATION_TYPE=OpenMP -DCMAKE_BUILD_TYPE=Release ..\pv
ninja
```
......
......@@ -2,16 +2,21 @@ r"""
This script is meant to act as a Catalyst instrumented simulation code.
Instead of actually computing values though it just reads in files that
are passed in through the command line and sets that up to act like
it's coming in as simulation computed values. The script must be run
with pvbatch with the following arguments:
it's coming in as simulation computed values.
This script must be run with pvbatch, either in serial or in parallel.
The arguments are as follows :
* -sym if run with more than a single MPI process so that pvbatch will
have all processes run the script.
* a list of files in quotes (wildcards are acceptable) but these are
treated as a single argument to the script.
* a list of Catalyst Python scripts.
An example of how to use this script would be:
mpirun -np 5 <path>/pvbatch -sym "input_*.pvtu" makeanimage.py makeaslice.py
eg, in serial :
<path>/pvbatch filedriver.py "temporalFile.ex2" gridwriter.py
eg, in parallel
mpirun -np 5 <path>/pvbatch filedriver.py -sym "input_*.pvtu" makeanimage.py makeaslice.py
This script currently only handles a single channel. It will try to find
an appropriate reader for the list of filenames and loop through the timesteps.
......@@ -70,7 +75,6 @@ for script in sys.argv[2:]:
pipeline.Initialize(script)
catalyst.AddPipeline(pipeline)
# we get the channel name here from the reader's dataset. if there
# isn't a channel name there we just assume that the channel name
# is 'input' since that's the convention for a single input
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment