diff --git a/docs/figure/report.Rmd/figholdout-1.svg b/docs/figure/report.Rmd/figholdout-1.svg deleted file mode 100644 index 9853f36..0000000 --- a/docs/figure/report.Rmd/figholdout-1.svg +++ /dev/null @@ -1,1310 +0,0 @@ - - diff --git a/docs/figure/report.Rmd/vtachy-1.svg b/docs/figure/report.Rmd/vtachy-1.svg deleted file mode 100644 index df12a25..0000000 --- a/docs/figure/report.Rmd/vtachy-1.svg +++ /dev/null @@ -1,653 +0,0 @@ - - diff --git a/docs/report.html b/docs/report.html index 1f5efda..3fa591a 100644 --- a/docs/report.html +++ b/docs/report.html @@ -440,7 +440,7 @@
Checks: -5 +7 -2 +0
Knit directory: @@ -490,21 +490,16 @@
The R Markdown file has unstaged changes.
-To know which version of the R Markdown file created these
-results, you’ll want to first commit it to the Git repo. If
-you’re still working on the analysis, you can ignore this
-warning. When you’re finished, you can run
-wflow_publish
to commit the R Markdown file and
-build the HTML.
Great! Since the R Markdown file has been committed to the Git repository, you +know the exact version of the code that produced these results.
To ensure reproducibility of the results, delete the cache directory
-report_cache
-and re-run the analysis. To have workflowr automatically delete the cache
-directory prior to building the file, set delete_cache = TRUE
-when running wflow_build()
or wflow_publish()
.
Nice! There were no cached chunks for this analysis, so you can be confident +that you successfully produced the results during this run.
- + -Repository version: 4437e7a +Repository version: 4887954
Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility.
-The results in this page were generated with repository version 4437e7a. +The results in this page were generated with repository version 4887954. See the Past versions tab to see a history of the changes made to the R Markdown and HTML files.
@@ -675,7 +661,7 @@Note that any generated files, e.g. HTML, png, CSS, etc., are not included in @@ -765,6 +742,40 @@
regime_threshold
and regime_landmark
, mp_threshold
and window_size
, mp_threshold
and regime_landmark
. B) Refitting the model with these interactions taken into account, the strength is substantially reduced, except for the first, showing that indeed there is a strong correlation between those variables.
++ +
++Version + | ++Author + | ++Date + | +
---|---|---|
+4887954 + | ++Francisco Bischoff + | ++2023-08-13 + | +
+ +
++Version + | ++Author + | ++Date + | +
---|---|---|
+4887954 + | ++Francisco Bischoff + | ++2023-08-13 + | +
Fig. 4.5 and Fig. 4.6 show the effect of each feature on the FLOSS score. The more evident difference is the shape of the effect of time_constraint
that initially suggested better results with larger values. However, removing the interactions seems to be a flat line.
Based on Fig. 4.4 and Fig. 4.6 we can infer that:
+ +
++Version + | ++Author + | ++Date + | +
---|---|---|
+4887954 + | ++Francisco Bischoff + | ++2023-08-13 + | +
Figure 4.6: This shows the effect each variable has on the FLOSS score, taking into account the interactions.
+ +
++Version + | ++Author + | ++Date + | +
---|---|---|
+4887954 + | ++Francisco Bischoff + | ++2023-08-13 + | +
According to the FLOSS paper41, the window_size
is indeed a feature that can be tuned; nevertheless, the results appear to be similar in a reasonably wide range of window sizes, up to a limit, consistent with our findings.
+ +
++Version + | ++Author + | ++Date + | +
---|---|---|
+4887954 + | ++Francisco Bischoff + | ++2023-08-13 + | +
Fig. 4.8 shows the best effort in predicting the most complex recordings. One information not declared before is that if the model does not predict any change, it will put a mark on the zero position. On the other side, the truth markers positioned at the beginning and the end of the recording were removed, as these locations lack information and do not represent a streaming setting.
+ +
++Version + | ++Author + | ++Date + | +
---|---|---|
+4887954 + | ++Francisco Bischoff + | ++2023-08-13 + | +
Fig. 4.9 shows the best performances of the best recordings. Notice that there are recordings with a significant duration and few regime changes, making it hard for a “trivial model” to predict randomly.
+ +
++Version + | ++Author + | ++Date + | +
---|---|---|
+4887954 + | ++Francisco Bischoff + | ++2023-08-13 + | +
+ +
++Version + | ++Author + | ++Date + | +
---|---|---|
+4887954 + | ++Francisco Bischoff + | ++2023-08-13 + | +
Fig. 4.11 the performance of the six best models. They are ordered from left to right, from the worst record to the best record. The top model is the one with the lowest mean across the scores. The blue line indicates the mean score, and the red line the median score. The scores above 3 are squished in the plot and colored according to the scale in the legend.
+ +
++Version + | ++Author + | ++Date + | +
---|---|---|
+4887954 + | ++Francisco Bischoff + | ++2023-08-13 + | +
+ +
++Version + | ++Author + | ++Date + | +
---|---|---|
+4887954 + | ++Francisco Bischoff + | ++2023-08-13 + | +
After the Inner Resampling is done, the best sets of shapelets are selected and evaluated on the Test Set without retraining a new Contrast Profile. Thus assessing the generalization of the shapelet set on new data.
The criteria to select the best sets of shapelets was described on section 3.5.2 being the Precision the ranking criteria. It was also required that the set being present on more than one fold and in both repetitions. Also, the sets of shapelets that had a negative \(\kappa_m\) were discarded.
The following results were obtained:
@@ -4300,6 +4692,17 @@