aboutsummaryrefslogtreecommitdiff
path: root/app
diff options
context:
space:
mode:
authorGertjan van den Burg <gertjanvandenburg@gmail.com>2019-06-07 12:57:08 +0100
committerGertjan van den Burg <gertjanvandenburg@gmail.com>2019-06-07 12:57:08 +0100
commit549ddd39a8b9eb9789c9b44e4a96569bf08ec26c (patch)
tree88ad84556cc80bb8c34ba031d30fdc4ec167ae40 /app
parentmerge d3 code for maintainability (diff)
downloadAnnotateChange-549ddd39a8b9eb9789c9b44e4a96569bf08ec26c.tar.gz
AnnotateChange-549ddd39a8b9eb9789c9b44e4a96569bf08ec26c.zip
Minor clarifications in demo
Diffstat (limited to 'app')
-rw-r--r--app/main/demo.py8
1 files changed, 5 insertions, 3 deletions
diff --git a/app/main/demo.py b/app/main/demo.py
index ff13351..afb7f61 100644
--- a/app/main/demo.py
+++ b/app/main/demo.py
@@ -76,8 +76,10 @@ DEMO_DATA = {
Don't worry if you weren't exactly correct on the first try.
The goal of this introduction is to familiarise yourself with
- time series data and with change point detection in
- particular."""
+ time series data and with change point detection in particular.
+ Note that in general we consider the change point to be the
+ point where the new behaviour starts, not the last point of the
+ current behaviour."""
)
)
},
@@ -212,7 +214,7 @@ DEMO_DATA = {
"""
What we see here is a change in *trend*. Changes in trend are
not always change points: gradual changes in direction are
- common and should not be considered *abrupt* changes.
+ common and should not be considered to be *abrupt* changes.
For trend changes it's not always easy to figure out exactly
where the change occurs, so it's harder to get it exactly