08-29-2024, 04:48 PM
You have been correctly following the video, however, leaving out a part that –unfortunately– is required to make it work. 
(there are pros and cons for covering keep and append in a introductory video and we keep an eye on it how “well” it works in its current form)
The full technical details on the phyphox file format are in our wiki, https://phyphox.org/wiki/index.php/Phyphox_file_format, and Analysis modules in general covers the attributes “keep” and “append”.
The concept of containers in phyphox differs from classic variables in programming languages. They are closer to a pipe system, i.e., by default the data flows as input into a module and the container is empty afterwards. There are circumstances that it is convenient that the data is retained for later modules. That‘s what the keep attribute is for.
If we keep the picture of pipes, then data flowing as output out of a module comprises just this data, i.e., the (empty) container is freshly filled. Again, there are circumstances that is is convenient to add the data to that of previous modules or analysis block runs. That‘s what the append attribute is for.
I hope that this clears it up a bit. Making this easier to understand is on our list for quite a while and we hoped that the different names for the attributes helped. There used to be a clear attribute for data in and out flows, however, that proved even more confusing…
(there are pros and cons for covering keep and append in a introductory video and we keep an eye on it how “well” it works in its current form)The full technical details on the phyphox file format are in our wiki, https://phyphox.org/wiki/index.php/Phyphox_file_format, and Analysis modules in general covers the attributes “keep” and “append”.
The concept of containers in phyphox differs from classic variables in programming languages. They are closer to a pipe system, i.e., by default the data flows as input into a module and the container is empty afterwards. There are circumstances that it is convenient that the data is retained for later modules. That‘s what the keep attribute is for.
If we keep the picture of pipes, then data flowing as output out of a module comprises just this data, i.e., the (empty) container is freshly filled. Again, there are circumstances that is is convenient to add the data to that of previous modules or analysis block runs. That‘s what the append attribute is for.
I hope that this clears it up a bit. Making this easier to understand is on our list for quite a while and we hoped that the different names for the attributes helped. There used to be a clear attribute for data in and out flows, however, that proved even more confusing…