Add a time based DAUG accumulation

[akrontab]

There is no way to see DAUG score over a time frame or to display DAUG averages over a set period of time. Implement a DAUG average over a DAUG time frame (which needs to be defined)

[danl-zz]

Hi there Aaron.

I just got this email 57 minutes ago. May I ask if this is a late delivery,
or is this anything urgent?

Cheers,

Dan

On Wed, Jan 22, 2014 at 2:46 PM, Aaron Krone notifications@github.comwrote:

There is no way to see DAUG score over a time frame or to display DAUG
averages over a set period of time. Implement a DAUG average over a DAUG
time frame (which needs to be defined)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1
.

With best regards,

Dan Lubrich

[akrontab]

Hi Dan!

Nothing urgent actually. Just cleaning up the Arduino code in the
github repository and adding a feature idea to the list. I was thinking
about adding some code and maybe building the project myself.

Thanks,
Aaron

On 01/22/2014 12:44 AM, danlub wrote:

Hi there Aaron.

I just got this email 57 minutes ago. May I ask if this is a late
delivery,
or is this anything urgent?

Cheers,

Dan

On Wed, Jan 22, 2014 at 2:46 PM, Aaron Krone
notifications@github.comwrote:

There is no way to see DAUG score over a time frame or to display DAUG
averages over a set period of time. Implement a DAUG average over a
DAUG
time frame (which needs to be defined)

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/1
.

With best regards,

Dan Lubrich

—
Reply to this email directly or view it on GitHub
#1 (comment).

[danl-zz]

Good idea! DAUGs were caculated every 1/10 s I believe, and then we set
certain limits in order to make it suitable for demonstration. For a real
application one would have to make the total time flexible and then apply
the limits accordingly (i.e. less for one hour, more for 12 hours) but in
principal should be the same.

I would recommend to check these DAUGs again. Although the Daug was running
around during the presentation
, the DAUGs did not seem to count up, although they did after the reset.

Cheers,

Dan

On Wed, Jan 22, 2014 at 3:54 PM, Aaron Krone notifications@github.comwrote:

Hi Dan!

Nothing urgent actually. Just cleaning up the Arduino code in the
github repository and adding a feature idea to the list. I was thinking
about adding some code and maybe building the project myself.

Thanks,
Aaron

On 01/22/2014 12:44 AM, danlub wrote:

Hi there Aaron.

I just got this email 57 minutes ago. May I ask if this is a late
delivery,
or is this anything urgent?

Cheers,

Dan

On Wed, Jan 22, 2014 at 2:46 PM, Aaron Krone
notifications@github.comwrote:

There is no way to see DAUG score over a time frame or to display DAUG
averages over a set period of time. Implement a DAUG average over a
DAUG
time frame (which needs to be defined)

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/1

.

With best regards,

Dan Lubrich

—
Reply to this email directly or view it on GitHub
<
#1 (comment)
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-33000128
.

With best regards,

Dan Lubrich

[akrontab]

Agreed. I'm trying to think of a good way to count the DAUGs for a given
time and if it should be on the iPad app or if the logic should be
calculated by the Xadow and sent over Bluetooth, or maybe both.

Joey actually realized the charge on the battery was getting low and the
Xadow reset every time it couldn't get enough power to run the LEDs. I also
found out that the blue color on the LED takes the most current versus any
other color.

I also cleaned up the code a little bit and it take almost 3kb less space
on xadow. Feel free to go crazy on the code in github.

Cheers and DAUG über alles ;)
Aaron
On Jan 22, 2014 1:35 AM, "danlub" notifications@github.com wrote:

Good idea! DAUGs were caculated every 1/10 s I believe, and then we set
certain limits in order to make it suitable for demonstration. For a real
application one would have to make the total time flexible and then apply
the limits accordingly (i.e. less for one hour, more for 12 hours) but in
principal should be the same.

I would recommend to check these DAUGs again. Although the Daug was
running
around during the presentation
, the DAUGs did not seem to count up, although they did after the reset.

Cheers,

Dan

On Wed, Jan 22, 2014 at 3:54 PM, Aaron Krone notifications@github.comwrote:

Hi Dan!

Nothing urgent actually. Just cleaning up the Arduino code in the
github repository and adding a feature idea to the list. I was thinking
about adding some code and maybe building the project myself.

Thanks,
Aaron

On 01/22/2014 12:44 AM, danlub wrote:

Hi there Aaron.

I just got this email 57 minutes ago. May I ask if this is a late
delivery,
or is this anything urgent?

Cheers,

Dan

On Wed, Jan 22, 2014 at 2:46 PM, Aaron Krone
notifications@github.comwrote:

There is no way to see DAUG score over a time frame or to display
DAUG
averages over a set period of time. Implement a DAUG average over a
DAUG
time frame (which needs to be defined)

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/1

.

With best regards,

Dan Lubrich

—
Reply to this email directly or view it on GitHub
<

#1 (comment)

.

—
Reply to this email directly or view it on GitHub<
https://github.com/hackphx-arduinowearables/Team09/issues/1#issuecomment-33000128>

.

With best regards,

Dan Lubrich

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-33001993
.