I have updated all of the source to use Scalars instead of hard-coded
floats.  I have also included my own source files and updated them to
work with this version of hoomd.
I have added my own source files (used for sputtering simulations) to
the full_double branch.
I have added SINGLE_PRECISION checks throughout the code in order to
prepare it for running in double precision on GPUs.  I have changed the
CMake files to allow CUDA to be enabled even when single precision is
disabled.
The code is now fully capable of double precision save for the EAM
force, binned neighbor list, and PPPM force.  I am still working out how
to get those functions working.
I have updated the block sizes for the Tersoff and Moliere forces in
pair.py.
I have changed PotentialTripletGPU, PotentialPairGPU, and
TablePotentialGPU to use texture reads in double precision.  I have also
streamlined some of the code in the CGCMMForceGPU.cu file.
Bug fixes in files below.
I have added a new compile option, ENABLE_TEXTURES, that determines
whether to use texture reads or direct memory reads when running on the
GPU.  When SINGLE_PRECISION and ENABLE_CUDA are on, this value is forced
on.  When ENABLE_CUDA is on but SINGLE_PRECISION is off this value is
user-selectable.  When ENABLE_CUDA is off the value of this option makes
no difference in the compiling process.
I have added the necessary code for reading double precision textures to
the FIRE energy minimizer.
CGCMMAngleForceGPU.cu was updated to use the double-precision texture
reads instead of the direct memory reads.  Unlike PotentialPairGPU.cuh,
this file does not allow for the user to specify at compile time how
double precision values will be handled.

CGCMMForceGPU.cu and TablePotentialGPU.cu were updated in a similar
fashion.
I have moved the texture-fetching functions to HOOMDMath.h so that there
aren't a bunch of copies of the functions in a bunch of different files.
I have also updated all code that uses texture reads to use the new
functions for fetching Scalar textures.  Integer texture reads are
unaffected.
I renamed the files for the Tersoff force computations because I did not
think it appropriate to label it as a generic three-body potential.  It
is unlikely that any other three-body potentials use a form similar
enough to the Tersoff potential that they can be handled just by using
different evaluators.
I removed my updater for removing particles since that is not going into
the official release.
Merge branch 'master' into full_double

Conflicts:
	libhoomd/computes_gpu/NeighborListGPU.cu
	libhoomd/computes_gpu/NeighborListGPU.cuh
	libhoomd/updaters_gpu/TwoStepNVTRigidGPU.cc
Merge branch 'master' into full_double

Conflicts:
	libhoomd/cuda/PPPMForceGPU.cu
	python-module/hoomd_script/update.py
Merge branch 'master' into full_double
Reset executable flag on scripts
Change tabs to spaces
Update bond table to work with double precision builds

refs #1035
Update NPTMKT to work with double builds

refs #1035