search

Alexanderreay / funf-open-sensing-framework

Automatically exported from code.google.com/p/funf-open-sensing-framework
0 stars 0 forks source link

Data integrity script #24

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
A script that outputs a report on the data integrity of a merged data db file.  
This would include
  * Data holes
  * Comparing configuration to actual data collected and reporting discrepancies
  * Tolerance parameters to tune how strict data collection should be
  * Per phone (installation), and per probe options

Original issue reported on code.google.com by alan.gar...@gmail.com on 2 Nov 2011 at 5:49

GoogleCodeExporter commented 9 years ago 
options: is that reporting probe settings, or options for what to check in 
different probes?
also maybe as part of the default (or special case) is some sort of battery 
report?

how long do you think this component would take?

Original comment by nad...@gmail.com on 2 Nov 2011 at 10:22

GoogleCodeExporter commented 9 years ago 
* Per phone (installation), and per probe segmentation

is probably a better way to describe.  Being able to isolate and report on only 
one phone, or only one Probe across phones, or only one phone and one probe. 

Later we may be able to segment it by device type or OS version.

This would be a script you would run on your merged database once you had 
collected the data.  A python script to analyze obvious gaps that appear in the 
data, using the configuration file changes that are also in the database.

I am guessing it would take probably a few hours to get something that identify 
and print data gaps, and a couple days to test and add enough other details and 
content to make it useful and readable.  

Later, it may be helpful to have a small visualization for the statistics in 
the script.

Original comment by alan.gar...@gmail.com on 2 Nov 2011 at 10:28