cause image
gauge image
effect image

This individual's Time Spent On Software Development is generally highest after a daily total of 3 hours of Cardio Heart Rate Zone over the previous 7 days.
Join This Study
Go To Interactive Study
Blue represents the sum of Cardio Heart Rate Zone over the previous 7 days
An increase in 7 days cumulative Cardio Heart Rate Zone is usually followed by an increase in Time Spent On Software Development. (R = 0.442)
Typical values for Time Spent On Software Development following a given amount of Cardio Heart Rate Zone over the previous 7 days.
Typical Cardio Heart Rate Zone seen over the previous 7 days preceding the given Time Spent On Software Development value.
This chart shows how your Cardio Heart Rate Zone changes over time.
Each column represents the number of days this value occurred.
This chart shows the typical value recorded for Cardio Heart Rate Zone on each day of the week.
This chart shows the typical value recorded for Cardio Heart Rate Zone for each month of the year.
This chart shows how your Time Spent On Software Development changes over time.
Each column represents the number of days this value occurred.
This chart shows the typical value recorded for Time Spent On Software Development on each day of the week.
This chart shows the typical value recorded for Time Spent On Software Development for each month of the year.

Abstract

This individual's Time Spent On Software Development is generally 30% higher than normal after a total of 3 hours Cardio Heart Rate Zone over the previous 7 days. This individual's data suggests with a high degree of confidence (p=1.9720644761658E-30, 95% CI -0.11 to 0.994) that Cardio Heart Rate Zone Minutes has a moderately positive predictive relationship (R=0.44) with Time Spent On Software Development. The highest quartile of Time Spent On Software Development measurements were observed following an average 3 hours Cardio Heart Rate Zone Minutes per day. The lowest quartile of Time Spent On Software Development measurements were observed following an average 96.593059936909 min Cardio Heart Rate Zone Minutes per day.Time Spent On Software Development is generally 28% lower than normal after a total of 97 minutes of Cardio Heart Rate Zone over the previous 7 days. Time Spent On Software Development is generally 30% higher after a total of 3 hours of Cardio Heart Rate Zone over the previous 7 days.

Objective

The objective of this study is to determine the nature of the relationship (if any) between Cardio Heart Rate Zone Minutes and Time Spent On Software Development. Additionally, we attempt to determine the Cardio Heart Rate Zone Minutes values most likely to produce optimal Time Spent On Software Development values.

Participant Instructions

Get Fitbit here and use it to record your Cardio Heart Rate Zone. Once you have a Fitbit account, you can import your data from the Import Data page. This individual's data will automatically be imported and analyzed.
Get RescueTime here and use it to record your Time Spent On Software Development. Once you have a RescueTime account, you can import your data from the Import Data page. This individual's data will automatically be imported and analyzed.

Design

This study is based on data donated by one participant. Thus, the study design is consistent with an n=1 observational natural experiment.

Data Analysis

Cardio Heart Rate Zone Pre-Processing
Cardio Heart Rate Zone measurement values below 0 seconds were assumed erroneous and removed. Cardio Heart Rate Zone measurement values above 7 days were assumed erroneous and removed. It was assumed that any gaps in Cardio Heart Rate Zone data were unrecorded 0 seconds measurement values.
Cardio Heart Rate Zone Analysis Settings

Time Spent On Software Development Pre-Processing
Time Spent On Software Development measurement values below 0 seconds were assumed erroneous and removed. Time Spent On Software Development measurement values above 7 days were assumed erroneous and removed. It was assumed that any gaps in Time Spent On Software Development data were unrecorded 0 seconds measurement values.
Time Spent On Software Development Analysis Settings

Predictive Analytics
It was assumed that 0 hours would pass before a change in Cardio Heart Rate Zone Minutes would produce an observable change in Time Spent On Software Development. It was assumed that Cardio Heart Rate Zone Minutes could produce an observable change in Time Spent On Software Development for as much as 7 days after the stimulus event.
Predictive Analysis Settings

Data Quantity
1156 raw Cardio Heart Rate Zone Minutes measurements with 1238 changes spanning 1462 days from 2015-03-29 to 2019-03-30 were used in this analysis. 559 raw Time Spent On Software Development measurements with 564 changes spanning 682 days from 2016-06-03 to 2018-04-16 were used in this analysis.

Data Sources

Cardio Heart Rate Zone Minutes data was primarily collected using Fitbit. Fitbit makes activity tracking easy and automatic.

Time Spent On Software Development data was primarily collected using RescueTime. Detailed reports show which applications and websites you spent time on. Activities are automatically grouped into pre-defined categories with built-in productivity scores covering thousands of websites and applications. You can customize categories and productivity scores to meet your needs.

Limitations

As with any human experiment, it was impossible to control for all potentially confounding variables. Correlation does not necessarily imply causation. We can never know for sure if one factor is definitely the cause of an outcome. However, lack of correlation definitely implies the lack of a causal relationship. Hence, we can with great confidence rule out non-existent relationships. For instance, if we discover no relationship between mood and an antidepressant this information is just as or even more valuable than the discovery that there is a relationship.
We can also take advantage of several characteristics of time series data from many subjects to infer the likelihood of a causal relationship if we do find a correlational relationship. The criteria for causation are a group of minimal conditions necessary to provide adequate evidence of a causal relationship between an incidence and a possible consequence.

