Open CJ-Wright opened 8 years ago
To be a bit verbose we need to have tests which test that our code not only has sound plumbing but returns the data we expect for:
Note that this depends on having the general integrate function broken up into its constituent parts and pipelined together.
See #62
Currently all of our tests on the data reduction module are smoke tests, meaning that they just make certain that our plumbing doesn't leak/error. However this offers no guarantee to the user that the output that we give out is reasonable or even intelligible for that matter. We might add some tests that do this, taking known data with previously performed reduction and making certain we put out reasonable results as well.