Configuration files

As already mentioned in the Basic functionalities page, there are two main types of usage for this application: one treating data files separately and the other one being more project-driven. This page will explain in deeper detail how these two options work by describing the different kinds of configuration files that are generated at runtime.

Separate files

For single data files, a configuration file is generated for each one of them: the full name of the data file is used to generate the name of the corresponding configuration file. For instance, if there is a file named data.csv the configuration file will be named data.csv.json.

In particular, this type of configuration consists of a JSON file structured as follows.

• labels: the list of label names, indicates which columns in the data file represent a label
• colors: the list of label colors, represented with a hex notation (e.g., #ff0000 for red)
• plot: the layout of the plots, by default every subplot contains a single time series
• normalize: list of plot indexes to be normalized (i.e., the scale is ignored for that plot)
• functions: the names of the calculated function columns (allows to distinguish them from the others in order to be able to remove them at will)

Project files

When a new project is opened, the user selects the files to be included. From that point, all the relevant information for the project is stored in a single configuration file, called project.json, which is still a JSON file but structured differently than before.

• files: list of data files in the current folder which are included in the project.
• labels: list of label names (shared among all data files)
• colors: list of label colors, still in hex notation (shared among all data files)
• Headers of the data files (if two have the same column names, they share the same layout)
• plot: list representing the plot layout (shared among all data files with that header)
• normalize: list of plots to be normalized (shared among all data files with that header)
• functions: the names of the calculated function columns (included in the header)

Program files

There are other two files adopted by the application which haven't been mentioned before: these can usually be found in the same folder as the TSL itself, but it is possible that if the program has no permission to read/write these files, they are stored somewhere else. Specifically, the alternative path is relative to the current user's folder:

~/.config/tsl/

Windows:  C:/Users/[USERNAME]/
Linux:   /home/[USERNAME]/
MacOS:   /Users/[USERNAME]/

• config.json: a configuration file containing the user settings (e.g., autosave)
• tsl.log: logging file for error reporting

Make sure to keep them in order to avoid unexpected behaviors!

Table of contents

• Project home
• Getting started
• Basic functionalities
• Configuration files
• Supported formats
• View on GitHub