The list of the criteria is as follows:
Strength (A.K.A. Effect Size)
A small association does not mean that there is not a causal effect, though the larger the association, the more likely that it is causal. There is a moderately positive relationship between Cardio Heart Rate Zone and Time Spent On Software Development

Consistency (A.K.A. Reproducibility)
Consistent findings observed by different persons in different places with different samples strengthens the likelihood of an effect. Furthermore, in accordance with the law of large numbers (LLN), the predictive power and accuracy of these results will continually grow over time. 713 paired data points were used in this analysis. Assuming that the relationship is merely coincidental, as the participant independently modifies their Cardio Heart Rate Zone values, the observed strength of the relationship will decline until it is below the threshold of significance. To it another way, in the case that we do find a spurious correlation, suggesting that banana intake improves mood for instance, one will likely increase their banana intake. Due to the fact that this correlation is spurious, it is unlikely that you will see a continued and persistent corresponding increase in mood. So over time, the spurious correlation will naturally dissipate.

Specificity
Causation is likely if a very specific population at a specific site and disease with no other likely explanation. The more specific an association between a factor and an effect is, the bigger the probability of a causal relationship.

Temporality
The effect has to occur after the cause (and if there is an expected delay between the cause and expected effect, then the effect must occur after that delay). The confidence in a causal relationship is bolstered by the fact that time-precedence was taken into account in all calculations.

Biological Gradient
Greater exposure should generally lead to greater incidence of the effect. However, in some cases, the mere presence of the factor can trigger the effect. In other cases, an inverse proportion is observed: greater exposure leads to lower incidence.

Plausibility
A plausible bio-chemical mechanism between cause and effect is critical. This is where human brains excel. Based on our responses so far, 1 humans feel that there is a plausible mechanism of action and 0 feel that any relationship observed between Cardio Heart Rate Zone and Time Spent On Software Development is coincidental.

Coherence
Coherence between epidemiological and laboratory findings increases the likelihood of an effect. It will be very enlightening to aggregate this data with the data from other participants with similar genetic, diseasomic, environmentomic, and demographic profiles.

Experiment
All of human life can be considered a natural experiment. Occasionally, it is possible to appeal to experimental evidence.

Analogy
The effect of similar factors may be considered.

Relationship Statistics

Property Value
Cause Variable Name Cardio Heart Rate Zone
Effect Variable Name Time Spent On Software Development
Sinn Predictive Coefficient 0.442
Confidence Level high
Confidence Interval 0.55196917967178
Forward Pearson Correlation Coefficient 0.442
Critical T Value 1.646
Total Cardio Heart Rate Zone Over Previous 7 days Before ABOVE Average Time Spent On Software Development 3 hours
Total Cardio Heart Rate Zone Over Previous 7 days Before BELOW Average Time Spent On Software Development 97 minutes
Duration of Action 7 days
Effect Size moderately positive
Number of Paired Measurements 713
Optimal Pearson Product 0.3413666018055
P Value 1.9720644761658E-30
Statistical Significance 1
Strength of Relationship 0.55196917967178
Study Type individual
Analysis Performed At 2019-04-04

Cardio Heart Rate Zone Statistics

Property Value
Variable Name Cardio Heart Rate Zone Minutes
Aggregation Method SUM
Analysis Performed At 2019-03-31
Duration of Action 7 days
Kurtosis 3.1951071398943
Maximum Allowed Value 7 days
Mean 18 minutes
Median 8 minutes
Minimum Allowed Value 0 seconds
Number of Changes 1238
Number of Correlations 1876
Number of Measurements 1156
Onset Delay 0 seconds
Standard Deviation 19.463294464905
Unit Minutes
Variable ID 5211881
Variance 378.8198314276

Time Spent On Software Development Statistics

Property Value
Variable Name Time Spent On Software Development
Aggregation Method SUM
Analysis Performed At 2019-03-30
Duration of Action 7 days
Kurtosis 3.9509291749464
Maximum Allowed Value 7 days
Mean 3 hours
Median 0 seconds
Minimum Allowed Value 0 seconds
Number of Changes 564
Number of Correlations 803
Number of Measurements 559
Onset Delay 0 seconds
Standard Deviation 4.5869899791775
Unit Hours
Variable ID 111632
Variance 21.040477069075

Tracking Cardio Heart Rate Zone

Get Fitbit here and use it to record your Cardio Heart Rate Zone. Once you have a Fitbit account, you can import your data from the Import Data page. This individual's data will automatically be imported and analyzed.

Tracking Time Spent On Software Development

Get RescueTime here and use it to record your Time Spent On Software Development. Once you have a RescueTime account, you can import your data from the Import Data page. This individual's data will automatically be imported and analyzed.
Join This Study

https://lh6.googleusercontent.com/-BHr4hyUWqZU/AAAAAAAAAAI/AAAAAAAIG28/2Lv0en738II/photo.jpg Principal Investigator - Mike Sinn