Update VisItBridge to include new lammps reader

Change-Id: Iaeee1e7561eecb59dd26ce4ba34c958424998f2d
Merge branch 'pflotran_timeseries' into 13902_visit_lammps_dump_crashes

Change-Id: Ic8f228a8cb6cccdd16340f4539f92e74cef3f945
Add test for LAMMPS Dump reader

Change-Id: Id1d88fec6b546299fde4a2f84745b2c526e75bb6
Remove unneeded breaks to paraview tests.

Change-Id: Ifab87f61ba973b0f109b91009e12d4ac14c60e76
Merge branch 'pflotran_timeseries' into 13902_visit_lammps_dump_crashes

Change-Id: If958a14b7959c3df673750f1e01d1ba12837ccaf
Includes for libusb are not needed on Mac OS X

Change-Id: I9d7117aafb39a3ea9a52cb6e13780d97a6c06b9b
Remove trailing whitespace

Change-Id: Ie36d8f2ac902f08c35f0d8806ab0beb8dcb758db
Rename wampURL => sessionURL

Having wamp in public interface may be confusing if we
move away from WAMP in the future, so use the more generic
session prefix.

Change-Id: Idc52080fe4d0b0d14e309f5da2645feee429f2d3
Remove tailing whitespace

Change-Id: Ia73ae69ea6df32740aa957ad87cc442f35d66e25
Rename url => sessionManagerURL

url is somewhat ambiguous as there is the sesssionURL
in the configuration class as well.

Change-Id: I32548376dc08edfb9d10339366bae73d73d371a7
Disable coloring by partial array in the test.

As per bug report 13906 the names of partial spanning arrays
on multiblock datasets change based on if we are connected to a remote
server or not. Because of this issue we can't color by an array
and have a stable test

Change-Id: I52e659eddc6ceebe9eba0d2e6713890ece70df67
Revert "Disable coloring by partial array in the test."

This reverts commit 358f40aac3d2a2ef9aee877155635f680eff5f5e.

Change-Id: Ia5c9c0ced365f85da797835bc3937c2313359690
BUG #13906. Fix partial arrays not reported in client-server.

Information about partial arrays was never serialized to CS streams and hence
was lost whenever information was transferred between processes. This fixes it.

Change-Id: I28c998f3d2ef71c6da42d98190728b11c33ff75c
Fix test after we fixed the partial array issue.

Change-Id: Iac3c96c9c06ccba772944044935a20b91767a6db
Fix AUTOINIT issues when building external plugins.

VTK_USE_FILE adds definitions for ${module}_AUTOINIT for all enabled modules.
This is okay for VTK, with ParaView, AUTOINIT is not useful since one needs
to init the CS streams separately. Also use AUTOINIT is defined, any application
needs to link against all enabled VTK modules which ends up being a very long
list and hard to keep up-to-date. We over come this issue by simply not setting
the ${module}_AUTOINIT definies.  So we get the current COMPILE_DEFINITIONS on
the directory and remove references to AUTOINIT.

Change-Id: I2345223af5588e0b9979f89dc7fa628cf6782278
Updating test after partiall array fix.

Change-Id: I97c69ff2aeb4e9f8ad762ef56fd70099619678e3
Add second lammps dump test to verify atom id loading works

Change-Id: Ic3058d0ba5adf67c0ec8b1249ce6cff00964da83
Update VisItBridge to get lammps dump reader atom id loading support

Change-Id: Id0028172eb2669bd393a05349652319fca81dd03
Update VTK to VTK master

Change-Id: I3b8fb4f449d5f1f3e2742a1a2fee20d172dbacfe
Fix test after partial array fix.

Change-Id: I0ce29a2007176141096cad3635df4f4061f6ba46