Make tests shorter

We should be able to write tests that go very fast, just doing the bare minimum to make sure things are working. Here is the latest timing information (from nosetests --with-timer amp/tests/), which shows us where to focus.

zernike_test.test: 254.8403s
force_call_test.test: 181.8552s
gaussian_test.test: 59.5360s
numeric_analytic_test.test: 55.1103s
force_call_test_tflow.non_periodic_test: 50.0682s
train_test.test: 26.0392s
test_gaussian_neural.train_test: 22.3611s
fpplot_test.test: 16.1364s
test_gaussian_tflow.train_test: 11.6122s
force_call_test.periodic_test: 10.3278s
train_test.periodic_0th_bfgs_step_test: 3.4943s
force_call_test.non_periodic_test: 3.2241s
test_NN_nodeplot.test_nodeplot: 2.5974s
force_call_test_tflow.periodic_test: 0.6090s
train_test.non_periodic_0th_bfgs_step_test: 0.4838s
displaced_atom_test.test: 0.1663s
rotated_atoms_test.test: 0.0199s
----------------------------------------------------------------------
Ran 17 tests in 717.175s

Comments (1)