Documentation for VPPV closes #11272

framework/doc/content/documentation/systems/AuxKernels/VectorPostprocessorVisualizationAux.md

@@ -0,0 +1,23 @@
+# VectorPostprocessorVisualizationAux
+
+## Short Description
+
+!syntax description /AuxKernels/VectorPostprocessorVisualizationAux
+
+## Description
+
+This object is intended to let you view VectorPostprocessor vectors that are of lenght `num_procs` (meaning there is one value per MPI process).  This object will take those values and fill up an Auxiliary field with them so the values can be visualized.
+
+## Important Notes
+
+Note: the VectorPostprocessor must be syncing the vectors it's computing to all processors.  By default many just compute to processor 0 (because that's where output occurrs).
+
+For instance: this is the case for [WorkBalance].  By default it only syncs to processor 0, but it has a parameter (`sync_to_all_procs`) to tell it to create copies of the vectors on all processors.
+
+!syntax parameters /AuxKernels/VectorPostprocessorVisualizationAux
+
+!syntax inputs /AuxKernels/VectorPostprocessorVisualizationAux
+
+!syntax children /AuxKernels/VectorPostprocessorVisualizationAux
+
+!bibtex bibliography

framework/doc/content/documentation/systems/VectorPostprocessors/WorkBalance.md

@@ -12,7 +12,9 @@ Currently computes: number of local elements, nodes, dofs and partition sides.
 
 ## Important Notes
 
-Note that this VPP only computes the complete vector on processor 0.  The vectors this VPP computes may be very large and there is no need to have a copy of them on every processor.
+Note that, by default, this VPP only computes the complete vector on processor 0.  The vectors this VPP computes may be very large and there is no need to have a copy of them on every processor.
+
+However, you can modify this behavior by setting `sync_to_all_procs = true`
 
 !syntax parameters /VectorPostprocessors/WorkBalance