They retain, although another session is loaded. This might be intentional and useful, but sometimes you have to press 3x "export" so that file is actually properly generated for saving.

Open file, while session open, then cancel. Clears current session.

I saw the repository is licensed under the CC-BY-SA. Thanks for making this tool freely available!

If you want to ensure the free usability and improvement of this software, Creative Commons Licenses are unfortunately not ideal for software.
See https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software
Citing the imporant part:

We recommend against using Creative Commons licenses for software. Instead, we strongly encourage you to use one of the very good software licenses which are already available. We recommend considering licenses listed as free by the Free Software Foundation and listed as “open source” by the Open Source Initiative.

Unlike software-specific licenses, CC licenses do not contain specific terms about the distribution of source code, which is often important to ensuring the free reuse and modifiability of software. Many software licenses also address patent rights, which are important to software but may not be applicable to other copyrightable works. Additionally, our licenses are currently not compatible with the major software licenses, so it would be difficult to integrate CC-licensed work with other free software. Existing software licenses were designed specifically for use with software and offer a similar set of rights to the Creative Commons licenses.

Version 4.0 of CC’s Attribution-ShareAlike (BY-SA) license is one-way compatible with the GNU General Public License version 3.0 (GPLv3). This compatibility mechanism is designed for situations in which content is integrated into software code in a way that makes it difficult or impossible to distinguish the two. There are special considerations required before using this compatibility mechanism.

Here is an easy choice of a free software license: https://choosealicense.com/
Github also provides the option to easily add a License file with the right text to your repository: https://docs.github.com/en/github/building-a-strong-community/adding-a-license-to-a-repository

Since you currently use the Share Alike CC License, a natural fit would be a copyleft license like AGPL3+ that ensures that modified versions that are distributed publicly have to share their improvements to the code under the same terms.
In comparison to GPL3+, the AGPL3+ also considers someone hosting this as a website instead of directly giving out the program as a public distribution and thus they also have to share their improvements back to the community.

I hope this can be helpful to ensuring your software can be used, integrated and improved upon by more people without having to worry about licensing issues/compatibility with CC-BY-SA.
In case the licensing decision was made intentionally as is, feel free to ignore and close this issue! :)

There is an unclear and confusing relationship between intervals and annotations.
Logically there is a n:m relationship between Intervals and Annotations.

But when one annotation is assigned to an interval, the list of annotations still shows all annotations ever used in the session for other intervals.
It is hence not clear, if the annotations still are assigned to that specific time interval, especially if the don't make particurlarly sense.

It would probably make most sense to have the annotations split into two panels.
One panel just listing the annotations without values, and a second panel showing the selected annotations for each interval with values.

I just looked at the example and the annotations, the problem is that it is not clear to which sensor values the annotations refer to. So it is not clear what is going on.

Hi @dimstudio

I tried to install your little inspection tool, but failed hopelessly. Could you please add some guidelines to the readme?

Thanks
Christian