INP_ts.txt). 2. the code to run (
INP_mops.txt). 3. the features to extract from that code (
INP_test_ts.mat) using the following:
TS_Initproduces a Matlab file,
HCTSA.mat, containing all of the structures required to understand the set of time series, operations, and the results of their computation (explained here).
INP_mops.txt, involves significant computation time. Thus, it can be a good first step to test out your analysis pipeline using a smaller, faster feature set. An example is the catch22 set of 22 features.
installof hctsa (by running
Toolboxes/catch22directory of hctsa):
timeSeriesData: either a N x 1 cell (for N time series), where each element contains a vector of time-series values, or a N x M matrix, where each row specifies the values of a time series (all of length M).
labels: a N x 1 cell of unique strings containing a named label for each time series.
keywords: a N x 1 cell of strings, where each element contains a comma-delimited set of keywords (one for each time series), containing no whitespace.
dlmread). Data files should thus be accessible in the Matlab path. Each time-series text file should have a single real number on each row, specifying the ordered values that make up the time series. Once imported, the time-series data is stored in the database; thus the original time-series data files are no longer required, and can be removed from the Matlab path.
NaNto indicate that the input time series is not appropriate for this code.
Databasedirectory of the repository), are as follows:
xrefers to the input time series and
x_zrefers to a z-scored transformation of the input time series (i.e.,
CO_tc3using a z-scored time series as input (
1as the second input with the label
CO_tc3_xz_1, and the second line will add an entry for running the code
ST_lengthusing the untransformed time series,
x, with the label
ST_length(x), and thus the functions
ST_length.mmust be in the Matlab path. Recall that the script
startup.m, which should be run at the start of each session using hctsa, handles the addition of paths required for the default code library.
Databasedirectory of the repository) should contain a row for every operation, and use labels that correspond to master operations. An example excerpt from such a file is below:
CO_tc3_xz_1, outputs is a structure, with fields that are referenced by the first five operations listed here, and the
ST_lengthmaster operation outputs a single number (the length of the time series), which is referenced by the operation named 'length' here. The two keywords 'correlation' and 'nonlinear' are added to the
CO_tc3_1operations, while the keywords 'raw' and 'lengthDependent' are added to the operation called
length. These keywords can be used to organize and filter the set of operations used for a given analysis task.