ptang4512 / electricsleep

Automatically exported from code.google.com/p/electricsleep
Other
0 stars 0 forks source link

Enhancement-export history #27

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
suggest a capability to export the historical information into a.csv  format 
file (along with any calibration information, alarm settings and comments-if 
that feature is implemented)

Original issue reported on code.google.com by pegbat...@gmail.com on 4 Dec 2010 at 3:55

GoogleCodeExporter commented 9 years ago
This is very possible and I will look into it. But... do you want this 
functionality because ElectricSleep doesn't analyze sleep data internally, or 
for some other reason? Just wondering ;)

Original comment by jondwil...@gmail.com on 5 Dec 2010 at 6:45

GoogleCodeExporter commented 9 years ago
I am interested in analyzing the quality of sleep which may be affected by 
other factors.  In an earlier version of your app, I noticed that I seemed to 
have longer periods of no  activity when I fell asleep with my light on.  I 
noticed this right before you published the most recent version (where now it 
seems I have very very few periods of no, or low, activity).  So I am 
interested in using this as somewhat of a sleep diary,  and then, if I can 
export the data, I can evaluate groups of data based on conditions I have 
annotated, and perhaps make changes in my sleeping environment to improve the 
quality of my sleep.

Original comment by pegbat...@gmail.com on 6 Dec 2010 at 12:10

GoogleCodeExporter commented 9 years ago
you have very few periods of no/low activity in 0.4.0? If so, try setting the 
Sensor delay option to UI.

Anyway, I intend for ElectricSleep to become a "sleep diary" and analysis tool, 
so exporting will hopefully become a bit redundant. 

Original comment by jondwil...@gmail.com on 6 Dec 2010 at 4:28

GoogleCodeExporter commented 9 years ago
Ah....  My droid didn't notify me when the latest version was available.  I was 
relying on it to do so.  Now I know to go looking for updates manually.  I'll 
use the new version starting tonight.

   I don't know exactly what I'd try to run statistics on until I had a body of information to play with.  If you are going to be running analyses on more than just movement you may want to create some structured fields available to the user to fill in if he/she wants.  e.g. room temp, lighting conditions, number/time of external interruptions (phone-crying child-snoring s.o.), common health changes from the norm (cold/flue)... 

I look forward to using 0.4.0.
Thanks
P

Original comment by pegbat...@gmail.com on 6 Dec 2010 at 9:13

GoogleCodeExporter commented 9 years ago

Original comment by jondwil...@gmail.com on 13 Jan 2011 at 2:14

GoogleCodeExporter commented 9 years ago
Whatever analysis features are included in the app, I'd much rather analyse the 
data on my PC.

Firstly because there is already a large range of data analytics software 
available (my day job is writing one of these products), and secondly because 
I'd much rather use a fast CPU like the 2.4GHz Phenom in my desktop machine 
than the 528MHz Qualcomm in my Hero, which already struggles to draw last 
night's chart on app startup.

Original comment by d.tullemans@gmail.com on 12 May 2011 at 12:53

GoogleCodeExporter commented 9 years ago

Original comment by jondwil...@gmail.com on 11 Sep 2011 at 5:11

GoogleCodeExporter commented 9 years ago
If anyone could tell me where the sleep data is stored on the SD card or how to 
get it off with something like adb I would greatly appreciated while waiting 
for this feature. I will also donate once this feature is added.  

Original comment by jon.cr...@kitware.com on 20 Sep 2011 at 1:34

GoogleCodeExporter commented 9 years ago
it should be in /data/data/com.androsz.electricsleepbeta/databases/sleephistory

If you donate, you would put it in 
/data/data/com.androsz.electricsleep/databases/sleephistory

and you would have best results trying it before running the app the first time.

The data is not in a readily consumable format (it is a SQLite database, with 
most of the important data held in a binary field)

Original comment by jondwil...@gmail.com on 20 Sep 2011 at 3:03

GoogleCodeExporter commented 9 years ago
It would be really good even if export just had the basic information.
Start, end, #spikes, tag/comment, quality, spike threshold.
That way, even though the average is available in the tool, we can look at the
Individual night data. It will also work as a backup of sorts anf also allow us
To export, delete history and then start afresh, thereby getting a new average
via the tool.
The product is great btw and I have used it for a couple of nights already.
wonder how the time to sleep is calculated though.

Original comment by soulsp...@gmail.com on 26 Feb 2012 at 6:59

GoogleCodeExporter commented 9 years ago
It'd be cool to have the sleep history exported to a .csv or plain text, 
something that can be passed to other tools, parsed to have pretty graphs to be 
shared online, loads of potential uses for the data that is collected! Perhaps 
utilize the new dropbox api to allow log dumping to a dropbox folder?

Original comment by sboz...@gmail.com on 12 Feb 2013 at 11:29

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I'd add my vote for this one. I'd really appreciate to postprocess the data on 
my PC. Is there really no way of accessing it? Is there no desktop sqLite 
software that can read the data file you spotted in #9? And what is the format 
hidden behind this mysterious binary filed?
The app is great for recording, but analysis is far too simple regarding the 
data collected. And I agree with #6, there's no point in manipulating charts on 
a phone. Screen is too small and CPU power not there. Plus the possibilities 
are endless and I doubt that a single analysis would fit the need of all of us 
beyond what's already there. Each one of us is looking for a particular view on 
the data and trying to satisfy everyone directly in the app would be a far too 
long task, longerr at least than an export feature ;)

Original comment by samy8...@gmail.com on 3 Mar 2013 at 9:25