aboutsummaryrefslogtreecommitdiff
path: root/app
diff options
context:
space:
mode:
authorGertjan van den Burg <gertjanvandenburg@gmail.com>2019-08-27 11:13:44 +0100
committerGertjan van den Burg <gertjanvandenburg@gmail.com>2019-08-27 11:13:44 +0100
commitf164834310df0f67fee7ac432a95d7b8c59ad212 (patch)
tree8c227cdc88db1f46d0ce8d47038856075b269a75 /app
parentScore user on demo and ask to redo if subpar (diff)
downloadAnnotateChange-f164834310df0f67fee7ac432a95d7b8c59ad212.tar.gz
AnnotateChange-f164834310df0f67fee7ac432a95d7b8c59ad212.zip
add demo example of a random walk
Diffstat (limited to 'app')
-rw-r--r--app/main/demo.py31
1 files changed, 30 insertions, 1 deletions
diff --git a/app/main/demo.py b/app/main/demo.py
index 42525b1..6b1fee3 100644
--- a/app/main/demo.py
+++ b/app/main/demo.py
@@ -234,6 +234,35 @@ DEMO_DATA = {
},
},
7: {
+ "dataset": {"name": "demo_650"},
+ "learn": {
+ "text": markdown.mardown(
+ textwrap.dedent(
+ """
+ The datasets we've seen so far are all relatively well behaved,
+ but real-world time series are often more chaotic.
+ """
+ )
+ )
+ },
+ "annotate": {"text": RUBRIC},
+ "evaluate": {
+ "text": markdown.markdown(
+ textwrap.dedent(
+ """'
+ This was an example of a [random
+ walk](https://en.wikipedia.org/wiki/Random_Walk), without a
+ change point. Some time series data will look similar to this
+ random walk, in the sense that it moves around, changes, but
+ does not change *abruptly*. This is important to keep in mind,
+ because not all datasets that you'll see will necessarily have
+ change points (it's up to you to decide!)
+ """)
+
+ )
+ },
+ },
+ 8: {
"dataset": {"name": "demo_700"},
"learn": {
"text": markdown.markdown(
@@ -261,7 +290,7 @@ DEMO_DATA = {
)
},
},
- 8: {
+ 9: {
"dataset": {"name": "demo_800"},
"learn": {
"text": markdown.markdown(