N3Roaster
commented
11 years ago Measurement de-duplication would also be a useful thing to have and would go a long way on its own toward resolving the underlying issue without having to throw away any of the data, but it is essential that good test cases are developed for serialization/deserialization before such a change is rolled out.
Configurations with high sample rates, large numbers of channels, and/or channels that are not synchronized to a common clock can result in excessively large data sets which take too long to save to the database and too long to reload for visualization or comparison. In such cases it may be useful to allow saving a partial measurement set. Every measurement with an annotation should be saved and currently there are models available with these plus one measurement per second, 5 seconds, 10 seconds, 15 seconds, 30 seconds, or 60 seconds.
The roaster configuration panel should add a control for selecting among these (or the default of saving everything), and the XML serialization code and example configuration should be examined to determine the most sensible way to respect that setting.