nilmdb/tests/data/extract-4

1332496830.008333 259567.000000 222698.000000 6207.600098 678.671997 9380.230469 4575.580078 2830.610107 2688.629883
1332496830.016667 263073.000000 223304.000000 4961.640137 2197.120117 7687.310059 4861.859863 2732.780029 3008.540039
Extract works now and we're back to 100% test coverage! It's slow, though; need to figure out where the slowdown lies. Add stream existence check to server's /intervals and /extract paths, add tests for it. Make start and end arguments optional for /extract, like /intervals Move --quiet command line option to just the insert subcommand. It's the only one that uses it right now, and otherwise it doesn't show up in after a "nilmtool.py intervals --help". Might revisit this later if more commands start supporting --quiet. Change cmdline/extract's write into a print, to keep the trailing newline. Fix lingering uses of Interval in nilmdb and change to DBInterval instead. Fix nilmdb interval bisection: - handle common case optimization correctly - db_endpos is always one after the last row, so use hi=db_endpos-1 Finish nlimdb stream_extract Add a bunch of cmdline tests for extract, particularly testing border cases around start/end. Compares output to a set of files stored in the tests/data dir. Some more tests in test_client to get better coverage. git-svn-id: https://bucket.mit.edu/svn/nilm/nilmdb@10893 ddd99763-3ecb-0310-9145-efcb8ce7c51f 2012-05-30 14:24:36 -04:00			`1332496830.008333 259567.000000 222698.000000 6207.600098 678.671997 9380.230469 4575.580078 2830.610107 2688.629883`
			`1332496830.016667 263073.000000 223304.000000 4961.640137 2197.120117 7687.310059 4861.859863 2732.780029 3008.540039`